Business change and projects end, but how do you wrap up and sunset an app, especially one you've worked on for years?

In the latest episode of the No Compromises podcast, we share a practical checklist for winding down an app when the whole company is closing. From documenting services and dependencies to deciding what data to retain, we cover backups, credentials, and why deleting local copies matters for security and sanity.

• (00:00) - Sunsetting a company vs project handoff
• (02:15) - First goals: stop charges, purge data
• (03:45) - Document before shutting anything off
• (04:15) - Use README/PRODUCTION.md and password manager
• (05:45) - Decide on retaining code, DB, uploads
• (07:15) - Hunt secrets in .gitignore and dotfiles
• (09:15) - Delete local containers and repos by default
• (11:30) - Silly bit

What do you do when you need to create some data but you haven't built out the UI for that data yet? A seeder is a great approach, but is it always the right one?

In the latest episode of the No Compromises podcast, we dive into a real project where starting with the most complex feature made test data management painful. Instead of exploding the complexity of our seeders, we built a minimal UI to manage test data.

We also talk about some other unexpected benefits, and talk through the trade-offs and why detours like this should feel uncomfortable (and be tightly scoped).

• (00:00) - Starting deep exposes messy user permutations
• (02:45) - Seeder explosion vs. a minimal UI
• (03:45) - Reframing the “detour” after using it
• (05:30) - Why the mini-UI helped: faster iteration, fewer seed resets
• (07:45) - Dogfooding + tester debugging benefits
• (08:00) - Guardrails: detours should feel uneasy and stay tight
• (09:00) - Silly bit

Blade gives you two big levers for keeping views maintainable: @include and Blade components.
When should you use one versus the other?
Does it matter?

In the latest episode of the No Compromises podcast, we lay out a clear heuristic for when to extract markup for organization (includes) versus when to encapsulate and reuse with controlled scope (components).

We also touch on scope pitfalls, “passing for documentation,” and why performance worries usually lie elsewhere.

Sign up for the free Mastering Laravel newsletter. The highest value-to-time ratio you will find.