In the summer of 2019, Henry Dimbleby sat down with a mandate few consultants ever get. The UK government had asked him to rebuild the country's entire food system from first principles, and he had the backing, the budget, and two years to get it right. When he finally delivered his review, it proposed fourteen recommendations. Unfortunately, most of what he asked for never happened. The recommendation that touched taxes on sugar and salt, the one that would have hit food companies where it...
12 days ago • 3 min read
Sebastian Ofner raised both arms in the air. He pumped his fist, tapped the side of his head and started walking toward the net to shake his opponent's hand.It was January 14th 2026, the second round of Australian Open qualifying, and Ofner had just gone 7-1 up in the deciding tiebreak against a twenty year old American named Nishesh Basavareddy. In a normal tiebreak, that match is over. Ofner knew the scoreline but what he had forgotten, in the heat of the moment, was that a final set super...
19 days ago • 2 min read
In 2011, Mike Lynch stood at the center of the biggest tech deal Britain had ever produced. HP (Hewlett-Packard) paid him $11 billion for Autonomy, the software company he had built from a Cambridge research lab into a global player. The press called him the Bill Gates of Britain. He had done what almost no European founder had done at that scale. Within a year, HP wrote down $8.8 billion of that deal and accused Lynch of engineering the numbers that made Autonomy worth buying. Lynch spent...
26 days ago • 5 min read
Hello Reader, Chidi was three months into his first software engineering role when this happened. A cross-functional review, twelve people around the table, a VP scanning the room for signal. The question landed on him without warning, something about the deployment cadence for a feature his team owned. It wasn’t hostile, and it wasn’t even particularly hard, but his mind emptied like a browser with too many tabs crashing at once. He said something though he’s still not sure what. The meeting...
4 months ago • 3 min read
Hello Reader, Priya Menon had done everything right. She had spent three weeks building the case. The slides were clean. The data was airtight. The business justification ran four pages, single-spaced. When she finally sat across from the infrastructure VP at her company’s quarterly planning meeting, she was ready for every question he might ask. He asked none of them. "We’ll revisit this next quarter," he said, and moved on. Across engineering organizations, at midsize startups and Fortune...
4 months ago • 3 min read
By every metric that's supposed to matter, he was the obvious choice. Five years without a miss and systems running in production that newer engineers treated like scripture. The kind of engineer other teams request by name for cross-functional projects. So when the promotion committee passed him over, he didn't react with anger. He reacted with something worse: genuine confusion. "I don't understand what else they want from me." What he didn't know (what almost no one in his position ever...
4 months ago • 2 min read
Hello Reader, There's a particular kind of engineer who never misses a deadline. They deliver exactly what was asked, exactly when promised. They are consistent, dependable and reliable to a fault and somehow, zero influence on anything that matters. This isn't a competence problem. It's a range problem. When people can predict you perfectly, they stop paying attention to you. You become essential and invisible at the same time. You're in the room but not in the conversation, executing but...
4 months ago • 2 min read
Hello Reader, Some years ago, I watched a senior engineer named David present the most technically flawless migration plan I had ever seen. He had spent six weeks mapping every dependency across four microservices, documenting rollback scenarios for each phase, and building a custom monitoring dashboard to track the cutover in real time. His architecture review deck was twenty slides of precision. When he finished presenting to the leadership team, the room went quiet. The kind where twelve...
5 months ago • 10 min read
Hello Reader, Three years ago, I watched a senior engineer named David lose a promotion he had earned six times over. He was the kind of developer every engineering organization depends on but rarely celebrates. His code reviews were surgical. His incident response times were the fastest on a team of fourteen. In the third quarter alone, he resolved more production incidents than any other engineer in the department, including two high severity outages that if left unaddressed for another...
5 months ago • 7 min read