> Exactly. A thing so small and simple that you can rewrite it in an afternoon is more futureproof than any 8000 LOC monstrosity.
As I've said multiple times, here and elsewhere, it is easier to fix the problem of under-engineering that the problem of over-engineering.
I also disagree with the article's "pros" for over-engineering. There is no pro that I can think of that doesn't boil down to resume driven development.
The pros of under-engineering is (the way you say it) obvious: very little time was spent to figure out that you did it wrong.
