as9as87df

I know you are being sarcastic, but this may have a grain of truth (not the concern but the concept itself)

Eventually these trees will die and rot/burn anyway, but new ones will grow and recover near equivalent carbon. Trees just hold carbon temporarily.(Underground gas is another story though)

If you burn oil from deep underground, that carbon would never have escaped without human intervention.

If you timeout on a significant number of questions, the code you wrote is not a few micro optimizations away from succeeding. The entire point is not to write the easy slow solution that is hundreds of thousands of times slower for large input sizes. This is much easier than getting the best solution, and hence less credit is given. I'm sorry that the instructions were not clear.

I agree with the author on some cases; Frequently, sites like hackerrank have a specific case that causes Java Arrays.sort() to go O(n^2) and time out. Those feel dumb; there are many real life situations where quicksort is fast on average and well worth using.

As for other things that hackerrank doesn't test, I would say you should use hackerrank to screen applicants vs as an end-all-be-all.

I saw the new logo, and I thought 'why does this green look ugly'. Since then, I've started getting used to it and it doesn't stand out as awful anymore. I haven't heard anyone else mention it until this article.