Search a title or topic

Over 20 million podcasts, powered by 

Player FM logo
Artwork

Content provided by Joel Clermont and Aaron Saray. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Joel Clermont and Aaron Saray or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

When building a UI makes more sense than bloating your seeders

11:49
 
Share
 

Manage episode 503367508 series 2974897
Content provided by Joel Clermont and Aaron Saray. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Joel Clermont and Aaron Saray or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

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

Need help on your Laravel project? Hire two experts and accelerate your progress.
  continue reading

134 episodes

Artwork
iconShare
 
Manage episode 503367508 series 2974897
Content provided by Joel Clermont and Aaron Saray. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Joel Clermont and Aaron Saray or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

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

Need help on your Laravel project? Hire two experts and accelerate your progress.
  continue reading

134 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Copyright 2025 | Privacy Policy | Terms of Service | | Copyright
Listen to this show while you explore
Play