Jeremy Loomis

We spent four straight months pushing out user-requested features as fast as possible to beat competitors. It worked for initial traction, but our codebase eventually turned into a fragile mess where adding one simple toggle broke two unrelated workflows. We had to freeze all new releases for three weeks just to refactor core modules and set up proper automated tests. It temporarily stalled our roadmap, but our error logs dropped by 80% and long-term development speed doubled afterward.

How do you convince stakeholders that spending time on internal code refactoring is more valuable than pushing out shiny new features?

My Downloads folder has slowly turned into a mix of PDFs screenshots installers and random files I only needed once. I keep meaning to clean it up but doing it manually every few days gets annoying. I d rather not pay for another cleanup app just for this. Are you using any built-in rules shortcuts or simple folder setup to automatically deal with old files?

One of my young and enthusiastic maker followers recently asked me for advice on finding alpha testers.

And honestly I realized I m not the best person to answer this one =D

We built RunEvr inside an animation studio, so our team of artists naturally became our first alpha testers.
We had a real product, a real team, and a real workflow to test it on from day one.

So I couldn t really give advice based on my own experience.