Khadija Abdi Hassan

We put off refactoring for way too long last year because we were so focused on launching new features every single week.

Eventually the codebase got so fragile that fixing one simple bug broke three other things in the app. Taking a few uninterrupted days to clean the foundation completely changed our speed going forward.

It really is the best investment you can make even though it hurts to look at an empty changelog at the end of the week. How do you decide when the tech debt is finally too heavy to ignore?

I think having more tools to build with can make it harder to be honest with ourselves about an idea.

When something is difficult to build, the effort itself forces you to think carefully about whether it s worth pursuing. But when changes take minutes instead of days, it s tempting to keep experimenting just because you can.

Not every unfinished project needs another attempt, and not every rough idea needs to become a product.

I m curious whether the real challenge now is less about execution and more about choosing what deserves our attention in the first place.

When I vibe code with Claude Code or Cursor, the agent tends to invent a new button, card and table on every screen. The app works, but each page looks slightly different, and sometimes the agent builds a placeholder UI and calls it done.

A few things I've tried:

Putting design rules in the prompt or an AGENTS.md file. It helps, but the agent drifts after a few screens

Giving it a component library to use. More consistent, but only if the agent can actually find and read the components