Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Developer Tea

Developer Tea artwork

AI-Proofing Your Skillset - High-Meaning, High-Specifity Vocabulary is the Path to Growth

Apr 29, 202631 minAudio

Why I'm Not "Picking a Fight" on AI: A listener asked if I'm intentionally stoking a flame war by treating agentic coding as a foregone conclusion. The honest answer is that I've used it, the data points one direction, and a show built around pretending otherwise would slowly drift away from reality - and away from being useful to you. Respecting the Misgivings, Without Getting Stuck in Them: Ethical concerns, skill atrophy worries, and questions about long-term effects are all legitimate. But the goal of this show is practical applicability, so we focus on mental models you can use Monday morning rather than litigating every angle of the debate. The "Minecraft" Principle: If I ask you to "build Minecraft," I've handed you several chapters of specification in a single word. That's meaning-rich abstraction - language that points at a huge amount of shared context with very little token cost. Meaning-Rich AND Specific: "Human history" is meaning-rich but uselessly broad. "Block-building game" is specific but loses fidelity. The sweet spot is vocabulary that is both compact and unambiguous - sitting in the top right of the meaning-density / specificity graph. A Real Example - Strategy Pattern: When working on authorization rules, I didn't want a pipeline. Instead of describing base classes, shared interfaces, and parallel execution to the LLM, I used the words "strategy pattern." Three words did the work of three paragraphs, and the output landed where I wanted it. Vocabulary as Leverage: Named patterns, named algorithms (Monte Carlo, etc.), named architectural concepts - these act like compressed pointers. The more of them you genuinely understand, the higher the leverage of every prompt you write and every conversation you have with another engineer. How to Build This Vocabulary: Have conversations with senior engineers. Ask an LLM what patterns are at play in a codebase, which ones you're using incorrectly, and which ones you're tricked into thinking you're using. Learn the abstraction layer that sits one step above your day-to-day implementation work. The Asterisk - Shared Context Required: This only works when both sides know the term. Public, well-documented concepts (patterns, papers, algorithms) translate immediately to LLMs. Private or organization-specific concepts need to be loaded into context - via CLAUDE.md, AGENTS.md, or skills - before that compression kicks in. Episode Homework: Pick one area of your current codebase. Ask an LLM to name the patterns in play, the patterns you're using incorrectly, and the ones you might be missing. Use that conversation to add at least one new piece of meaning-rich vocabulary to your working set. ๐Ÿ™ Today's Episode is Brought To You by: Unblocked Your coding agents have access to your code base - and probably more - but access isn't the same as context. Agents can't reason well across MCPs on their own, they don't know your architecture decisions, and they don't know which docs are reliable versus written by someone in their free time two years ago. โ— Unblocked is the context layer your agents are missing. โ— It synthesizes your PRs, docs, Slack messages, and Jira issues into organizational context that agents actually understand. โ— That means better plans, higher quality code, fewer tokens, and fewer correction loops. โ— Whether you're running Claude Code, Cursor, Codex, or any agentic workflow, it's worth a look. Get a free three-week trial at getunblocked.com/developertea. ๐Ÿ“ฎ Ask a Question If you enjoyed this episode and would like me to discuss a question that you have on the show, drop it over at: developertea.com. ๐Ÿ“ฎ Join the Discord If you want to be a part of a supportive community of engineers (non-engineers welcome!) working to improve their lives and careers, join us on the Developer Tea Discord community today! ๐Ÿ—ž๏ธ Subscribe to The Tea Break We are developing a brand new newsletter called The Tea Break! You can be the first in line to receive it by entering your email directly over at developertea.com. ๐Ÿงก Leave a Review If you're enjoying the show and want to support the content head over to iTunes and leave a review!

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. What Kind of Engineers Are Getting Hired Right Now?

    Nov 20, 202615 minAudio

    What kind of engineers are getting hired today? Some of what hiring managers look for hasn't changed at all, but the reasons it matters have shifted, and the importance of those traits has grown. In this episode I talk...

    Credit the people on this episode

  2. Finding A Way Through Forced Change of AI Transformations

    Nov 14, 202618 minAudio

    You likely chose most of the changes in your career yourself, and many engineers now feel AI-driven change is being forced on them. In this episode, I talk about why that shift feels so personal, and how three ideas can...

    Credit the people on this episode

  3. Three Default Thinking Modes That Can Screw Up Your Planning and Vision

    Nov 5, 202617 minAudio

    Your brain is constantly trying to simplify the world. It takes a snapshot of what it sees, builds a picture that makes sense, and then works from that picture. Most of the time this works well enough. But when we plan...

    Credit the people on this episode

  4. Signs You May Have a Regressive Mindset

    Oct 24, 202617 minAudio

    Keeping up has always been part of the job for software engineers, and with AI it's harder than ever. In this episode, I talk about two signals that you, your coworkers, or the people you manage might have a regressive...

    Credit the people on this episode

  5. How History Can Inform a Dynamic Understanding of Technological Revolutions Mirroring this Moment In Software Engineering

    Sep 30, 202617 minAudio

    You're tired of hearing that you need to pick up AI, so today I'm not going to add to that pile. Instead, we'll look back at two moments in history that look a lot like this one: the arrival of Fortran in the 1950s, and...

    Credit the people on this episode