Post

Paul Stack
@stack72.dev

Bug reports that looked like noise turned out to be 3 compounding root causes underneath. We rearchitected the whole thing in 8 days, multiple agents working together. If it failed, we lost 8 days. Previously this would've been a 6 month project unprioritised. stack72.dev/the-rearchit...

stack72.devThe Rearchitecture Your Team Could Never JustifyEvery codebase has the rearchitecture that never gets prioritised. We split ours into six parallel workstreams and shipped it in eight days, start to finish. The hard part wasn't speed. It was coordin...

0 reposts0 likes

Daniel Terhorst-North
@tastapod.com

I'm calling this 'Adjacent Engineering': things that are not on your mainline that would not otherwise get done because a) you have to learn some tech or domain just for that one time, or b) it is just too much of a time sink and opportunity cost. I describe it as 'wider rather than faster'.

Jon Topper
@topper.me.uk

Hypothesis: “wider” will always touch hygiene factors or non-functional issues, because those were always underserved vs feature development in the past. This wider focus will ultimately result in faster delivery and lower defect rates.