11–13 of 13 posts
Talking about getting things done in the least amount of time and then bringing up the retarded old "it's all Turing complete" argument shows that he has some more thinking to do on this subject.
The simplest solution is often also the most flexible. I don't think you can argue that simple is bad design.
During requirements and feature planning, I have often found that features get more and more complicated until - guess what - things click, similarities become obvious, and you end up with a solution that's a lot more simple - and more flexible - than you expected. You don't always get that "aha!" moment, and you can't spend your entire development cycle chasing it, but it is often there.
Nice. I guess the author never experienced the joy of having this lovely conversation with his users: Programmer: That feature you asked for two weeks ago? It's done. Take a look. What do you think? User: Oh... hmmm... yeah, that's kinda wrong... See, I know I said I wanted X, but I just realized I actually wanted Y. But Y is very similar to X, can't you just tweak it and I'll come back to take a look after lunch? Pr…
The less code you have to write initially, the less you'll have to scrap when the rewrite comes. And the rewrite always comes. The question is when.