Podcasts about developer tea

The skills problem isn't going anywhere — it's just wearing new clothes. In this episode, I unpack how the lessons we learned decades ago (limiting work in progress, the theory of constraints, test-driven development) are coming roaring back as the fundamentals that will carry you through the agentic shift. The bottleneck has moved, and knowing where it went changes how you should work. A lot of what we're learning about building with agentic tooling isn't new at all — it's a re-emphasis on lessons software engineers learned twenty years ago, just arriving in a new form. In today's episode, I walk through why the fundamentals are becoming more important than ever, why so many of us feel scattered despite having the most powerful tooling we've ever had, and where the real bottleneck in software delivery has quietly moved. My goal isn't to convince you that your job is now babysitting AI — it's to show you which parts of the work are still squarely yours, and how older principles can make you faster and more confident right now. Limiting Work in Progress Is Back: Just because you can spin up fifty agents doesn't mean you should split your focus across fifty things. Orchestrated fan-outs are powerful, but a human juggling agents across hiring, on-call, and a project all at once still pays the same old context-switching tax — and the quality drops while the speed never improves. Work Deeper, Not Wider: Instead of spreading yourself shallowly across more tickets, run multiple sessions on the same domain. Write a competing or adversarial version that critiques your assumptions, develop better documentation, or capture what you're learning as a reusable skill. Depth beats breadth. The Scattered-Engineer Epidemic: Engineers are burning out faster, not slower. We have the capacity to push more through the pipeline, so we're getting handed (or choosing) more than we can carry. Reducing parallelism often holds your delivery speed steady while dropping your cycle time and raising quality. The Theory of Constraints, Revisited: Treat your software development lifecycle as a pipeline with a bottleneck — and if you can't find one, you've optimized one part too far. Writing code used to be the choke point, so we spent enormous energy de-risking work before it ever reached an engineer. The Bottleneck Has Moved: When production gets cheap, it's no longer worth heavily de-risking upstream — which is why engineers are picking up more experimental, proof-of-concept, discovery work, and product folks are prototyping with these tools too. The new constraint isn't writing the code; it's verifying the agent didn't ship something broken. Verification Scales With Your Effort: The more an agent produces, the bigger the pile of PRs, MRs, and outputs waiting on human review. That backlog is the new bottleneck — and skepticism is creeping in because we're not even sure our tests are sufficient to verify what the agent built. Why TDD Fits This Moment: The honest question isn't "Can I trust the agent?" — it's "What verification loop do I need to build so I can trust it more?" Clear requirements feed a clear testing loop: write the failing test, let the agent write the code to turn it green, and you bridge the gap between requirements gathered and requirements met. It's not as simple as "go write a test," but it's a strong fit for where we are right now. Episode Homework: Go dig into the fundamentals — limiting WIP, the theory of constraints, test-driven development. Find the old lesson that still applies to your workflow today, bring it to your team's flow, and email me about what you discover.

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. If you've been following along with our recent focus on durable skills, you know we've been hunting for the abilities that translate beyond this month, this year, or whatever AI does to our industry next. Today's skill doesn't have a tidy name you can search for — it's softer than that. Jonathan calls it "principle-oriented thinking": the habit of deconstructing the labels we put on things to understand their core components, properties, and capabilities. It's how NASA engineers turned a sock into a water filter on Apollo 13, and it's how forward-thinking engineers are reframing what AI can actually do rather than jamming it into a predetermined slot. Labels Are Useful Shortcuts — Until They Aren't: Every label, from "software engineer" to "sock," carries baggage, heuristics, and presupposition. That's not a flaw — labels are how we move through the world quickly. But when a label is the only lens you have, it quietly caps how much value you can get out of the thing you're looking at. The Apollo 13 Sock: When the crew needed to fix a life-threatening problem with mismatched parts, the engineers on the ground had to forget what a sock was for and ask what it actually is — a piece of cloth with tensile strength, flexibility, and filtering properties. Strip the assumption that it goes on a foot, and a whole new set of uses opens up. Stop Slotting AI Into Old Roles: The common move is to take one responsibility — coding, debugging, refactoring — hand it to an agent, and keep everything else the same. That works, but it's low-leverage. The more powerful approach starts by asking what the agent is fundamentally capable of, then rebuilding the workflow around those raw materials. See Things as Materials, Not Fixed Functions: When you deconstruct out from under a label, tools and concepts start to look like craftable raw materials. You can then combine them in new, valuable ways they haven't been combined before — alloying old methods with new capabilities to create properties neither had on its own. Reason From Properties, Not Personas: Ask what the actual properties of an LLM are. Non-determinism isn't a bug to apologize for — it's a property you can exploit. The existence of many different models is a property too, which is exactly what makes adversarial review possible. That's principle-oriented thinking applied to agents. Extend the Latticework: Charlie Munger talked about a latticework of mental models that weave together rather than sit in isolation. The durable skill isn't quarantining your concept of "AI" off to the side — it's grafting a new section onto the existing tapestry and letting it reshape everything you already understood. Episode Takeaway: Look at how you spend your time and ask new questions of it. What is the material here? What kind of thinking does the agent actually do? What can a human do that an LLM can't — and the other way around? That's how you avoid believing a sock is only ever good for a foot.

A lot of what we've been talking about lately is durable skills — the abilities that last regardless of how our tools and tech environment change. In today's episode, I want to step back from the AI conversation and focus on one of the most durable skills of all: feedback. We've all been on both the giving and receiving side, and we can probably count on one hand the times someone gave us feedback that genuinely drove a good change — that left us wanting to do better without feeling torn down. So how do we accomplish that kind of feedback, on both sides of the table? That's what this episode is all about. Start With Your Goal, Not Your Frustration: Before you give feedback, recognize that your gut impulse often comes from a negative emotion — frustration, feeling slighted, feeling disrespected. Those feelings are valid signals that something is off, but they aren't a sufficient reason to give feedback. Effective feedback is goal-oriented: ask yourself what you actually want to change before you say a word. Premature vs. Mature Feedback: Premature feedback is really about making sure someone knows how you feel — which can quietly turn into an attack so they share your pain. Mature feedback is forward-looking and aimed at improvement. Venting may give you catharsis in the moment, but if the behavior worsens or the relationship is damaged, the net outcome is negative. Why Asking for Feedback Changes Everything: Even hearing "can we meet for ten minutes, I have some feedback" measurably raises your heart rate and pushes you into a defensive state. But when you ask for feedback, your mind and body register that you're in control — same information, completely different physiological response. Make It Behavior-Based and Specific: Good feedback is about observable behavior — what a camera would have caught — not someone's core identity. If your feedback violates a person's self-concept (painting a competent engineer as incompetent), they have to change who they believe they are to accept it, and that gap rarely gets bridged in a 30-minute call. Use a Model — But Add the Intervention: The popular SBI model (Situation, Behavior, Impact) is a strong backbone, but it stops short. Don't just describe the past — partner with the person on what comes next. Think of it as SBI + Intervention: what can you commit to trying differently so the impact changes? That's where feedback becomes coaching. The Netflix Four A's: Aim to assist, make it actionable, show appreciation, and accept or discard. Lead with the intent to help, get specific about the behavior, appreciate the person's willingness and intent, and recognize that not every piece of feedback will be useful — both sides get to keep what's valuable and let the rest go. Receiving Feedback Well: When someone hands you messy, un-modeled feedback, you can walk them through the framework — "help me understand the situation, what behavior did you see, what was the impact?" People respect that you're engaging, shift into problem-solving mode, and give you more actionable feedback as a result. Episode Homework: Pay attention to patterns over time. One piece of feedback shouldn't be attached to your identity — but three or four that point in the same direction are worth introspecting on. Career development and feedback are two sides of the same door; walk through it and you grow.

Right now, the questions we have about our careers feel existential. We keep coming back to the same theme: how do you prepare for an industry that's changing this fast, and what mindset actually works in this new reality? One skill keeps surfacing as the answer — your ability to update your own mental models. In today's episode, I want to push on that further and put some of software engineering's most beloved thinking models under scrutiny. Some of these models served you well for years. Some of them now deserve to be challenged, replaced, or thrown out entirely — and learning how to tell the difference is itself the skill that will determine whether you hit a ceiling. Move Past "So What" Questions: The typical engineering objection to agentic coding is that it produces quality issues. But the people deciding to adopt these tools already accept that. Our job is to stop arguing the surface-level point and start asking the real one: so what do we actually do about this new economic reality? The Economics of Acceptable Loss: Abstraction always leaves something to be desired. An agent's code may not match what a staff engineer produces by hand over months — but that gap is usually an acceptable trade against shipping something two, three, or four times faster. Understand the cost-benefit picture instead of pretending the cost doesn't exist. Abstraction Has Always Done This: This isn't new. The calculator dissolved the specialization once required for complex math. Spreadsheets commoditized ledgering and accounting. Agentic coding is the same pattern arriving for our work — making something that required deep specialization suddenly far more accessible. Roles Are Blurring: As these generic tools raise everyone's ability to abstract, the boundaries soften. You're already seeing product managers open pull requests and engineers making product decisions. The neat lines around "what an engineer is" are not as fixed as they used to feel. Why Your Hard-Won Wisdom Is the Target: If you've spent years in this industry, your models were bought with blood, sweat, and failed projects. That experience is real wisdom — and it's exactly what I'm asking you to be willing to challenge, because the thing that always worked for you is the thing most likely to become a ceiling. This Skill Survives Either Way: Even if you think AI is mostly hype and I've been infected by it — fine. The ability to challenge your pre-existing models is a critical skill regardless. It's how you keep growing as you get more senior instead of repeating what used to work. Models Are Approximations: The whole point of a model is to approximate the reality around us. That's their value and their limitation. When the underlying reality shifts this dramatically, holding tightly to an old approximation stops being wisdom and starts being a liability.

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. Two Surfaces Coming Into Contact: Picture your knowledge, skills, and toolset as one surface, and the actual state of the art as another. We've always known the surface area we could learn far exceeds what we can learn, which forces us to place bets on a learning strategy. What's changing is how fast that second surface is moving underneath us. Improvement by Practice vs. Improvement by Change: Practice is wielding what you've already adopted—smoothing out errors, building muscle memory, refining what you already know. Adaptation is fundamentally folding something new into your repertoire. Both are real forms of improvement, but they are not interchangeable. The Cornerstone Mistake for Senior Engineers: Later in your career, the time you spend adapting naturally goes down as you settle into practice. The biggest error I'm already watching engineers make is moving too quickly toward practice when the industry is loudly calling for adaptation instead. Inspect and Adapt—at the Right Altitude: Sprint retros were never really about getting marginally better at the thing you already do. The intent of "inspect and adapt" is to step up one level and examine the system. The trap is treating adaptation like a minor refinement—getting a little better at prompting—when it should mean asking whether you're thinking about prompting in the wrong way entirely. Question the Ratio, Not Just the Output: Real adaptation looks like asking whether you have the right mix of human and agent on a problem. Are you leaning on the agent for things you shouldn't, or failing to lean on it for the things you should? Have you genuinely thought about how sub-agents or an agent team are working the problem you're producing? A Spectrum, Not a Binary: On one end, you make micro-adjustments to your refinement process. On the other end of experimentation, you ask whether refinement—or even having engineers plan the work—is the right thing at all. The point isn't that practice is dead; it's that the industry is changing fast enough that the adaptive end of that spectrum deserves far more of your attention than it used to. Episode Homework: Take something you currently treat as a practice problem—"how do I refine tickets faster?"—and step up a level. Ask the adaptive version of the question instead: "Is refinement even the right thing anymore?"

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. Don't Just Bring Star Stories — Bring Failure Stories: Interviewers don't only want to hear how you succeeded. They want to know what you do when the pressure's on and things fall apart. If every story you tell is a highlight reel, there's a built-in social signal that you're hiding something. Get comfortable telling the other kind of story. Identify the Real Problem, Not the Proximal One: The most common failure story I hear in interviews is "the knowledge transfer was bad" or "the docs weren't good." That's not wrong — it's just incomplete. The senior mindset asks why that happened. Why didn't we have docs? Why was context insufficient? Walk it back until you hit something actionable but not too abstract. The Systemic Diagnosis is the Leveled-Up Answer: Fixing the proximal cause fixes this instance. Fixing the root cause fixes the system that keeps producing instances like this. When you connect what you learned to a systemic adjustment, you stop sounding like someone who survived a bad project and start sounding like someone who improves the organization around them. Ownership Means Owning the Outcome, Not the Task: Use the homeowner metaphor. A homeowner doesn't personally fix every leaking pipe — but the outcome of the home is theirs. As an engineer, your scope of ownership has expanded dramatically in the agentic era. You're now responsible for outcomes of code you may not have even read, and the deciding skill is how you carry that responsibility. The Word to Pair With Ownership is Relentlessness: Not in an anxious, burn-yourself-out way. Relentlessness means following a thread to its natural end — through escalation, through asking the next question, through finding the right person if it's not you. It's the antidote to "I'll let someone else handle it" syndrome. You Don't Have to Do It All Yourself: Relentless ownership is not "carry every task across the finish line personally." If you're not qualified, the owner's job is to find who is, communicate risk to stakeholders, and keep the trail alive until the outcome is resolved. That's the differentiator between a senior thinking engineer and a junior one working through assigned tickets. Failure Is Usually a Lapse in Ownership: If you make a list of five things you've failed at (and you should), you'll often find the through-line isn't lack of skill — it's that you stopped escalating, stopped following up, stopped staying with the thing until it was actually resolved. Episode Homework: Write down five real failures. For each one, ask: where did I stop being relentless? What system produced this outcome — and what would I change upstream next time?

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. The Replication Crisis, Briefly Explained: Understand the difference between reproducing a study (re-running the analysis on the original data) and replicating one (recreating the study from the ground up), and why a surprisingly large portion of well-respected psychology research, including studies cited in Thinking Fast and Slow, doesn't hold up under scrutiny. Base Rates Matter: Kahneman didn't pick uniquely bad studies. If you randomly sampled from the broader academic literature, you'd hit the same failure rate. The lesson isn't about one author — it's about how we evaluate any body of knowledge. The Beginning of Infinity Framework: Drawing from David Deutsch's book, explore the idea that all progress is rooted in the assumption that we are fundamentally incorrect, and that improvement comes from continually building better explanations on top of incomplete ones. Beliefs as Calibration, Not Truth: Your beliefs about what makes a good engineer, what makes good code, or what makes a good career move are not eternal truths. They are calibrations to your current reality, and that reality is changing fast. The Ego Trap of Old Beliefs: Notice the very human, very subtle pull to defend things you previously argued for — not because they're still right, but because admitting otherwise creates a discontinuity with your former self. This is one of the biggest blockers to learning. Two Competing Explanations of AI Adoption: Walk through a worked example of holding two predictions about AI in tension and asking honestly which one better explains the reality you're seeing — at both a macro industry level and the micro level of debugging a system. Moving Goalposts Aren't a Conspiracy: A lot of what feels like shifting goalposts in our industry is just goalposts moving on their own. A big part of our job as engineers is figuring out where they are now and predicting where they're heading next. Episode Homework: Pick one belief you hold strongly about your work — about what makes a good engineer, about a tool, about a process. Try to deconstruct it into its parts and ask whether a better explanation exists for what you're actually seeing.

Hey everyone, welcome to today's episode of Developer Tea. This is the second part of my interview with Bryan McCann, the CTO at you.com. If you haven't listened to Part One, I'd encourage you to go back, as it provides crucial context for our continued discussion. In this episode, we dive into how you can think about relating to and integrating the massive changes that AI is bringing to your job, whether you are a software engineer, manager, director, or product professional. Bryan and I discuss his interests beyond research, including art and organizational design.Explore the two primary paths for developers in the long run: specializing as managers of AI tools (like a product manager with engineering insight) or striving to be better than AI at building better versions of AI itself (the "neurosurgeon" type).Understand why refining your intuitions about what should be built becomes increasingly crucial as automation makes execution easier.Examine how conceptual biases often become the bottleneck when interacting with powerful AI tools, such as focusing on very narrow tasks for a broad tool.Learn how to approach AI failures: treat a failed output as an opportunity to dig in and figure out why, perhaps by asking the AI to write a better prompt or identifying a fundamental missing capability that could become a great startup idea.Conceptualize AI as the earliest versions of magic, where the manipulation of symbols (like embeddings) allows us to extend our influence into the world in a flexible and powerful way.Discover principles of organizational design by studying how neural networks learn, focusing on strong information flow, skip connections, and aligning with the objective.Consider the idea that the next phase of human development might involve emulating AI's learning mechanisms (rather than expecting AI to become more human-like) to unlock the next phase of humanity and continue our search for meaning.Hear Bryan's final piece of advice for listeners: focus on learning and working on things you are passionate about that will have the highest possible impact.

Hey everyone and welcome to today's episode of Developer Tea. It's been quite a while since I've had a guest on the show. Today, I'm joined by Bryan McCann, CTO at you.com. We dive into a wide-ranging discussion, exploring the philosophical origins of his career—from studying meaning and language to working in very early AI research. This discussion is less advice-heavy and more focused on kind of theory and discussion. I hope this is insightful for you and helpful as you crystallize your own philosophies on these subjects.Explore the philosophical journey that led Bryan McCann from being a philosophy major interested in meaning to pioneering early AI research. Bryan views his current work as an extension of those original philosophical questions.Discover how Bryan shifted from hitting a dead end in "armchair philosophy" to using computational tools to study language and try to make machines that could create meaning.Understand why Bryan believes that meaning, in the sense he originally sought it, is an innately human thing, tied to purpose and the narratives we use to shape our sense of reality.Discuss the profound realization that AI breakthroughs might be akin to discovering electricity, suggesting we are tapping into a fundamental framework of meaning or connection that has always existed.Examine the concept of super intelligence and the "flywheel effect," where AI accelerates research and development, building better versions of itself and potentially surpassing the classic anthropomorphic vision of machine intelligence.Explore Bryan's other interests, including organizations, people, and art, which he sees as continuing the uniquely human search for meaning.Consider the idea that humanity's constant need to differentiate itself from machines may simply be a mechanism for survival, enabling our continued dominance.

Today, we celebrate 10 years of Developer Tea. I wouldn't be doing this podcast without you listening. Especially if you have been listening for many years, thank you!

After today's episode, your resumé is going to get better! In this episode I will share the biggest mistake and the best advice I've ever received about building a great resumé. This will take some work from you, but I hope you walk away from this episode feeling like you have the right mindset to improve your resumé drastically, and land more interviews, ultimately leading to better job opportunities for the Developer Tea audience!

Today Marks 9 Years of Developer Tea.Thank you all for your support, and your friendship. I wish you all well on your journey, and may you find clarity, perspective, and purpose. (Don't worry, we aren't going anywhere!)

Developer Tea has been around for 8 years. Thank you so much for your incredible support over these years!In today's episode we discuss how it feels to be wrong.

First off, thank you for an incredible 7 years! Our listeners and sponsors make it possible to do this show, and I'm incredibly grateful for every one of you.In this episode, we continue our discussion with two more exercises for making meaningful and purpose driven behavior change resolutions.

Developer Tea is a podcast for developers designed to fit inside your tea break. Jonathan Cutrell started the podcast in 2015 and now has hosted over 1000 episodes. We interview Jonathan Cutrell about the early days of Developer Tea, Spec.fm, developer content, and more. Links https://jonathancutrell.com https://twitter.com/jcutrell https://spec.fm/podcasts/developer-tea https://designdetails.fm https://spec.fm https://twitter.com/chantastic https://developertea.com https://twitter.com/DeveloperTea https://www.charitynavigator.org Contact us https://podrocket.logrocket.com/contact-us (https://podrocket.logrocket.com/contact-us) @PodRocketpod (https://twitter.com/PodRocketpod) What does LogRocket do? LogRocket combines frontend monitoring, product analytics, and session replay to help software teams deliver the ideal product experience. Try LogRocket for free today (https://logrocket.com/signup?pdr). Special Guest: Jonathan Cutrell.

The most critical career mistake you can make isn't a secret. Are you in control? If you aren't driving your career, who is?What if the best thing you could do was nothing?Not indefinitely, of course - but often, we intervene in the world when the right choice is to do nothing.This is uncomfortable because it is unfamiliar, but might be the most critical change you can make in your thought process.✨ Sponsor:  AroundThank you to Around for their support of Developer Tea!More people are working remotely than ever. And that means more video meetings than ever. But it doesn't have to be a drag with bad UX, fatiguing full-screen takeovers, and everything we hate about video meetings. Around is changing the game with a tool made specifically for remote teams to get work done together.Check out their awesome features (like AI camera framing, auto-filters, and much more) at Around.co!

Joel Beasley is the host of Modern CTO, a podcast with guests coming from IBM, Microsoft, Nasa, Reddit, and hundreds of others. Joel and I have wanted to have this discussion for a long time, and we finally found the right overlap to do it!You can learn more about Modern CTO at https://moderncto.io and listen to this episode in the alternate podcast universe here.Thanks for joining me on Developer Tea, Joel!✨ Sponsor:  Command Line HeroesCommand Line Heroes is a podcast that tells the epic true tales of developers, programmers, hackers, geeks, and open source rebels who are revolutionizing the technology landscape.Check out Command Line Heroes wherever you get your podcasts!

Joel Beasley is the host of Modern CTO, a podcast with guests coming from IBM, Microsoft, Nasa, Reddit, and hundreds of others. Joel and I have wanted to have this discussion for a long time, and we finally found the right overlap to do it!You can learn more about Modern CTO at https://moderncto.io and listen to this episode in the alternate podcast universe here.Thanks for joining me on Developer Tea, Joel!

Model Manager episodes of Developer Tea are dedicated to helping engineering managers find models of thinking that improve their approach to management.Great managers don't attempt, in vain, to control the actions of others. Great managers take advantage of the unique parts of being a human: that they can self-improve through learning and change, and they can create environments that encourage others to do the same.✨ Sponsor:  Command Line HeroesCommand Line Heroes is a podcast that tells the epic true tales of developers, programmers, hackers, geeks, and open source rebels who are revolutionizing the technology landscape.Check out Command Line Heroes wherever you get your podcasts!

Model Manager episodes of Developer Tea are dedicated to helping engineering managers find models of thinking that improve their approach to management.Processes create uniform approaches and uniform outputs. But what is the output you should care about the most? In this episode, we'll discuss why human behavior is the primary and most critical output of any process.✨ Sponsor:  Command Line HeroesCommand Line Heroes is a podcast that tells the epic true tales of developers, programmers, hackers, geeks, and open source rebels who are revolutionizing the technology landscape.Check out Command Line Heroes wherever you get your podcasts!

In today's episode, we welcome back to the show Ali Spittel! Ali is a developer advocate at AWS Amplify. So, naturally in this episode, we discuss topics around what it means to be a developer advocate! Ali has a passion for making code accessible and fun, and you'll hear that in this episode.✨ Sponsor: LinodeThank you to long time sponsor and friends of the show Linode for sponsoring today's episode!Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier.Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

In today's episode, we welcome back to the show Ali Spittel! Ali is a developer advocate at AWS Amplify. So, naturally in this episode, we discuss topics around what it means to be a developer advocate! Ali has a passion for making code accessible and fun, and you'll hear that in this and the next episode.✨ Sponsor: LinodeThank you to long time sponsor and friends of the show Linode for sponsoring today's episode!Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier.Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

As we transition together through strange periods (whether at large scale like the present moment, or at a smaller scale within your organization or culture), the way we look at each other changes. This observation shift brings behavior change - that's what we're talking about in today's episode.✨ Sponsor: LinodeThank you to long time sponsor and friends of the show Linode for sponsoring today's episode!Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier.Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

Uncomfortable places may feel dark, but they often carry the most illuminating lessons. In today's episode we discuss using these darker moments as a compass to find your values.✨ Sponsor: LinodeThank you to long time sponsor and friends of the show Linode for sponsoring today's episode!Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier.Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

Today's guest is Dan Pupius, CEO and co-founder of Range. Dan cares deeply about creating products that make healthy and sustainable workplaces a common occurrence. We talk in depth about designing constraints and opinions into products with the long term in mind.✨ Sponsor: LinodeThank you to long time sponsor and friends of the show Linode for sponsoring today's episode!Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier.Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

AndrewBeeple: https://www.theverge.com/platform/amp/2021/3/11/22325054/beeple-christies-nft-sale-cost-everydays-69-millionDungeons & Designers: http://dungeonsanddesigners.com/MadMaxMiniatures: https://www.instagram.com/madmaxminiature/MMM Etsy: https://www.etsy.com/shop/MadMaxMiniatureLaurenBojack Poster, Eric is Eric: https://www.instagram.com/erik_as_erik/Botanica Tarot Deck: https://www.instagram.com/p/CMIa39ypEMa/Kevin Jay Stanton: https://linktr.ee/kevinjaystantonThe Drawing Board: https://youtu.be/OIfL69ps15gWolfwalkers: https://www.cartoonsaloon.ie/The Grammys, W.A.P. Performance: https://www.youtube.com/watch?v=UnBZLFB7kLoPatrickAround: https://www.around.co/Marriage or Mortgage: https://www.imdb.com/title/tt14037542/Developer Tea: https://developertea.com/Jonathan Cutrell: https://jonathancutrell.com/

Much of our attention and effort is used trying to remove human influence and finding "raw" truth. Today, I want to ask you to do the opposite of that.✨ Sponsor: LinodeThank you to long time sponsor and friends of the show Linode for sponsoring today's episode!Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier.Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

There is far more information that we ignore than what we pay attention to. This selective attention is important to understand as both a necessary skill and a potential pitfall. ✨ Sponsor: LinodeThank you to long time sponsor and friends of the show Linode for sponsoring today's episode!Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier.Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

Your actions speak louder than words. You already know that. But have you asked yourself what your actions are saying about who you are?✨ Sponsor: LinodeThank you to long time sponsor and friends of the show Linode for sponsoring today's episode!Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier.Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

It's hard to construct with deconstruction in mind. It's difficult to imagine designing for final shutdown. In this episode, we talk about the importance of transformation and change, and the ultimate reality of everything: it all ends, at some point. If we want to build better software and lead better lives, we should build with open eyes about the end. Today, we also celebrate the shutdown of Spec.fm, the podcast network Developer Tea has been a part of for over 5 years! ✨ Sponsor: LinodeThank you to long time sponsor and friends of the show Linode for sponsoring today's episode!Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier.Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

Becoming enlightened may not mean rising above everything. Instead, maybe it means zooming in. It's easy to believe that as we continue to get older, we care less and less about the details, and we care more about the "big picture." Interestingly, if you study individuals with high levels of excellence and experience, they tend to care deeply about the details and notice things others may not. This expansion of the current moment is the paradox of transcendence - only once we care deeply about the present moment, enough to notice the minute details, can we rise above it. ✨ Sponsor: Linode Thank you to long time sponsor and friends of the show Linode for sponsoring today's episode! Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier. Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

This week, we continue the discussion of learning in public with guest, Shawn Swyx Wang. Swyx is best known for being the Reactjs subreddit mod, and recently released the book, "The Coding Career Handbook". In this part 1 with Swyx, we discuss his background and how he got started in engineering. 

Over the next couple of episodes of this show, we're talking about learning and teaching in public. Today, we sit down with Kent C. Dodds. Kent has created some of the most important teaching materials for React developers at epicreact.dev. In this part 1 with Kent, we talk about the roots of why Kent cares so much about teaching. 

Have you ever thought about building something because you assumed the product already existed? In today's episode, we dig into this question with Keith Pitt. Keith is the CTO and co-founder of Buildkite and in this part 1 of our two part interview, we dig into starting Buildkite and Keith's journey in development.

In today's episode we sit down with Venkat Venkataramani to talk about his role as a co-founder and CEO of Rockset.In this part 1 of our two part interview, we dig into leadership mindset and leading  a company during difficult times. 

We've been talking about making decisions and in today's episode, we're going to focus on the status quo. Something happens to each of us when we think about ourselves with relation to other people. We are much more likely to image that we are better than or on par with the average person. But exactly how do we measure the status quo and how does our assumption effect our decision making?✨ Sponsor: LinodeThank you to long time sponsor and friends of the show Linode for sponsoring today's episode!Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier.Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

In today's episode of Developer Tea, we're talking about what it means to be right about something.  ✨ Sponsor: Monday.comThanks to Monday.com for supporting the show!Ever dreamt of building an app that impacts the daily lives of hundreds of thousands of people? Well now is your chance! Monday.com is an online teamwork platform that just launched a contest to develop apps for the 100,000 teams that use monday.com for their daily work. And the prizes? They’re insane. With $184,000 in total prizes, they are giving away 3 Teslas, 10 MacBooks, and more!Check it out at monday.com/DEVTEA 

In today's episode, we're talking about things that we choose not to be good at.   ✨ Sponsor: LinodeThank you to long time sponsor and friends of the show Linode for sponsoring today's episode!Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier.Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

On today's episode of Developer Tea we're joined by Ravs Kaur. Ravs is the CTO at Uplevel and in the next two episodes she joins us to talk about leadership and management.  

In today's episode of Developer Tea we're joined by Ravs Kaur. Ravs is the CTO at Uplevel and in the next two episodes she joins us to talk about leadership and management.  

✨ Sponsor: LinodeThank you to long time sponsor and friends of the show Linode for sponsoring today's episode!Simplify your cloud infrastructure with Linode’s Linux virtual machines and develop, deploy, and scale your modern applications faster and easier.Listeners of Developer Tea can now enjoy $100 in free credit! You can find all the details at linode.com/developertea.

Today's guest is Jonathan Cutrell - Director of Engineering at PBS & host of the Developer Tea podcast.In this episode we discuss:How and why he started Developer TeaThe why behind things we do as developersWhat drives the actions we takeThe psychology of remote workingHierarchies of developer rolesand much much more!

Mezi návrhy na témata k povídání, které od vás dostáváme, se často opakovalo podcastování - jak to děláme, proč to děláme atd. Aby to nebyla jenom sterilní debata nás dvou, domluvili jsme se s podcastem Vzhůru dolů a natočili společný díl. V tomto letním, netechnickém vydání si s Martinem Michálkem a Robinem Pokorným povídáme o tom, co nás motivuje, jak přistupujeme k nahrávání, kam publikujeme atd. Sami jsme byli překvapení, jak se naše pohledy mohou lišit. Těšíme se na vaše komentáře, přání i připomínky, které můžete psát na info@dotnetpodcast.cz. A pokud se vám díl líbil, budeme rádi, když nám koupíte kávu na https://www.buymeacoffee.com/dotnetcezet. Nově nás najdete i na Instagramu https://www.instagram.com/dotnetpodcastcz. Odkazy: - Podcast Vzhůru dolů: https://www.vzhurudolu.cz/podcast - Hovory od křivého stolu: https://channel9.msdn.com/Shows/Hovory-od-kriveho-stolu - Anchor: https://anchor.fm/ - Streamyard: https://streamyard.com/ - Developer Tea: https://open.spotify.com/show/02fM1JHpt9HmHGp482K71b - Buchty: https://wave.rozhlas.cz/buchty-6669798 - Reply All: https://gimletmedia.com/shows/reply-all - 38. díl - Vánoční kafíčko: https://www.dotnetpodcast.cz/episodes/ep38/ - 32. díl - Vigor: https://www.dotnetpodcast.cz/episodes/ep32/ - Darknet Diaries Podcast: https://darknetdiaries.com/ - Nahrávky ovčí babičky: https://open.spotify.com/show/2dlzesc0o8Oy9w2hN00dAw - Win2D Maze Game: https://github.com/microsoft/Win2DMazeGame - Win2D: https://github.com/Microsoft/Win2D Twittery atd.: - https://twitter.com/machal (Martin M.) - https://twitter.com/robinpokorny (Robin) - https://twitter.com/deeedx (Martin Š.) - https://twitter.com/madrvojt (Vojta) Pokud nechcete, aby vám unikla nová epizoda, odebírejte RSS: https://bit.ly/netcz-podcast-rss, sledujte nás na Twitteru: https://twitter.com/dotnetcezet nebo na Apple Podcasts a také na Spotify. Hudba pochází od Little Glass Men: https://freemusicarchive.org/music/Little_Glass_Men/

Jonathan Cutrell is Director of Technology at Whiteboard, an interactive design and development firm. He also hosts of Developer Tea podcast. We talked about his experience speaking at CSS Dev Conf, his podcasts, and Whiteboard.