The 2023 skill erosion argument was easier to dismiss as an old automation story. In 2026 it is harder to dismiss. The point is not that AI makes people stupid. The point is that AI makes it very easy to skip the part where competence is actually fo...

Juniors In reaction to the often-heard complaint that the SWE profession would suffer the absence of junior engineers due to AI + seniors doing all the work, I recently was thinking the following. This is not going to happen, because there will al...

A lot of people say the new skill is writing better specs. I agree, but I think there is a trap here. A good spec is not just a more detailed prompt. It comes from understanding the domain AND software engineering well enough to know what should not ...

Forward-Deployed Engineers recently became the new hot role across big AI companies. The FDE feels more like an old enterprise software consultancy coming back again. In a nutshell it is field engineering, consulting, systems integration, domain ana...

Most product changes do not enter a company as clean technical tasks. They arrive as rough business intent. A customer is confused. A workflow feels slow. A new case must be supported. Some manual operation should be automated. Someone says: "can we...

One of the loudest claims around AI coding tools is that one developer can now do the work of a whole team. Ship features in hours. Replace weeks with prompts. Move 10x faster. Well, maybe. But only if you pretend that software development is mostly...

I bumped into the claim somewhere on LinkedIn and that got me thinking why some people may think so while others consider this a huge overstatement. As I often see, such contradictions emerge because people judge microservices from very different imp...

AI storm has revealed an opinion that in AI-accelerated product teams, traditional "source of truth" artifacts like Figma, design documents, software models become obsolete because products evolve too quickly, with codebase modified directly and iter...

AI is not one tool. That is the ubiquitous judgment mistake across posts in social networks. AI is a set of very different capabilities, and treating them as one thing is where most confusion starts. Some parts are genuinely useful in engineering. S...

This is the teaser post of the original1 review that is pretty detailed, containing images and diagrams. Beck K., Extreme Programming Explained 1999 Extract The book is only 1/5 about programming and 4/5 about organizational matters. The book cove...

In software engineering, work is almost never purely mechanical. The hard part isn’t typing code, it’s discovering constraints, modeling the domain, defining contracts, and making irreversible decisions explicit. When that work is done, TDD / codin...

The AI publicity landscape is full of either bought or excited adopters' promotion, with a very small part of experienced engineers feedback. As very fairly noted on LinkedInhttps://www.linkedin.com/feed/update/urn:li:activity:7391379938538311680?up...

I will be very quick on this. Consider. Code for business applications is a constant flow of professional decision - product and engineering context bounded - 100% deterministic - conscious and precise, not arbitrary and probabilistic. The ability...

There is quite a terminology collision among these terms happening in backends. This short note concisely explains what is what, where, and what for. Contents Event-Driven Architecture EDA Messaging Disambiguation Event Sourcing Event Storming ...

This is the teaser post of the original1 review that is pretty detailed, containing images and diagrams. Meszaros G., xUnit Test Patterns 2007 Extract This bookhttps://www.amazon.com/xUnit-Test-Patterns-Refactoring-Code/dp/0131495054 is essential ...

TDD: Barrier and Brilliance TDD stalled on Beck’s “no design before tests” flaw, but when paired with thoughtful design it flips costs into benefits—isolated complexity, minimal debugging, and cleaner interfaces shaped from the consumer’s view. >...