6 ms·

Yet another example of someone mixing the concepts of scientist, engineer, and technician in the computing world. You wouldn't hire a food scientist to control

Yet another example of someone mixing the concepts of scientist, engineer, and technician in the computing world. You wouldn't hire a food scientist to control and feed the machines that produce the bread in an industrial bakery, or even to design and build that production line. Producing code is not as closely related as one might think to the science that leads to the algorithms and design patterns that underscore the languages and frameworks that enable the tools and techniques ultimately used by those who produce code. The sooner all concerned (me, you, academics, entrepreneurs, employers) settle on a suitable terminology for what it is that computer scientists, software engineers, and developers need to learn to do what they do, the sooner we can get past this type of article.

Nerdfest 11y ago
Absolutely. This is what I posted on the other copy of this article: The problem is that even if you understand those concepts well, you're not necessarily able to apply them after most programs. If your startup is in the business of crating new algorithms to solve various problems, that's one thing, but what most want is someone who knows what existing algorithm should be used to solve a problem in the best (or at least an acceptable) way, and do so in a manner that's both expandable and maintainable. Ideally, they're looking for a craftsman, not a scientist. These roles can occasionally be found in the same person, but it's extremely rare in my experience.