Do you actually own the code you ship?

When a tool hands you a working solution, how much do you really need to understand about why it works?

In the latest episode of the No Compromises podcast, we discuss whether developers still care about understanding the code they ship, or whether that expectation is becoming a relic of the past.

We explore why knowing the "why" behind a solution isn't just about curiosity. It's about having enough domain knowledge to ask better questions, push back on bad answers, and ultimately produce better work.

We also walk through a real code review example involving a tricky Eloquent query, talk through the pressures that pull developers away from digging deeper, and consider what separates a line cook from a chef in how we approach our craft.

• (00:16) - Are developers losing the habit of asking why
• (02:16) - How AI changes the copy-paste-and-move-on cycle
• (05:25) - Learning by accident while reading the manual
• (06:24) - The Eloquent query neither of us could explain
• (12:16) - Silly bit

Join a community of developers who still care about understanding the code they ship.