4 ms·
Good point, sir. I'm not a native speaker, as you might already have guessed, and probably think of my spelling skill too much :) I'll fix the typos. But I'm n
by yanis_t 11y ago
Good point, sir. I'm not a native speaker, as you might already have guessed, and probably think of my spelling skill too much :) I'll fix the typos.
But I'm not going to "find out" about the quick sort, anyway. And the reason why is exactly what this article is about.
What I was trying to say by it, is that we as developers should invest our time consciously in learning things that will lead to company's profit. There's so much to learn these days. Many new shiny interesting things. And we are sometimes being too tech-y, we like to learn hard stuff, because it make us feel smart.
While the smart thing would be to constantly thinking about whether I really need that skill or not.
- Nadya 11y ago>I'm not a native speaker, as you might already have guessed I picked up on that, don't worry! It was meant as advice, as many people would stop reading without keeping that in mind. >What I was trying to say by it, is that we as developers should invest our time consciously in learning things that will lead to company's profit. This assumes you're already working for the company. Generally this sort of thing is asked in an interview. If the company is asking you to perform a quick sort - it may be the field of work that is beneficial to the companies bottom line and therefore be important to know! The reasoning here is much like the argument against "code a binary tree search on a whiteboard" except it replaced "search binary tree" with "quicksort". It may or may not be applicable but if a company is asking, they believe it might be. (Or they consider it a display of talent/skill, which can be equally important in hiring decisions.)