Tag: Engineering Culture

Categories
Authors

Tracy Kidder and the Human Code

Tracy Kidder died yesterday, March 24th, of lung cancer. He was 80.

I’ve been sitting with that quiet, heavy fact for a few hours now, staring at the screen, thinking about what his work meant to me—and specifically, about the enduring legacy of The Soul of a New Machine.

On its surface, the book is a chronicle of a team of engineers and coders at Data General Corporation, racing against the clock in the early 1980s to build a 32-bit minicomputer. If you haven’t read it, that description likely sounds like the synopsis for a dry technical manual. It is, gloriously, anything but.

What Kidder did—what hit me with such force when I first turned those pages—was capture the raw, unvarnished pulse of human obsession. He didn’t just document the architecture of a machine; he mapped the architecture of the minds building it. He translated the late-night pizza runs, the bloodshot eyes, the tribal hierarchies of the engineering floor, and the strange, almost religious fervor that overtakes people when they are creating something they profoundly believe in.

He called it:

“An adventure story, a kind of cultural anthropology.”

That is exactly right.

He ventured into a world most journalists would have fumbled or fundamentally misunderstood.

The early computer industry was hyper-technical, fiercely insular, full of impenetrable jargon, and populated by brilliant minds who regarded outsiders with a polite, if dismissive, suspicion.

But Kidder didn’t blink. He embedded himself. His deep reporting and novelistic prose illuminated the basement labs of tech just as deftly as he later illuminated home construction and global disease prevention. He held a fundamental trust that the human drama playing out inside the sterile machine room was worth finding. And he found it.

Reading Soul as someone who has spent years orbiting technology, I continually find myself marveling at a different kind of engineering: how does a writer actually do this? How do you make the arcane feel intimate?

As one reviewer aptly noted at the time, “Kidder makes the telling seem absolutely effortless.” Which is, of course, the ultimate tell. Effortless prose is always the product of staggering effort.

A friend once said of his process:

“Tracy throws up on the page and cleans up afterward. He was absolutely indefatigable in the writing.”

That immense labor shows—not as the sweat of a struggling author, but as the pure clarity of a master.

What the book quietly teaches, if you’re paying attention, is a profound lesson about the nature of craft itself.

Those Data General engineers weren’t just building a minicomputer. They were building an identity, a tribe, a shared sense of purpose. They were transferring a piece of themselves into the silicon and wire. Kidder understood this alchemy. He highlighted people who had mastered their realms, elevating them into characters whose struggles rang true because they were anchored by staggering amounts of research. He believed—and subsequently proved to the world—that ordinary people doing terribly difficult things in obscure rooms were worthy of the full weight of literary attention.

That was his extraordinary gift. And it is far rarer than it sounds.

The honors and brisk sales from the book vaulted Kidder into the top ranks of American nonfiction writers. But his true legacy lives in the narrative talents he inspired. I suspect a vast number of people who went on to write serious, empathetic nonfiction about technology read Soul at some formative moment and thought: This is how it should be done. I know I was one of them.

He will be deeply missed. But the book remains, waiting on the shelf. If you haven’t read it, today feels like exactly the right day to start.

Categories
AI Programming Prompt Engineering Software Work

The Great Inversion

For twenty years, the “Developer Experience” was a war against distraction. We treated the engineer’s focus like a fragile glass sculpture. The goal was simple: maximize the number of minutes a human spent with their fingers on a keyboard.

But as Michael Bloch (@michaelxbloch) recently pointed out, that playbook is officially obsolete.

Bloch shared a story of a startup that reached a breaking point. With the introduction of Claude Code, their old way of working broke. They realized that when the machine can write code faster than a human can think it, the bottleneck is no longer “typing speed.” The bottleneck is clarity of intent.

They called a war room and emerged with a radical new rule: No coding before 10 AM.

From Peer Programming to Peer Prompting

In the old world, this would be heresy. In the new world, it is the only way to survive. The morning is for what Bloch describes as the “Peer Prompt.” Engineers sit together, not to debug, but to define the objective function.

“Agents, not engineers, now do the work. Engineers make sure the agents can do the work well.” — Michael Bloch

Agent-First Engineering Playbook

What Bloch witnessed is the clearest version of the future of engineering. Here is the core of that “Agent-First” philosophy:

  • Agents Are the Primary User: Every system and naming convention is designed for an AI agent as the primary consumer.
  • Code is Context: We optimize for agent comprehensibility. Code itself is the documentation.
  • Data is the Interface: Clean data artifacts allow agents to compose systems without being told how.
  • Maximize Utilization: The most expensive thing in the system is an agent sitting idle while it waits for a human.

Spec the Outcome, Not the Process

When you shift to an agent-led workflow, you stop writing implementation plans and start writing objective functions.

“Review the output, not the code. Don’t read every line an agent writes. Test code against the objective. If it passes, ship it.” — Michael Bloch

The Six-Month Horizon

Six months from now, there will be two kinds of engineering teams: ones that rebuilt how they work from first principles, and ones still trying to make agents fit into their old playbook.

If you haven’t had your version of the Michael Bloch “war room” yet, have the meeting. Throw out the playbook. Write the new one.

Categories
Creativity Curiosity Living Work

The Human Router

There is a distinct difference between information and wisdom, and often, that difference is measured in velocity. We are accustomed to thinking that faster is better—fiber optic cables, 5G, real-time Slack notifications. We want knowledge to travel at the speed of light.

But Dan Wang, in his book Breakneck, captures a sociological truth about Silicon Valley that defies this obsession with speed:

“When I worked in Silicon Valley, people liked to say that knowledge travels at the speed of beer. Engineers like to talk to each other to solve technical problems, which is how knowledge diffuses.”

It is a charming, slightly irreverent metric, but it points to something profound about how humans solve difficult problems. There is “codified knowledge”—the explicit instructions found in textbooks, API documentation, and internal wikis. This travels instantly. It is frictionless. It is also, usually, insufficient for true innovation.

Then there is “tacit knowledge.” This is the intuition, the heuristic, the war story about why a specific architecture failed three years ago. This knowledge is heavy. It doesn’t travel through fiber optics; it travels through proximity. It requires the social friction of a shared table and the serendipitous collision of two engineers venting about a seemingly unrelated problem.

Crucially, this mechanism requires a specific type of operator: the Connector. These are the unsung heroes of the “speed of beer” economy. They aren’t always the 10x engineers on the leaderboard. They are the “human routers”—the people who instinctively know that the problem you are facing today is the same one Sarah from the Platform team solved last year. They are the ones who drag the introverted genius out to the pub, not to distract them, but to plug them into the grid. They curate the environment where the spark can jump the gap.

In our modern drive for remote efficiency, we are optimizing for the transfer of data. But we must be careful not to optimize away the people who pour the drinks, literal or metaphorical. That slow, liquid diffusion of ideas is often where the real breakthrough hides—steered by those special few who know exactly who needs to talk to whom.