Ilian Madzharov

Our dev cycle has turned into a endless loop of patching one bug only to watch another feature break right after.

It feels like we spend more time re-testing existing features than actually building new ones.

We re trying to set up a lighter workflow so every update doesn't trigger a full manual check of the entire app.

What basic QA routines or lightweight tools keep your builds stable without slowing down your weekly ship date?

I've been building a SaaS with Lovable + Supabase that handles pretty sensitive stuff bank data via Open Banking, tax-related info. It's still in beta with very few users, but I want to get security right before opening it up more.

I know the basics (HTTPS, not exposing API keys in the frontend), but I'm not confident I've covered what actually matters for something handling financial/tax data.

For anyone who's dealt with this:

What would you consider the absolute minimum before letting real users connect their bank accounts to something you built solo?

As a solo developer I feel like I am constantly caught between building new stuff and fixing my past mistakes.

When you are trying to launch fast you write quick dirty code just to see if an idea works. But a few months later that same code turns into a headache. Changing a tiny button now breaks two completely unrelated things.

The issue is users always want new features but my codebase is crying for a complete rewrite. If I spend two weeks refactoring I ship zero updates to users. If I keep building new features the whole app will eventually break.

For those running solo projects long term how do you balance refactoring with building new features. Do you set aside specific days for tech debt or just fix things as you go?