[brudgers]

Debt provides leverage. If the burden will obviously prevent reaching 2 million page views per month then it might be time to restructure. If it might keep you from hitting 20 million, all the bottle necks on that path havent been built yet. So there's no way to solve that problem now and anyway growing by an order of magnitude is a more important problem to solve.

That's not to say that building a wall around new code to keep the mud out is a bad idea, but that's a response to growth.

[nRike]

I completely agree. I recently started looking for this topic because the feeling I get is that everything is messy and its becoming a nightmare just to think about it. In my case, I'm taking more responsabilities and I think we need to start implementing best practices with our engineering team. Does that makes sense to you?

[brudgers]

Better practices going forward make sense. But rewriting working code should have a business case when the working code solves a business problem. Scaling and maintenance are second order problems. Success is the first order problem.