ABOUT THIS EPISODE
In this episode of Fundamentals of Software Engineering, Nate and I dig into context engineering, the phrase that has quietly replaced prompt engineering as the term on everyone's 2026 bingo card. Our core argument is simple. Context engineering is not a shiny new AI skill, it is a data fundamental you probably already know, just wearing a new name. Prompt engineering is about how you ask. Context engineering is about what the model actually knows when you ask. We frame it as a desk and a filing cabinet, where the context window is the desk and your job is deciding what belongs on it right now. Along the way we get into structured versus unstructured data, retrieval augmented generation, tools, and why getting the right information in front of a model matters far more than crafting the perfect prompt.
We also pump the brakes on the idea that coding is solved and engineers are optional. We talk through the headlines, Spotify shipping thousands of deploys a day with most pull requests now AI assisted, and Ford rehiring hundreds of veteran engineers after AI could not replace decades of hard earned wisdom. That leads us to data hygiene, access control, and lineage, because AI does not fix garbage data, it exposes it. We cover keeping context fresh, why a confidently wrong AI is worse than no AI, and why curation beats volume when tokens are the currency of large language models. We close on data migration, version control for your schema with tools like Flyway and Liquibase, data validation, and the case for smaller local models fed the right context. Data is the backbone of everything we build, even in the age of AI.
__________________________________________________
Key Highlights
🚀 Deploy Versus Release: Spotify reportedly ships around 4,500 production deploys a day with 73 percent of pull requests AI assisted, which opens a great conversation about why a deploy is not the same thing as a release.
🛑 Pump the Brakes on Coding Is Solved: Ford rehired more than 300 veteran engineers after AI failed to match decades of expertise, a reminder that new tools boost productivity but do not remove the need for engineers in the loop.
🗂️ Context Engineering, Defined: We reframe the buzzword as a data fundamental, where prompt engineering is how you ask and context engineering is what the model knows when you ask, using the desk and filing cabinet analogy.
🧹 AI Exposes Garbage Data: If you have skipped access control, lineage, and data hygiene, AI will not solve that for you, it will shine a bright light on the disciplines you skipped earlier.
📦 Structured Versus Unstructured Data: We break down the two main data types and why the proliferation of data stores means picking the right tool for the job instead of copying whatever Twitter or Netflix did.
🔄 Migrating and Versioning Data: From big bang versus phased migrations to schema version control with Flyway and Liquibase, we cover the fundamentals that keep data changes safe and repeatable.
🎯 Curation Beats Volume: More context is not always better. Because tokens are the currency of large language models, feeding a smaller local model the right curated context often beats reaching for the biggest frontier model.
__________________________________________________
Resources & Next Steps
📘 Fundamentals of Software Engineering: From Coder to Engineer, the book behind the show, available on O'Reilly and Amazon.
🌐 FundamentalsofSWE.com, the home for the book and the podcast.
🧠 NotebookLM, a Google tool for building a curated, specialized model around your own documents.
🛠️ Flyway and Liquibase, tools for version controlling database schema changes.
🎧 Subscribe to Fundamentals of Software Engineering on Apple Podcasts
__________________________________________________
Chapter Timestamps
00:00 Cold open, deploy versus release and pump the brakes
01:02 Welcome and what this episode covers
03:47 Podcast and book intro, Fundamentals of Software Engineering
05:15 Data as the old priesthood, DBAs and data models
06:47 News, Spotify's 4,500 deploys a day and 73 percent AI assisted PRs
08:00 Deploy versus release explained
11:06 News, Ford rehires veteran engineers after AI falls short
12:06 Why you still need experts in the loop
13:33 Domain knowledge AI cannot replace
16:21 Data fundamentals, data outlives the systems
19:25 Prompt engineering versus context engineering
21:01 Context engineering defined, the desk and the filing cabinet
22:48 Garbage data, access control and hygiene
23:16 Structured versus unstructured data
24:34 Proliferation of data stores and the right tool for the job
27:24 Supplying context, prompt stuffing, RAG and tools
31:03 Keeping context fresh, a confidently wrong AI is worse than no AI
33:31 Data migration, big bang versus phased
37:59 Version control for data with Flyway and Liquibase
41:55 Data validation and guarding against bad input
45:54 Curation beats volume and tokens are the currency of LLMs
51:56 Smaller local models, curated context, and a dad joke to close
