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

Fundamentals Will Help You Survive the Constant Acceleration of Software Engineering

Sep 21, 202613 minAudio

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 Fundamentals Too: This is the key move. If you understand what makes Postgres a good fit - structured, predictable, relational data - you can evaluate any other relational database without learning it from scratch. Understand the primitives of NoSQL, or of an index lookup, and you no longer need to chase every implementation. Decompose, Then Recompose: Principles-first thinking means breaking things down into their underlying characteristics so you can recombine them into solutions you care about. It works on databases, on business offerings, on competitive positioning - anywhere you'd otherwise be tempted to evaluate things as wholly separate. Applying It to LLMs: When a new model drops from one provider or another, you don't need to start over. If you know which characteristics matter, you can see what changed here versus there - and treat them as variations on shared fundamentals rather than two entirely different things. Practice vs. Analysis: There are two flavors here worth separating. Fundamentals in practice are the things you do repeatedly - giving feedback regularly, for example. Fundamentals as analysis is a way of looking at new technology and asking what core characteristics make it up. You want both: composable actions and composable tools. Risk as a Fundamental: A live example from my current role - determining the right level of risk in a given scenario can't be a one-size-fits-all rule. It requires understanding the fundamental characteristics of the risk and reward you're accepting. Episode Homework: Look at your work and ask where you're too deep in the weeds. Where are you thinking too granularly? Where are you missing the abstraction class - the consistent things shared across multiple iterations that you could be watching from a step away? That distance is what gives you leverage to notice when something fundamental actually changes. ๐Ÿ“ฎ 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