Nobody Knows: Kent Beck on Navigating Uncertainty When Old Skills Lose Their Edge

Nobody Knows

TLDR: Kent Beck launches his "Still Burning" series with a raw admission: nobody has the answers anymore, not even thirty-year veterans. The prescription is cheap experimentation, letting go of what no longer serves you, and staying engaged despite the uncertainty.

Summary:

Kent Beck, the mind behind Extreme Programming and the author of "Tidy First?", has kicked off something called "Still Burning" — and it reads like a manifesto for anyone who has spent years building expertise only to watch the ground shift beneath their feet. The central thesis is disarmingly honest: nobody knows what comes next. Not the senior engineers, not the architects, not the people who have been shipping software since before some of today's developers were born. That kind of radical honesty from someone of Beck's stature is both refreshing and a little unsettling.

What makes this piece interesting is the framing. Beck is not throwing his hands up in despair. He is arguing that the correct response to deep uncertainty is not paralysis but experimentation. You try things. You run cheap experiments. You treat your assumptions like hypotheses rather than truths. This is, of course, deeply aligned with the agile and XP principles Beck has championed for decades, but applied now to something bigger than a codebase — applied to your entire career trajectory and professional identity.

There is a phrase Beck uses that sticks: "bless and release." It is the idea that you can honor the skills and practices that got you here while simultaneously acknowledging they may not be what carries you forward. For anyone who has invested years mastering a particular framework, language, or architectural approach, this is a genuinely difficult emotional exercise. But Beck frames it not as loss, but as liberation.

The piece is also notable for what it does not do. It does not pretend to have a roadmap. It does not offer a tidy five-step plan for thriving in the age of AI-assisted development. It simply says: if you still care, keep showing up and keep experimenting. That is the whole message, and honestly, in a landscape saturated with confident predictions and hot takes, the humility is the point.

The subtext, of course, is AI. While Beck does not dwell on it explicitly in this particular piece, the context is unmistakable. When he talks about old skills losing leverage, he is talking about a world where large language models can generate code, where architectural patterns that took years to internalize can be suggested by a tool in seconds. The question is not whether the world has changed — it is whether you are willing to adapt your relationship with your own expertise.

Key takeaways:

• Nobody has reliable answers about the future of software development, regardless of experience level
• The appropriate response to uncertainty is cheap, fast experimentation rather than clinging to established patterns
• "Bless and release" — acknowledge past skills while being willing to move beyond them
• Humility and curiosity are more valuable than confidence in a rapidly shifting landscape
• Staying engaged and trying things matters more than having the right strategy

Why do I care: As a senior frontend developer, this hits close to home. We have all felt the ground shift — whether it was the move from jQuery to React, from REST to GraphQL, or now from hand-written code to AI-assisted development. Beck is essentially telling us that the discomfort of not knowing is not a bug in our careers, it is the feature. The real risk is not experimenting with the wrong thing; it is refusing to experiment at all. If you have been quietly anxious about whether your hard-won expertise still matters, this piece will not give you answers, but it might give you permission to stop pretending you need them.

Nobody Knows