I've been trying, Jason. What's the secret to finding the right ones? I've been looking for two principal software engineers to work within and across a small number of teams, embedding everything you taught us. Finding someone who can describe, leave alone do TDD or refactoring is almost impossible

The problem was never 'not keeping it modular'. Oh it would have been so much easier if we had done DDD... I mean.. yes. But not doing DDD wasn't the problem.
Not doing the things that enable long-term sustainable development was the problem. Modularity and DDD are only a small part of that.

If you don't do those things, you will eventually have to 'scale'. Because eventually, you will spend most of your time dealing with unplanned work. To continue to ship features, you will need more people. Now you have to manage dependencies. If only you had kept things highly modular...

How much future capacity you take, depends on how good you are with staying on top of your code. Teams that continuously design, refactor, test, integrate, keep libraries up to date, fix bugs immediately etc "should be able
to maintain a constant pace indefinitely".

every time I read something like this, I can't help but having a brief moment thinking.. "hang on, did we hire Jason for something recently?"

well.. apparently that worked

off we go to .cursorrules..
Priorities:
0. Fix build failures

I have questions around data residency..

Before you go, can you just quickly update the health monitoring system for our network load balancers?

Obviously I’m assuming you’re learning from each arrow. Would be terrible if you were aiming at the wrong thing for a long time. I think Kent Beck said something like ‘not more right, but less wrong’ - ie wrong for less amount of time.

I’m struggling with your analogy/picture. Sending lots of small arrows quickly into lots of directions should increase your chance of accidentally hitting the right target. Spending a lot of time carefully aiming at one thing only, assumes that you confidently aiming at the right thing.

good to know! :) maybe put us down on the waiting list for a couple of copies and should other interest materialise, we pool together?

But Jason - refactoring doesn't scale. Retire and replace is often the better option. /s

Recoding Troubleshooting Agile with @dsquirrel.bsky.social and @jeffreyfredrick.bsky.social live at @citcon.bsky.social