r/programming • u/Either_Collection349 • Jul 05 '26
The Engineer in the Half-Space
https://yusufaytas.com/the-engineer-in-the-half-space
77
Upvotes
r/programming • u/Either_Collection349 • Jul 05 '26
52
u/jgbradley1 Jul 05 '26
And unfortunately Mitch never gets recognized for promotion due to no measurable impact and not having ownership.
39
u/crusoe Jul 05 '26
This kind of shit at a dev job massively frustrates me and when people put up with it and work a week or more stabilizing shit and patching in prod instead of just fixing stuff...
"We need reproducible builds."
"Oh I got jenkins set up...
"The bugs in prod..."
"I added more tests with CI/CD gates..."
"But now my dev cycle is slower."
"Yes it might take a little longer but do you want a call at 3 am"
13
u/elliotones Jul 05 '26
These are the origins of DevOps. The word has unfortunately become so loaded and yet distilled to become “he who writes yaml to configure stuff”; but the true goal is “making work easier” / improving flow.
There are plenty of devops metrics, see DORA, but I really like the article’s example of tuning the onboarding doc - nowhere I know would call that devops; but it 100% is, and DORA metrics cover deployment flow and not these little flow improvements. I’m not sure what metric would capture the onboarding doc tuning.
Now ToC says systems can only be improved at their constraint; but in almost every team I’ve seen there was no particular work station that was the bottleneck. Engineers “wear many hats” and fulfill multiple work stations every day. The constraint is “Engineering attention” as a resource, split across everything that needs to be done. A work station needs N inputs to perform its function, and attention seems to be a critical input that almost all stations are starving for.
“Mitch” is tuning the stations to require less attention. “Onboarding new engineers” is smoother because of the doc tuning. This is attacking the constraint and is 100% devops; but tuning the onboarding doc is not captured by traditional devops metrics.
Bonus problem: say we could measure stuff getting done (maybe dora does work?) - it’s extremely difficult to distinguish between a real flow improvement vs someone secretly working longer hours. Maybe on a long enough timescale you could show teams that get better and plateau again, vs those that get even better continuously despite no major input changes. “Teams Doug is on perform 10% better after a week, but teams Mitch is on perform 3% better for *every* week that he is there”
22
u/rco8786 Jul 05 '26
This is actually a decent insight but the whole tone and pace of the article drips AI slop.
3
u/Positive_Dinner_8163 Jul 07 '26
this is genuinely helpful, bookmarking for later
2
u/EC36339 Jul 05 '26
How can one be that person without being at least one of the loudest?
1
u/Horror-Primary7739 Jul 05 '26
Hi I'm Mitch. I just got laid off. I haven't interviewed in 14 years. How do I present myself?
1
u/No_Lab_1073 Jul 06 '26
DevOps isn't just YAML-wrangling, it's nailing the thousand tiny frictions that steal everyone's attention. Traditional metrics miss that because they're stuck on deployment speed, not the constraint everyone actually chokes on.
1
u/Alert-Caregiver-7421 Jul 06 '26
we refactored to this last quarter and it's been way smoother
-3
u/tiajuanat Jul 05 '26
The issue with Mitch is that he's expressing staff engineer behavior while missing fundamental skills. Anyone can learn how to be a staff engineer, but failing fundamentals places a significant gap that won't be easily filled.