I am against vibe coding because you can't maintain what you don't understand.

If you don't know the logic behind what's been built, how can you support customers? And if you can't look into the programmed logic and make changes, who's going to do it?

As I'm re-designing a new subscription management system, I implement from the ground up the logic throughout the whole app, starting from user stories based on whether you're an already existing customer, or whether you're a free user, or tomorrow, a new customer.

This logic is documented from A to Z and will drive customer support. Yes!

The other good aspect of designing intentionally something is that you can apply principles an AI wouldn't necessarily have suggested.

In this case, I decided that customers that bought a plan before the release of these new pricing plans, will enjoy the benefits of the best pricing plan, but at the former price they paid. Not for 2 weeks or 3 months, but as long as they stay. No impact for them, that's it.

Why? Because I hate companies emailing me that prices will raise, or that in 10 days my bill will go from 40/mo to 100/mo. So, this is not going to happen to **ISMS Copilot** customers.

Vibe code can hardly do this!

Let's go back to designing and testing.