Have you ever felt a little stung when someone called what you do “vibe coding” as if decades of craft just became optional?

In the latest episode of the No Compromises podcast, we discuss why the rise of vibe coding as a term says something important about where software development is headed.

Aaron makes the case that vibe coding trades long-term quality for short-term results, like a kitchen that serves one burger fast but cannot make a second one for 27 minutes.

We also get into how AI tooling is shifting the role from writing code to reviewing and directing it, why the skills you have built still matter, and why Aaron is calling himself a software developer again.

• (00:00) - How developer titles have evolved over the years
• (02:12) - The problem with calling yourself a vibe coder
• (06:37) - Stepping back and letting AI handle the small details
• (10:49) - Your existing skills still matter more than you think
• (13:56) - Aaron's next chapter

Have you ever had someone review your pull request, make changes without telling you, and just merge it in?

In the latest episode of the No Compromises podcast, we discuss whether the traditional code review workflow still makes sense in a world where AI tooling lets developers move faster than ever.

Aaron shares two real situations where a reviewer fixed and merged code without discussion, and we dig into why the lack of communication is the real problem, not the act of fixing things itself.

We also get into commit strategies, how friction in reviewing someone else's changes kills the learning, and why well-worn workflows deserve a fresh look when the tools around them have changed.

• (00:00) - When a reviewer merges your PR without asking
• (03:31) - How we handled it differently with time pressure
• (05:43) - Should the reviewer just fix it and merge?
• (08:02) - Too many commits create friction for the author
• (13:44) - Silly bit

Your team is not the only one figuring this out. Join the conversation in the No Compromises community.

Have you ever handed off a feature request with barely any detail and expected the developer to just figure it out?

In the latest episode of the No Compromises podcast, we discuss why writing clear requirements is one of the most valuable things a business can do before development starts.

We make the case that even imperfect requirements beat none at all because they determine where the discovery happens, closer to the finish line rather than somewhere in the middle of the country.

We also cover why letting AI write your requirements for you is a trap, and how AI can help you review and cross-check requirements instead. And why the more detail you put in upfront, the less money you spend on surprises later.

• (02:53) - Good requirements let you build start to finish
• (05:10) - Imperfect requirements still beat having none
• (07:36) - Why AI should not write your requirements
• (09:09) - Using AI to cross-check requirements instead
• (10:46) - Silly bit

Subscribe to the Mastering Laravel newsletter for practical insights that help you communicate better with your development team.