Popular posts

If a business deal that will make or break your startup depends on whether you can deliver or not, would you rather go for the money and put something in place that's horrible by everyone's standards or implement it correctly, lose the deal and have more such pressure? Doing things 100℅ correct is a luxury not everyone can afford, especially early stage startups, I've seen some horrific code in my life but that horrific code closed the deal, made the owners millionaires and after that they spent plenty of time catching up with the technical debt now that they had the luxury of doing things properly.

Some people code for money other people get money for coding. I'd rather do it right the first time. I value craftsmanship more than money.

In the case of two of these startups I've worked at with 20+ staff members, failing to deliver would have meant mass retrenchments or even closing down which would have meant that beautiful code would have been worthless and thrown away. In startups you often need a different type of craftsmanship, build a well designed interface and write the dirtiest, quickest nastiest code behind the interface, code that you can just replace at some point without affecting anything else. Often business requirements change so quickly that the code behind that interface will be thrown away in any case

That's nice. It still doesn't change my opinion.