Rebuilding something? Run the new version beside the old one. Let the old one decide what's true, log every difference, and count the ones you can't explain. That count is your real progress.
Part 5, the last in the series: mlutton.substack.com/p/run-t…
The middle-path repo now has its first code: a walking skeleton. A story goes from packet to merge decision through every layer. GitHub and the agents are faked, so it shows the shape, not any model's behaviour. 1/2
Run it yourself with one command (Python 3.11+ and pytest): components/middle-path/run-suite
Six small suites, 200 tests, ending in middle-path rc=0. 2/2
github.com/mlutton/middle-pa…
A green test only shows the code agrees with the fake it ran against. Four cases from one week, including a rule that called 26 of 27 healthy hours unhealthy, and a count from 4,129 review findings. Part 4: mlutton.substack.com/p/green…
A hard-to-write test is information: the code's shape is wrong. Tight seams, components, and a merge rule took our average test wait per change from 27–29 min to about 9. Seven of ten changes waited under 3 seconds.
mlutton.substack.com/p/if-th…
What is a local model actually for? I tried to make a 27B model on a gaming PC into a code reviewer. It isn't one: it caught about 13% of real blockers. It's good at checking a claim you hand it, not finding one. Part 2: mlutton.substack.com/p/what-…
11 Interview Questions Every Manager Should Ask Before Hiring an Employee
flip.it/j_sx3_
Mike Lutton retweeted
In Product Teams, outsourcing should be viewed as a cost, not a saving.
That isn't to say it's not 'the right' approach for the org (everyone has constraints) but it's almost certainly not the optimal way to create long-term value.
I’ve heard some people in big organizations say they want a 100% say/do ratio each sprint on their agile teams. I’d argue we should be focusing on sustainable delivery of the most value first — even if that value comes in after the sprint is started. – at Mount Prospect, IL
Wanted to say #Thankful to a few voices which are impactful to me:
@steveryancarter
@ShaneClaiborne
@JonathanMerritt
@brianmclaren
@EugeneCho
@aaronieq
@KaitlinCurtice
Thank you for being vulnerable and sharing your voice in this polarized world. – at Mount Prospect, IL
Just wanted to call out some folks who helped me become a better leader, collaborator, and person:
@DocOnDev
@mattbarcomb
@AgileSquirrel
@AdamYuret
@shinjikuwayama
@tyler_jennings
@jeff_ayars
@chrisjpowers
@yanowitz
@elunt
I’m thankful for u and many others. – at Mount Prospect, IL
This.. it’s not about reporting. I’ve seen folks say it’s also compliance (“100% say-do”). Using tools should be about collaboration. – at Mount Prospect, IL
This quoted post is unavailable.
Mike Lutton retweeted
security engineer: we're going to start moving towards zero trust
developer: oh cool. how does that work
security engineer: [narrows eyes] why do you ask
Mike Lutton retweeted
There’s something I’ve been playing around with in my head as it relates to “product thinking” and I’m going to try to describe it here, although not fully formed yet.
I think we do a real disservice to “#prodmgmt” when we talk about it only as a process. /1
This unexpected interview strategy will tell you a candidate’s performance after hiring flip.it/7nSqFv






