Ask HN: At what point does "clean architecture" become technical debt?

4 pointsposted 7 hours ago
by kiops

Item id: 49401374

3 Comments

aristofun

2 hours ago

These meme only makes sense for very small products.

After a certain threshold of complexity and size any software becomes a collection of trade offs and compromises, never something you might call a “clean architecture”. Its a red herring, myth, utopia.

It’s a thousand years old attempt to calculate and reduce the complexity of real world interactions and problems to a bunch of mathematically elegant metaphors and formulas.

The threshold is usually very low - first bunch of real world paying customers, real world usecases, startup market fit etc.

dtdynasty

5 hours ago

When the cleanliness doesn't serve existing or future requirements.

karmakaze

3 hours ago

Exactly, architecture for its own sake is debt on day 1.