2 ms·
In every challenging software development job, you'll be solving problems you've never encountered before. That's the nature of software. Once you understand th
by dmansen 11y ago
In every challenging software development job, you'll be solving problems you've never encountered before. That's the nature of software. Once you understand the problem, you move on to something else.
So, why is it such a stretch to ask people to solve Fibonacci? I don't understand this mentality. Reminds me of "why should I learn calculus? I'll never use it in real life!" from college. You're supposed to be a professional software developer, and should be able to handle an unfamiliar problem.
If you're a professional musician auditioning to play Mozart, you wouldn't complain that your audition piece is Beethoven.
- vonmoltke 11y ago> In every challenging software development job, you'll be solving problems you've never encountered before. The problem is, the vast majority of software development jobs are not this. That was the point of the comic in the post. There is a whole lot of maintenance, API gluing, and spec work that needs doing. Even at the "elite" companies like Google. The current trend in hiring seems to be at least partially born of Google's ill-advised[1] strategy of hiring generic software engineers that could theoretically be slotted into any role at the company. Hire for a position. If that position involves challenging, novel problems then throw things like that at the candidates in the interview. If it doesn't, don't. [1] After they reached a certain point as a company