Skip to content
Episode from the podcast Developer Tea
Finding Leverage by Escaping Functional Fixedness artwork

Episode

Finding Leverage by Escaping Functional Fixedness

Released Friday, January 26th 2024 12 min

Show notes

About this episode

Finding leverage is difficult to do, but a lot of the reason for this is that we allow ourselves to fall into well-traveled cognitive pathways. If we reject the solution domain-set that comes to mind immediately, we may be able to consider options for solutions we had never considered. This larger solution set may also include a high-leverage option we had previously ignored. 📮 Ask a QuestionIf 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 DiscordIf 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 by visiting https://developertea.com/discord today! 🧡 Leave a ReviewIf you're enjoying the show and want to support the content head over to iTunes and leave a review! It helps other developers discover the show and keep us focused on what matters to you.

More from Developer Tea

All episodes

Finding A Way Through Forced Change of AI Transformations

18 min

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 help you face it: the Stoic principle that "the obstacle is the way," Nassim Taleb's antifragility, and the biological cycle of stress and adaptation. For most of my career, the changes I went through happened at my own pace. I picked what to learn, whether that was jQuery animations or the next framework, and each new skill felt like a superpower. Many engineers today will recognize that progression, and it's a big part of why we love this work. Now the AI-driven shift in our industry is changing that for a lot of people. The change isn't chosen anymore, and for many engineers it's scary. In today's episode, I talk about why this shift feels so personal, and I share a framework you can use to grow through it instead of avoiding it. Change You Chose vs. Change Chosen for You: A lot of what made software engineering rewarding was agency. We picked our tools, our learning paths, and often our jobs. Agentic engineering is taking away some of that choice, and it's worth naming that loss honestly. A Note for Engineering Managers: If you never went through this kind of progression as an engineer, this part is for you. Code is more than a convenient tool for your engineers. It's something many of them love. Like a blacksmith with a hammer they've used for 20 years, they may not want the "better" tool, and a purely rational argument about better tooling misses the human side of the conversation. The Obstacle Is the Way: Drawing from Ryan Holiday's book and the Stoic philosophy of Marcus Aurelius it's based on, consider treating the obstacle in front of you as the path forward instead of something standing in your way. Antifragility and Stress Adaptation: Nassim Taleb's Antifragile describes systems that are actually improved by stressors. The same pattern...

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

17 min

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 projects, set goals, or try to predict where something is headed, these default modes of thinking can lead us in the wrong direction. In today's episode, I cover three of these defaults: linear thinking, static thinking, and infinite or non-discrete thinking. I also talk about how they show up in your career and in the way engineering leaders set vision for their teams. Static Thinking and the Snapshot Problem: We tend to fix our beliefs about people very quickly, which is why first impressions carry so much weight. If someone acts a certain way in one meeting, we assume that's how they act in every meeting. This is closely related to the fundamental attribution error, where we treat a person's behavior in one moment as a permanent part of who they are instead of a response to their environment. Linear Thinking and Exponential Change: When something is changing, we assume it will keep changing at about the same rate. AI agents are a good counterexample. Research suggests their effectiveness roughly doubles on a timescale of a few months, and even if the exact numbers are off, the curve is exponential. That kind of growth is hard to picture intuitively, and it probably won't last forever. At some point it will likely level off into something closer to logarithmic. Where Our Intuition Comes From: Nonlinear patterns are all around us in nature. Think about how quickly heat rises as you move your hand toward a fire, or how loudness changes as you get closer to a speaker. But our social lives mostly involve slow, roughly linear change, and over the course of human history our minds have adapted to that kind of linear model. Your Career Isn't a Straight Line: Many of us expect our salary and growth to rise steadily, in steps, for our whole careers. That ex...

Signs You May Have a Regressive Mindset

16 min

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 mindset, which shows up as quietly avoiding the learning you need to stay current. Keeping up has always been part of being a software engineer, and right now it's harder than ever. A lot of us are tired, skeptical, or just overwhelmed by the constant stream of AI news, and it's easy to slide into habits that slowly cut us off from new information. In today's episode, I talk about two signals to watch for in yourself, your coworkers, or your reports that point to a regressive mindset. That's a pattern of avoiding progress and learning, often without realizing you're doing it. What a Regressive Mindset Actually Is: A progressive mindset doesn't require jumping on every new tool or throwing out your whole toolset. Constant upheaval isn't progress. What matters is that your understanding of the world keeps growing. The regressive mindset shows up as avoiding learning and leaning on defense mechanisms that shield you from more nuanced information.Signal #1: Avoiding Information by Category: Watch for the moment you click away from an article or video just because it mentions AI or agents. You don't have to read everything, but if you're skipping things purely because of the subject, it's worth figuring out why. Fatigue might mean you need a break. Skepticism or discomfort is a different story.The Ostrich Effect: Avoiding uncomfortable information is a lot like sticking your head in the sand. It feels protective, but over time it leaves you behind and out of touch with what it takes to stay competitive as the industry changes.What Is Your Alternative Path?: If your plan is to keep avoiding this information, ask yourself honestly what that looks like a year or five years from now. I'd argue that avoiding it forever just isn't possible.Signal #2: Tying a Con...

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

17 min

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 the spread of autopilot in commercial aviation. Both show how new abstractions change the shape of our work without being purely good or purely bad. You've heard plenty of engineering leaders tell you to use more AI and more agents, often in a way that seems out of touch with your day-to-day work. I'm not going to add to that today. Instead, I want to share some history. If it feels like our industry is in a completely unique moment, it helps to look at earlier times that had a similar shape. In this episode, I look at the early skepticism around Fortran and the effects of autopilot on pilot skill. Then I explain why a dualistic "good or bad" view of AI leaves out most of what is actually happening. Fortran and the Skeptics: In the 1950s, Fortran became widely known as the first high-level language, generating machine code so programmers didn't have to write it by hand. Skeptics doubted it. John von Neumann reportedly questioned why a serious scientific machine should do "clerical work," and many engineers didn't trust the generated code. The Critics Were Partly Right: Early generated code wasn't very good and needed a lot of massaging. The Fortran team didn't go back to the old way. They put their effort into improving the new abstraction. The criticisms of the new tool became the fuel for making it better. Autopilot and Cognitive Saturation: Commercial aviation is one of the safest forms of travel, and automation is a big reason why. Taking the manual work of flying off the pilot frees up mental capacity for radio calls, navigation math, and diagnosing problems. That adds a safety margin to every flight. Children of the Magenta Line: Automation also brought a new risk. When pilots rely on GPS and autopilot, their manual flying skills can atrophy,...

Fundamentals Will Help You Survive the Constant Acceleration of Software Engineering

13 min

Fundamentals get talked about constantly, but rarely defined. In this episode I dig into what a fundamental actually is — the building blocks, heuristics, and core characteristics that don't change — and why they matter more than ever in a profession where abstraction moves faster than almost anywhere else. If you feel like you can't keep up with every new framework, model, or tool release, the answer isn't to read faster. It's to step up a level. Fundamentals get talked about constantly — in sports, in hobbies, in software — but we rarely stop to define what one actually is. In today's episode, I unpack what makes something fundamental, why software engineering in particular buries its fundamentals under layer after layer of abstraction, and how principles-first thinking gives you a way to keep up with an industry that never stops moving without needing to learn every single new thing that ships. What Actually Counts as a Fundamental: Fundamentals aren't rules — they're building blocks, behaviors, habit patterns, and heuristics. In basketball it's dribbling. In football it's blocking. In software it's readability, reliability, the setup-execute-teardown shape of a test, basic logic structures. In communication it's sender, receiver, feedback, and noise. Why Software Abstracts Faster Than Almost Anything Else: Compare the practice of law, where the fundamentals look largely the same as they did fifty years ago, to software, where the work is symbolic at its core. We build symbols that mean something to humans but map down to a hard physical reality of flipped bits and moving electrons — and that symbolic nature is exactly what lets abstraction pile up so quickly. The Rise of Linguistic Abstraction: Our abstractions have become increasingly language-shaped. Object, function, flow, durable object, mesh, graph — these are primitive ideas expressed as words, and understanding that shift explains a lot about how the industry actually progresses. Abstractions Have Funda...

This podcast, its content and its artwork are not owned by, affiliated with, or endorsed by Castquire.

Up next

  1. Nothing queued. Use + Queue on any episode to line it up.

0:00 0:00