Most developers use AI assistants the same way they use a search engine: ask, get an answer, move on. That habit is costing them the most valuable thing AI can actually do. The real power isn’t in generation — it’s in conversations that build understanding before you write a single line of code. Topics covered:
5 AI Conversation Patterns Every Developer Should Know Read More »
Most developers are leaving a lot on the table with AI coding assistants — not because the tools aren’t good, but because of a few fixable mistakes I keep seeing in real teams.In this video I cover three common mistakes and how to avoid them: Plus a bonus fourth mistake: only using AI for code
3 AI Coding Assistant Mistakes I See in Real Teams — And What to Do Instead Read More »
A recent post by Simon Wardley makes the point that the transition to AI will take a while because it requires practices to emerge and be accepted, to co-evolve with AI. Alex analyzes and comments this theory. Links:
Practices Coevolve with AI Read More »
Pure functions are functions that return the same value for the same input values, and don’t change the state of the system. Idempotency refers to functions that make the change a single time, if receiving the same relevant values – either input arguments or an identifier. These two concepts are related in that they help
Simplify Designs with Pure Functions & Idempotency Read More »
After going through our courses on clean code, refactoring, TDD, or software design, a common question is “how do I convince my colleagues to follow these practices?”. The answer is more subtle than you might expect, and it involves an interesting trip to the patterns community.
How do I convince my colleagues to <practice> Read More »
We’ve often noticed how people starting with a technique imbue it with a lot of potential to solve all the problems of software development (* exaggerating for effect). This is rarely the case. Let’s look in particular at domain modeling, and how bounded contexts are not 1-to-1 to business domains, inspired by another excellent article written by Mattias Verraes.
Architecture Modeling is Complex, Exemplified Read More »
Can Claude help with legacy code? Let’s try to use it and see what value it adds and what limitations it hits.
Can Claude help with legacy code? Read More »
Architectural Kata is a format that helps software architects and software developer with an interest in software architecture practice techniques related to the challenging arts of modeling, designing, and structuring software systems at a high level. In this video, Alex explains what the architectural kata is and how you can benefit from it. Also check
Architectural Kata Explained Read More »
The modular monolith is a mythical beast of software architecture. While it sounds simple enough – single deployed unit, separated in modules – it’s rarely seen in practice as it very quickly devolves into spaghetti code or a big ball of mud. In this video, Alex explains a few important considerations for modular monoliths:
Modular Monolith Architectural Style Read More »
A new essay by Rebecca Wirfs-Brock and Mattias Verraes was published on Rebecca’s blog, and it’s very insightful. Alex reacts and comments on the signals for software design and software architecture and on the need for experiments for exploring the design space. Links:
Signals and Experiments in Software Design and Architecture Read More »
