3 ms·
I would imagine one reason for this is because the real complexity of a project has nothing todo with the programming. It has to do with evolving the business.
by blain_the_train 9y ago
I would imagine one reason for this is because the real complexity of a project has nothing todo with the programming. It has to do with evolving the business. Were on our 3rd re-write of our business, but the codebase still has legacy systems from the first two drafts. No language can save you from that.
- yogthos 9y agoI love it when people make a mess because they didn't really understand the problem initially, then rewrite it in something else and give all credit to the new technology they happened to be using. When you rewrite a project it's always going to be a lot better, because you have a much better understanding of the problem being solved having done that once already.
- hellofunk 9y agoIndeed, on anything serious I write it at least twice. Of course, using Clojure makes this easy since there is usually not a lot of code to rewrite. But after you get into something, you know details about what is needed that you simply cannot adequately predict beforehand in a lot of circumstances.
- imhoguy 9y agoTrue, but only with small projects. Once initial creators of rather complex project leave then the mess begins. No language will save you from changing requirements, egos or best practices. Will your rewrite of inherited 200KLOC "is always going to be a lot better"?