Having a solid product that solves a problem well can be orthogonal to how well a codebase lends itself to readability, learning curve, and efficiently ramping up new developers on a project.

Just because you succeed at one says nothing about other practical and important metrics.

▲

epolanski 3 days ago | parent [-]

I don't think you're reading this correctly.

The proper way to read it is to understand the problem and its pros and cons.

Without going long in the speculation, the situation likely was: there's only one guy who really can deliver this because of his knowledge, cv and experience and we need it.

And at that point your choice is having a solution or not.

	▲	WhitneyLand 3 days ago \| parent [-]
		As the old saying goes the graveyards are full of irreplaceable men. But even if we grant that only one person could deliver a solution, it wouldn’t change the fact that you’re giving up on certain things to get it.