Three sessions. Your real codebase. I work with you to apply Combinant® Design to the software you ship — decombine, recombine, and measure whether the cost of change goes down.
3 sessions × 2.5 hours · Online (Zoom) · For course participants only
Your goal is clear: reduce the cost of change in your codebase — and prove it with numbers. Combinant® Coaching is how we do it together. Every session is structured around applying Combinant® Design to your real code: finding the fundamental elements hiding inside your architecture, applying Decombination®, recombining, and measuring the result. Effort per feature, cost per change, recombination ratio. Before and after. On your code, not on course topics.
Each coaching session is 2.5 hours of working on your real codebase using Combinant Design. What we focus on depends on where you are.
Understand. We look at the code together. We identify the areas where change is expensive — the classes that keep growing, the IFs that multiply, the features that take longer than they should. We measure what's there: classes, IFs, dependencies, rigidity. This is the baseline.
Combination. We look at the same code through the lens of Combinant Design. What would it take to make this software combinable? We map the domain: which behaviors repeat across features, which structures share the same shape, where the building blocks are buried inside monolithic classes. This is the design target.
Decombination. We break the design apart on a shared board. We find the fundamentals hiding inside your biggest structures. The goal is to extract pieces with high recombination potential: small, independent, reusable across features. You see them emerge. We discuss alternatives at every turning point.
Recombination. We put the pieces back together in new ways. Features that used to require new code now emerge from existing building blocks. We measure again — same metrics, different numbers.
Continue. If you book more sessions, we move to the next area of your codebase. Each round, the fundamentals library grows. Each round, the cost drops further. The curve becomes visible across your whole architecture.
You can book one package of three sessions to start and continue with more as your codebase evolves. There's no fixed sequence — we work on whatever matters most to you right now.
You lead a team or a codebase and you've noticed: every new feature costs about the same as the last one. Sometimes more. Your architecture is supposed to make things easier, but the cost doesn't go down. You want to know if there's another way — and you want proof on your own code, not on a textbook example.
You don't need to have taken any Combinant course. If you write or review code for a living, you're ready.
You've seen the method on Breakout, on MiniVi, on course topics. You know it works in controlled environments. The question is: does it work on my code? On my team's architecture? On the mess we've accumulated over three years?
That's what coaching answers. Not in theory. In your repo, in your metrics, in your next sprint.
The before/after dashboard is yours to keep. Show it to your CTO. Use it to justify the next refactoring cycle. Or use it to decide the method isn't for you — at least you'll know, with numbers.
Coaching is for professionals who want to apply Combinant Design to their own software. It's independent from the courses — you don't need to have taken Combining Breakout or any other course.
That said, if you've completed a course, coaching is the natural next step: you've seen the method on course topics, now you apply it to your real work.
Francesco Cirillo. Senior software designer, Extreme Programming pioneer. Decades of designing software led to one question: how do you reduce the cost of change? Combinant® Design is his answer.
Book Coaching — $750 Launch price