A good way to minimize technical debt is to block PRs that have TODOs until the author completes them, therefore eliminating the technical debt they would have otherwise introduced.
Although I wonder how much self-censorship that encourages. Whether or not to put a TODO in your code is a judgement call. If you tell some developers that admitting to a TODO means that they can't submit, they might not admit to them as often.
It's a bit case-by-case, but I think I'd rather encourage contributors to admit to the lacks in their code and accept them - but get them to commit to follow ups that will fix the problems.
This is likely to lead to developers just leaving out the TODOs instead of doing the work. Especially for work that isn't needed now but should be done at some point in the future.
I didn't even think about that, but yeah he totally did.
This whole article has a very "Wow, all other languages except for the one I've invested time in really suck!" feel to it. The arguments presented are shallow at best, rely on short-term data, mostly just popular trends of what people are talking about/searching for.
There's not any empirical evidence that I've seen in this article that suggests any language is better than any other language.
OP here: You are right, CloudFlare would have been nice and in retrospect we should have added it. I think it would have fared quite nicely as during all the tests we do on regular basis its doing really well.
yes. That is true. We did not expected the post will get that popular. Unfortunately, it was all done too late. What helped us the most was that blog is hosted on DigitalOcean VPS. We scaled up to the most powerful instance and instantly the blog was back. Kudos to DigitalOcean, it saved our bacon big time today :)