Kent Beck to juniors: your salary is an option premium on who you'll become

"We didn't hire you to complete tasks"

Kent Beck — the programmer behind Extreme Programming and TDD — wrote a newsletter post addressed to junior engineers, and the title is the thesis: the company didn't hire you to finish tickets. It hired you to become someone worth keeping. He puts the economics plainly:

"We are paying your salary now as the option premium on the engineer you are going to become. If we play this game right, we'll have a kick-ass next generation of engineers."

From there he lays out a grading rubric. The floor — what keeps you a B instead of a C — is unglamorous: your code actually works, you communicate, your estimates land within about 3x, you don't dump unreasonable work on others, and you never make the same mistake twice. The ceiling — what makes you an A — is about learning velocity: question whether a task needs doing at all, find the high-impact 10%, ship small reviewable diffs daily, and simplify the surrounding code while you're in there ("make the hard change easy, then make the easy change"). The advice that follows: take the time those skills save you and reinvest it in ways that help others.

The line that set the thread off was the other side of the bargain:

"Brutal as it seems, we'd like to expend as little effort as possible on people who aren't going to make it."

"They hire juniors because they have junior tasks"

The most direct rebuttal challenged the premise itself.

"Companies do not hire juniors as some long term play to develop them into good engineers. They hire juniors because they have junior level tasks that need completed." — a reader who found the rubric useful but the thesis wrong

That reframe matters: if the company isn't actually buying an option, then "we didn't hire you to complete tasks" is a story juniors are told, not a deal they're in.

"This is what a complete lack of leadership looks like"

Others turned the option-premium logic back on Beck. A reader with 24k+ karma quoted both halves and called the math broken:

"'We'd like to expend as little effort as possible on people who aren't going to make it'… And this is what a complete lack of leadership looks like. [the premium line] — Not if you do jack shit to help them improve." — a reader with 24k+ karma

Another read the whole piece as posture:

"So much of this is written with an air of superiority over the noob. Indicates a bit of an ego problem… The goal should be to boost everybody's productivity instead of treating them like a game." — a commenter on the article's tone

The honest version, from someone who hires juniors

The sharpest support came not as agreement but as confession. A founder who hires juniors said the A/B/C sorting is real — and ugly — because mentoring isn't rewarded.

"The quality of the questions and how much effort they have put in… are what differentiates a C from a B… a C who sponges up your day quickly gets categorised into not being given fun or difficult work… the industry treats mentoring time as lost time." — a startup founder and CEO

That's the uncomfortable middle: Beck describes the machine accurately, and the thread's objection is to the machine, not the description.

The catch nobody on either side denied

One reply quietly undercut the entire rubric:

"It's interesting that you have to be an A to tell the rest apart. And good luck if you have a lot of Bs that believe they are As." — a commenter on who does the grading

And the era-mismatch objection: the option-premium model assumes a junior stays long enough for the option to pay off. In a market where "tenure is better measured in months than years," and where seniors brag about how much code AI now writes, the bet Beck describes may be one neither side is actually around to collect on.