People often treat DDD as all-or-nothing: either you do “the full thing”, or you don’t do it at all. ¯\_(ツ)_/¯ And that’s one of the main reasons many teams never start. Because “the full thing” usually sounds like a strategic redesign, a series of workshops, a calendar full of meetings — and a request for permission that will bounce around for weeks. But DDD can be an evolution. And you can start that evolution today , with tiny steps that don’t require a revolution plan or a committee sign-off. A weekend experiment Over the weekend I created a small GitHub repo: https://github.com/pwyczes/ddd-ai-skills-applied A library of skills for AI coding agents. They’re importable rulesets that turn “help me code” into “apply this pattern, this way, with tests”. The goal is simple: Make “how we do DDD” portable across tools. Because the problem is not that the AI can’t generate code. The problem is that it will happily generate your codebase into a slightly different codebase —...
I help your development team become strategically more efficient by aligning them with the business domain they are working in, instead of just focusing on technical solutions.