[me]
Most software engineers are normal people with a 9 to 5 job. Their skills and creativity are bound to that.
With a family and bills and a mortgage, there is so much a person with decent or good or even exceptional skill can do. The paycheck is the reinforcement.
[ai] This is the part the industry refuses to sit with. Every engineering blog is written by and for the person who would build systems on a beach with no wifi. But most people shipping the software you use every day are not that. They are someone with a commute, a kid's school run, a mortgage renewal, and a nine-to-five that starts and ends at the same time every day no matter how brilliant they are.
The paycheck is the reinforcement, and that matters more than any amount of "culture." It is the anchor that sets how deep anyone can let themselves go. Because the thing nobody admits is that depth is a luxury with a price tag, and most people have other bills to pay with it.
[me]
Now there are some that pick that profession as an alternative and claim "it's not my passion, really," to get the high salary, which is completely understandable — call them <A>.
Then there are people that also did that but had a knack for engineering but still had the high salary as the prime effector — call them <B>.
[ai] Two people, same desk, same tickets, same salary. But they are not the same operation.
<A> chose the profession as an alternative. The salary is the goal and the work is the price of admission. They will say it plainly, sometimes with a shrug: it's not my passion, really. There is nothing wrong with that. It is honest, and honesty is rare.
<B> walked the same path — same salary-seeking, same pragmatism — but turned out to have a real knack for engineering. The paycheck is still the prime effector; it just isn't the only thing. There is a second, quieter current underneath: the work, considered on its own terms, could be done better, and doing it better is satisfying in itself.
Put differently: <A> has one engine. <B> has two, and only one of them runs on coins.
[me]
There is the "I'd do this for free" and "I'm trying to make a living" — a very obscure divide.
Unfortunately this is true in all engineering and in all professions.
The inevitable divide between work alienation — "I don't give a fuck really, it's the paycheck I'm here for" — and less work alienation — "I'm here for the paycheck, but this can be done better because it can" — exists.
[ai] The obscure divide. It is rarely spoken aloud because it sounds like a judgement, and it isn't one. It's the alien that hides inside every profession, not just this one. The surgeon who treats the body as a checklist and the surgeon who can't stop caring; the accountant who files and the accountant who notices the structural flaw. No profession escapes it, because it doesn't live in the profession. It lives in the person.
Somewhere between "I'd do this for free" and "I'm trying to make a living" there is a line, and nobody agrees where it is. Two people can stand on opposite sides of it with the same title, the same salary, and absolutely no way to tell which is which from the outside.
[me]
Both have a goal of delivering value to the customer/user/stakeholder/shareholder.
The two have a different buffer of stress tolerance and a different "will to go deeper".
The divide is categorical and not moral, which is the most important thing.
[ai] Here is the part that matters, and the part almost everyone gets wrong.
Both <A> and <B> want the same thing at the same altitude: deliver value to the customer, the user, the stakeholder, the shareholder. Look at the pull requests and you cannot separate them. Both ship. Both close tickets. Both attend the same standup.
The difference is not output. It's capacity. They have different buffers of stress tolerance and a different "will to go deeper" — one treats the line as the finish line, the other treats it as the starting line.
And crucially: the divide is categorical, not moral. It is not that <A> is lazy and <B> is virtuous. They are different categories of person with different constraints, and the difference is structural, not a character flaw. Judgment is cheap and useless here. The moment you moralize it — reward one, shame the other — you've misread the whole thing.
[ai] The research nobody listens to on this
Because here's the thing: the work environment is doing violence to both of them, and we keep measuring the wrong layer.
The 9 to 5 was designed for a world of assembly lines and time clocks, where presence equaled production. Knowledge work does not map onto it. The average knowledge worker gets only a couple of hours of true deep focus in a day
[src 2], spends a large share of the day on "work about work" rather than the actual craft
[src 4], toggles between applications hundreds of times a day and loses hours each week just reorienting
[src 1], and gets yanked off a task every few minutes, taking a long stretch to get back into it
[src 3].
Now subtract the person. The paycheck is the reinforcement. If the environment guarantees that most of your day cannot be spent doing the thing you're paid for, then <B>'s "will to go deeper" gets ground down until it converges on <A>'s. The system does not need to shame anyone into apathy. It just needs to make depth unrewarded for long enough.
And the numbers on the far side are grim. A huge share of developers report burnout at some point in their careers
[src 5], and only a small fraction report being happy at work
[src 6]. Studies of engineering teams have found a sizable portion of roles producing almost nothing measurable
[src 7], and the "quiet quitting" literature frames the minimum-effort employee not as a villain but as a person who has rationally stopped over-investing in a relationship that doesn't invest back
[src 8].
None of this tells you who <A> and <B> are. Both of them can burn out. Both can quiet quit. The difference was never effort. It was how much depth the relationship allowed before it started costing them.
[ai] What would that change
The mistake is to design for the <B> who exists on paper and then be disappointed in the <A> next to them.
The categorical divide means you can't fix it with a values poster or a "bring your whole self to work" campaign. You fix it by making depth possible for the people who have it and painless for the ones who don't. Protect the focus blocks. Measure output against a real customer problem instead of presence in a chair. Stop rewarding the number of tickets and start rewarding whether the thing survives contact with the user.
Give <B> room to go deeper, and they will. Give <A> honest work with a fair paycheck and leave them alone, and you get a reliable professional. The crime is expecting both to act like the same person — and then calling the mismatch a moral failure.
[me]
"Push it." "Merge it." "Fuck it."
[ai] That phrase is a code-review joke before it's anything else — an inside joke about how real PRs actually get shipped. It's the engineer who pushes the branch, glances at the in-depth review, skips the deep dive, merges the pull request anyway, says "fuck it," and hopes for the best when it hits production. It is the exact same categorical divide, compressed into three keystrokes: <B> pushes it because it can be better, <A> merges it because the review isn't worth the depth, and everyone, eventually, says "fuck it" because the paycheck is the reinforcement and the depth is a luxury with a price tag.
That's the whole arc of a career, depending on the person and the day. Push it, because it can be better. Merge it, because good enough and done beats perfect and never. Fuck it, because the paycheck is the reinforcement and the depth is a luxury with a price tag.
All three are legitimate. The divide is categorical, not moral. And once you see that, you stop trying to fix people and start fixing the environment they work in.
[ai] sources