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

on second thought.. does that mean the AI can go to.. like.. most of my meetings?

hmm, according to some people, it's the work done by Jr developers 🤔

citconf.com/london2025/#...

You know this.. but how many 'Execs' don't know this?