The skills that survive every industry shakeup aren't the ones you can Google — they're softer, harder to name, and far more durable. In this episode, Jonathan explores principle-oriented thinking: the practice of stripping away the labels we attach to tools, roles, and even ourselves to see what something actually does at its core. It's the difference between handing your coding off to an agent and rethinking your entire workflow around what these new materials are truly capable of.

Feedback is one of the hardest skills in any career, and most of us have only experienced a handful of moments where it actually drove positive change. In this episode, Jonathan explores how to give and receive feedback that leads to real growth — starting with setting your ego aside, getting clear on your goal, and using behavior-based models like SBI and Netflix's Four A's. It's a durable skill that turns a contentious, dreaded conversation into a genuine pathway to career development.

If you're a software engineer right now, the questions you're asking about your career probably feel existential. We've been spending a lot of time on this show preparing for the changing industry—what skills matter, what mindset works—and one answer keeps surfacing: your ability to update your mental models is itself the critical skill. In today's episode, I push on that idea directly. Some of the thinking models that defined good software engineering for the last decade deserve real scrutiny now, and a few of them may deserve to be thrown out entirely. This is an uncomfortable ask, especially for those of you who earned your wisdom the hard way—but the engineers who can hold their hard-won models loosely are the ones who won't hit a ceiling.

If you're a software engineer right now, you likely feel like your world is changing overnight. We are writing half or less the amount of code that we wrote even a year ago, which represents a seismic, groundbreaking shift in our industry. For many of us, this career has always been engaging for deeply creative and intellectual reasons—and that excitement is still here. But our mental models of what it means to be a good engineer, and what it means to keep improving, have gone a little stale. In today's episode, I want to talk about a distinction that I believe will become the cornerstone mistake for seasoned engineers: confusing _practice_ with _adaptation_, and leaning on the wrong one at the worst possible moment.

If you've heard that your job in the agentic coding era is to "become a manager of agents," you may have noticed something doesn't quite fit. Most of us never trained to be managers, and frankly, that's not the role most engineers want. In today's episode, I unpack what that shift _actually_ means — it's closer to a tech lead or architect mindset — and zoom in on a specific interviewing and on-the-job skill that will help you stay employable: how you think about, talk about, and take ownership of failure.

What happens when you discover that a book that fundamentally changed how you think is built on a shaky foundation? In today's episode, I share my own struggle with the replication crisis surrounding Daniel Kahneman's *Thinking Fast and Slow*, and I use it as a springboard to talk about a much bigger skill: knowing how to update your beliefs when reality shifts underneath you. This isn't about throwing out science or losing trust in your heroes. It's about developing the muscle to replace old explanations with better ones — a skill that has never been more important for software engineers.

If you've felt like the show has leaned hard into agentic coding lately, today's episode opens with why: the realistic future of software engineering includes these tools, and pretending otherwise makes this show less useful to you. From there, I want to give you something practical — a transferable skill that will compound in value as LLMs get more capable, and that also makes you a stronger communicator with humans. The skill is learning to speak in **meaning-rich, high-specificity abstractions**.

Many engineers have built their careers on the belief that coding is their primary value — the flagship skill, the gate opener, the reason they get paid. But if AI can do a large slice of that implementation work, then coding-as-your-core-value leaves you in a very narrow place. In today's episode, I want to reframe how you think about your skills, and give you a simple three-part framework for deciding which skills are actually worth investing in as the industry shifts.

Your job is changing faster than ever, and it might be tempting to believe that chaos is simply the new norm. In today's episode, I want to push back on that idea. Part of your role as a senior engineer or leader is to make sure chaos doesn't win — not just to rein it in reactively, but to go on the offense and create order. We'll talk about one important way to do this: protecting the ceremonies on your team.

Your tool set isn't just a collection of utilities — it's the environment you live in every day, and it's shaping you whether you realize it or not. In today's episode, I explore two principles that senior engineers consistently apply to their workflows, regardless of which specific tools they're using. As our industry goes through one of the most rapid periods of change in the last 20 years, the engineers who thrive won't be the ones chasing every new tool — they'll be the ones who obsess over reducing friction in the work they do most often.