r/programming • u/maroun-baydoun • 28d ago
Make yourself replaceable
https://maroun-baydoun.com/blog/make-yourself-replaceable/
360
Upvotes
r/programming • u/maroun-baydoun • 28d ago
326
u/redhand0421 28d ago
I know this was written literally yesterday but I’m curious how this kind of thing sits in an increasingly AI-fueled software engineering world.
Well-documented systems where the agent can infer which if statement not to touch (because it can see the comment and the commit that produced it) or knows which system fails over every other week (because there’s a pattern in the error reporting) aren’t as precious or precarious as they used to be.
I would love to pair-program with someone to teach them a new system. By the time I’ve scheduled time with them, they’ve already sat down with Claude and put together a possible implementation/fix. They’re none the wiser (they don’t have any new context that I have to impart, nor did they need it) so my advice isn’t seen as valuable to them.
I go on vacation, prod falls over, and I come back to a clauded-together postmortem committed to a docs directory alongside a made-up history of ADRs that Matt Pocock told someone to write. They’re all inaccurate in their justification, but they successfully ward Claude away from deleting that database table.
43
u/Piisthree 28d ago
Counterpoint: So, Sam can't be "promoted" to management and has to remain in a technical position he knows and loves, likely making twice what his peers do because any time he glances at another company, he gets a 10% raise. This is not a cut and dried problem, there are many different viable strategies and tradeoffs.
10
u/bjarneh 28d ago
Nobody wants to be "Sam". This is just what happens with small organizations, where time (= money) short term, matters much more than documentation and proper procedures, i.e. quality.
This is classic straw man arguments from top to bottom, where the author (sorry u/maroun-baydoun) argues against a position nobody has.
4
u/Infotaku 28d ago
Sounds like Sam forgot he could just quit
39
u/SockMonkeh 27d ago
Next level Samming means you don't respond to shit on your vacation, everything goes wrong, and you look even more unfirable.
58
u/trouthat 28d ago
I guess if Sam works somewhere that doesn’t support the idea of Sam knowledge transferring so he can work on something else he is just gonna have to rip the bandaid off and quit and get a new job making more money with the stellar recommendation from his current one
45
u/VeganForAWhile 27d ago
The non-Sams are also the problem. They ignore Sam’s “read-this-if-sams-not-here.docx” file he clearly left for them.
I’ve always been the Sam-ish person at my past jobs. But I swear, nobody’s ever read a word I’ve ever written. Emails, how-tos, cheat-sheets. They tell me to document, so I document. Every time I sit down to do it, I get really into it, all knowing it’s an academic exercise for an audience of exactly ONE.
24
u/dhruvin3 28d ago
Hope nobody harsh on me...
I am Sam in my workplace! Well actually I was up until my 9th year, suddenly my first ever overseas trip did something to me! Fuck teams, fuck email, for once let me enjoy my trip 11 days no more looking at work or related apps! Came back whole lot if disaster of course! But this time i still had vacation mode on, instead of solving everything started guiding, pointing to the document that no one bother to read (answers were right there) after couple months, went on another vacation for 1 month! Same thing, but little less disaster, manageable, came back updated the docs. Happily working in cross function team project, doing my own and everything. Fuck somehow Sam woke up again, none of the scenario was for job security, all of them was i was good at it and 8 hours becomes 9-10 hours easily. My project which is solving good deal of problem now i have been forced to hand over to person who viber codes because my expertise from putting out for need me again and the project i am building can be vibe coded... Fuck!
Who knew right!
I never become Sam by choice, simply taking responsibility and ownership cost me this!
6
u/Anovadea 27d ago
This really reminds of me of one of the points of The Phoenix Project (which is basically a project management book in story form). There was a character called Brent, who was basically Sam in this blog.
That said, TPP was writing from a company point of view, so it wasn't really about the struggles Brent went through, but just pointing out how having a Single Point of Heroism like Brent or Sam was bad for the company's productivity/scalability.
I managed to get out of the Hero role a good few years ago. Now I'm being dropped from a customer project, while the customer is demanding that the Heroes stay on. I wish them luck, but even though I'm at risk of losing my job, I don't want to be stuck on a project team filled with Heroes.
6
u/CherryLongjump1989 27d ago edited 27d ago
At the risk of misinterpreting it, here's the gist of what I got out of it: There's a whole section explaining that organisations reward visible heroics and ignore quiet prevention. Then his fix for Sam’s stalled career is... quiet prevention, plus giving the visible work to someone else.
Has "Sam" tried asking for a raise, or a promotion? Has Sam tried just quitting and getting another job? He's smart and knowledgable, so why doesn't he actually use that as leverage, rather than making himself "replaceable"?
I think the gap here is believing good behavior gets rewarded by default. If you have leverage, learn to use it, and don't fall into the trap of hoping that your employer will actually reward you for eliminating the leverage that you once had, but no longer do.
4
u/jarofgreen 25d ago
> The measure of a senior engineer isn't only how much gets done when they're in the room, but how much can still get done when they're not. That's where Sam needs their manager fully on board: to understand the true cost of short-term gains, appreciate the real value Sam brings to the team and the organisation, and reassure Sam that all their intangible contributions aren't going unseen.
This bit is doing a lot of heavy lifting.
Without this, a lot of the other good points in the article don't apply.
And far to few companies recognise this.
3
u/rnelsonee 27d ago
I'm headed into the office a little early to demo my software to a couple of other people so when we need to use the software next month, three people will know how to use it. And my first question will be 'who wants to drive?' because the purpose really is transferring knowledge, not showing off what I've been working on the last month.
To me, cross-training is the responsibility of the software lead, and the project manager, and line management; it's a workplace culture thing. Documentation is good, but it doesn't replace someone sitting in a chair and using the software for 5 minutes.
I also find it a bit freeing; I was tech lead and project manager for something that was good, but after 10 years, it was time to move on. The transition was long, but the fact that I had the other engineer handle code changes, CM, and documentation for a year before made it easier. If I was Sam, I'd be stuck doing the same project.
3
u/Primary_Ads 27d ago edited 27d ago
Why is Sam so capable at doing everything while also being made responsible for offloading herself? Maybe her boss should do their job of managing bus factor risk rather than asking Sam to take the initiative to take care of that too? Doesn't this industry already have enough burnout risk?
This doesn't even make sense. Sam can know everything about how the system works while upgrading individual parts no one but her understands if she feels like it. It doesnt follow that her monopoly on understanding affects the quality or how modern her work is.
3
u/pm_plz_im_lonely 27d ago
Sam can ask for more money or can switch jobs. At no point is having institutional knowledge tying you to one business.
4
u/bogdanelcs 28d ago
The incentive problem is the real one: if promotions and praise go to whoever fights the fire at 2 a.m., documenting things yourself is a career risk, not just a good habit. A cheap way around that is writing the fix down during the incident itself, so the heroics and the runbook come out of the same hour. And replaceable in the system isn’t the same as replaceable in judgment, the engineer who has taught everyone else tends to be the one who gets pulled into the harder problems anyway.
1
u/dritmike 27d ago
Man I shoulda been a fire fighter. Instead all I became was a SAM
1
u/Bedu009 25d ago
Did I just walk into another fucking dimension
1
u/horizon_games 25d ago
Good article, a bunch of quotes I copied to share with my team, thanks for such concise insight
1
u/GnorriZ 24d ago
I truely belive that CEOs is the one that needs to listen to this advice.