Is this literally what they teach in school now? I’m asking this honestly. It would explain quite a lot about why we have such a hard time finding programmers and engineers under 50 who are able to think through simple interview questions about designing basic solutions.
The past 2 programmers hired at my job lasted about 2 years each, and it was clear that they both would immediately move forward with the first “solution” that popped into their head for any problem. They’d “fix” a problem in minimal time, but this would cause TONS of wasted labor, troubleshooting, and travel downstream. They didn’t bother to think beyond the immediate “fix” for this problem with no regard for that problem it would cause for 2 other teams.
We have a few other old school programmers that went through computer engineering and science degrees when it was more akin to philosophy. They are fantastic and I love working with them.
Is this literally what they teach in school now? I’m asking this honestly. It would explain quite a lot about why we have such a hard time finding programmers and engineers under 50 who are able to think through simple interview questions about designing basic solutions.
The past 2 programmers hired at my job lasted about 2 years each, and it was clear that they both would immediately move forward with the first “solution” that popped into their head for any problem. They’d “fix” a problem in minimal time, but this would cause TONS of wasted labor, troubleshooting, and travel downstream. They didn’t bother to think beyond the immediate “fix” for this problem with no regard for that problem it would cause for 2 other teams.
We have a few other old school programmers that went through computer engineering and science degrees when it was more akin to philosophy. They are fantastic and I love working with them.