Isaac Abraham

want to learn more about fluent method chaining in c# ?

4

Since the introduction of the Delivery API in Umbraco 12, the amazing Umbraco community has been asking a bunch of questions on how to do this and that with the API. A lot of those questions have led to a better API feature set and/or improved documentation 🚀 A few have not (yet) made it into the official docs. I have put together a blog post describing some of the most interesting/useful, undocumented extension points in the Delivery API. 👉 https://lnkd.in/dNRVh3hn #umbraco #headless

29

2 Comments

🚨 JavaScript Contractor Pay Rates 🚨 Over the last 2 weeks I've spoken to 80+ JavaScript Engineers, who are all contractors, and are all highly skilled and experienced with React. They have other skills of course, but their core skill is React/Typescript. Below is a scatter graph of what they are getting paid right now in a contract role. I did this a couple of years ago and I remember there was a huge variety of rates regardless of experience, what I can see from below is that rates have stabilised massively, and people are now getting paid pretty consistently dependant on their level. It's good to see the market has stabilised and that people are getting paid what they are worth. If you feel you are getting paid below market rates, reach out and we can see what other opportunities I have for you. Or if you are looking to ramp up contingent staff quickly, and need to know what you should be paying, reach out. #JavaScript #TypeScript #React #Contractors #Sydney

25

7 Comments

I don't often post things like this but I'm seeing a lot of misinformation around TDD and it not working or is a failure. I've been responsible for implementing or pushing TDD for over 15 years now and have gone through various different frameworks, and methods. When I joined SRL there was a growing bug problem, and zero worth unit, integration, or UI tests. Over the last three years Martin Thorne, Steve Pugh, Olufemi Adesina, Kathryn Beggs, and latest recruit Maude Williamson have worked diligently to create Unit, Integration and Cypress UI frameworks in place. The coverage for each is on average over 80% and continues to improve. It is the responsibility of developers to test their own code and is often the first line of defence against poor requirements. We're now averaging +1 bug/month reported from clients, and usually these are P3, P4s, or disguised scope creep. Simply put TDD DOES work - but as with any skill if you've not got genuinely experienced people then it's going to be a mess. *Ahem* Agile my eyes are on you.

18

1 Comment

Moving jQuery => React, wasn't easy for me... React fitted well in many of my use-cases but not all projects needed npm, configs, compiling etc. I felt bloated with the effort I need to do, to get myself coding the project. I wanted a lightweight plug-n-play solution, which I found in form of AlpineJS. I used Alpine for many side projects, or wherever I wanted to start SUPER SIMPLE... Some of the things I love the most about Alpine: ➜ Super simple to setup ➜ Small bundle size <10kb ➜ Good rendering performance ➜ Very simple learning curve ➜ can fit with any CSS framework (even Tailwind) Off course there might be some drawbacks compared with React, like no routing etc. But it serves the purpose well. P.S: Just a Monday attempt to share some experiences, What you use for your side-projects btw? #softwareengineering #javascript #js #mondaymotivation

5

It's not all non-symbolic AI... I presented today to Accord Project Technology Working Group on recent enhancements to the Template Engine and how TypeScript expressions within templates are compiled and evaluated. Accord Project uses TypeScript over Concerto types (with Concerto also compiled to TypeScript) to provide type-safe logic/calculations for templates; ensuring that a wide array of programming errors are caught at template compilation time, not at runtime. #typesafety #soundness #typescript #templating #legaltech

17

2 Comments

Pair programming is terrible for a team… 🔴 When it gets forced upon them… It can be a powerful tool when used appropriately and without dogma. 🟢 The mindset of the developers and the relationships between them are crucial for it to succeed. Be pragmatic; allow developers to pair up if they want to, but don’t force it. Have you ever seen pair programming fail miserably? Why did it fail? 👀 ----------------- 🔄 Support by reposting 👉 Follow Richard Donovan - Wellbeing for Software Developers & Leaders

52

30 Comments

Here's a concise representation of your ML platform, courtesy of Laszlo Sragner.

1

A topic I talk to lot's of people about is legacy systems... Many organisations have outdated software that was created a long time ago, and the original developers have moved on. This leaves them vulnerable to various issues and risks 😓 How can we help: - We can update and modernise the systems to extend their lifespan - We can support them if you're thinking of replacing them in the future - We can help mitigate the risks associated with legacy systems in the business If this sounds like something you're currently dealing with then feel free to drop me a message, or get in touch with us over at https://bit.ly/4aV0dNn to see how Ghyston could help you 💬 #LegacySystems #SoftwareSolutions #SoftwareDevelopment

12

Cloud providers provide a service. Programmers use that service. Why do job adverts for programmers say they need to be _experts_ in one particular provider? It's like advertising for a van driver and saying they want experts in Ford Transit Mk. III's.

13

5 Comments

Across my recent polls, only 17% of developers said they learned C# in school or University... why?! Most C# developers seem to "fall into" C# further into their career, rather than dive into their early careers with C# already under their belt. Is this partly what contributes to C# not having a 'shiny and new' reputation, despite consistent updates and new releases? Check out my article in the comments which looks into how we can do C# hiring well despite it not being in a majority of curriculums. #CSharp #DotNET #LinkedInArticle

23

7 Comments

We’re getting close to typing some C#! We’ve described our components in plain language and listed their dependencies in the Architecture documents. At the very end of the stream, I talked a little bit about Contracts in software development, and why they’re important. We’ll talk about that some more this afternoon. The stream is archived in the usual place, I’ll link it in the comments. See y’all at 1:00 pm eastern over on Twitch! #thatDeveloperDad #liveCoding #softwareArchitecture #cSharp #dotNet 

1

1 Comment

What is a TypeScript Engineer? I keep seeing this pop up in recruitment posts, which means clients are asking for it...right? Has this replaced the FullStack Engineer, which, lets be honest, meant a NodeJS developer. That was back in the good old days when it was only NodeJS. Now we have Bun, Deno, Hono and more. Or perhaps its asking for a Javascript developer...whatever that means in todays world of a thousand js frameworks and evolving ES standards. Or are they actually asking for a Java developer, because someones used Gen AI along the way and it got confused between Java and Javascript (*shudders*) Are they seriously in need of a type system engineer, thats kinda niche. It's hard enough trying to explain what you do as a job to "normal" folk as it is, without this level of obfuscation. How would you even explain this when asked "What do you do?". Do kids nowadays needs to consider themselves experts in everything inside package.json to land a job? When will the industry move beyond this fixation on specific languages? I get it, it's an important consideration, but asking for Typescript Engineers...it's not going to help you find the devs you actually need.

14

7 Comments

Have you used Wardley Mapping in your teams? Maps can be used to help you find a route to your destination. Many of our other diagrams in technology either document things as they are, or describe an ideal future state. Wardley maps can help you leave that 2 hour meeting with clear next steps. They also help us ride the architect elevator up a few floors and tell compelling stories to our business stakeholders about why all this Serverless modernization stuff matters to them. In the new episode of Serverless Craic, David Anderson, Michael O'Reilly and Mark McCann talk about their experience after a decade of using Wardley Maps to get buy in, and go on to execute some of the most successful Serverless First transformations anywhere on AWS. Well worth a listen, and I’m looking forward to part 2.2.

22

3 Comments

Why do I favour practices like developer testing, TDD, refactoring and continuous integration? It's to enable rapid & sustained evolution of production-ready software. The odds of delivering the right thing in a single pass are so remote that many iterations are likely required. And even when we hit the bullseye, it's almost always a moving target. Not least because putting software into an environment has a tendency to change that environment and the problems we need to solve.

43

Check out my latest articles on TheServerSide! I've been sharing insights on newer stuff on Java. Give them a read and let me know what you think. #TheServerSide #Java https://lnkd.in/gXEN588N

26

1 Comment

One of my goto lines: "What if we just spent a day building a nice spreadsheet?" If it brings 80% of the value for 1-2% of the cost, maybe we should just start there. In time, if the spreadsheet evolves and matures, and the business process evolves and matures, and it becomes clear EXACTLY how the custom software should be designed/built, THEN it might make sense to solidify that into a custom solution. -- Related, my other first suggestion for automation is: "Do you have a checklist for this process, yet? It's a really low cost way to get a ton of early automation value." Existing employees can use the checklist. The checklist can evolve as more edge cases are discovered about the process. Eventually, it's so clean and stable, but taking longer than it ought to, that crystalizing the logic of the checklist into an actual program might make business sense. -- Start small. Only build custom when you really need to, and after exhausting the low-hanging fruit options. You might discover that you don't need custom at all. But if you do, you'll at least benefit from significantly reduced development costs due to having a rich algorithm clearly written down already.

12

7 Comments