So the article seems to imply that "hackers" are the sort of people that look at a partially working system and say: "hmm let's re-write that in a new and untes

So the article seems to imply that "hackers" are the sort of people that look at a partially working system and say: "hmm let's re-write that in a new and untested language" or worse still "lets write this in language x because I've always wanted to try it" if thats the case, then I formally suggest that such people can get in the sea. I might be somewhat unfair, but that was my reading. > innovation tokens are completely made up So are programming languages. Innovation tokens are there to make sure that a business can complete a project vaguely on time and vaguely on budget. Look the reason why people were able to get away with pissing away millions of dollars in pointless re-writes of things is because the speed of business based on those systems was slower. Now, if your site is down, then customers flee. I mean sure, writing your own database for your SaaS company might be a thing, but its almost certainly expensive and pointless. You're on the hook for scaling it, recovering it when it fails, and finding and fixing all the bugs. In short, this article, I feel, encourages a damaging, selfish side of CS that I think should be phased out.