4 ms·
I've seen similar articles to this one, both in print and on web sites. I used to explain it to people as the difference between 'coders' and 'engineers' but I
by ChuckMcM 9y ago
I've seen similar articles to this one, both in print and on web sites. I used to explain it to people as the difference between 'coders' and 'engineers' but I think my own hubris at having a degree got in the way of my thinking on it.
Over the decades I've met a bunch of people who program computers for a living, and there is clearly a spectrum where on one end is a person who spends the weekend benchmarking different sort algorithms under different conditions for the fun of it, and the guy who left the office at 5PM once an integration test passed on a piece of code that he pasted in from stack overflow was deemed to have no regressions. There are many different disciplines that have such a wide dynamic, from chefs who spend their weekends trying different flavors to cooks who take frozen patties out, reheat them and serve. Painters who throw human emotion into a painting and painters who lay down a yellow line on a road according to a template for $20/hr.
It seems to me that most, of not all, of the 'theory' stuff in computer science is just math of one form or another. This is not unlike all the 'theory' stuff in electrical engineering is just physics. You can do the tasks without the theory, but you rarely invent new ways of doing things without that understanding.
But just like carpenters and architects there is a tremendous amount of depth in the crafting of things. That brilliance should be respected, college trained or not, so trying to 'split' the pool doesn't lead to any good insights about what being a good engineer is all about.
- Clubber 9y ago>I used to explain it to people as the difference between 'coders' and 'engineers' This isn't going to be popular, but it's true. Coders are what people called themselves before business started making the decisions about how to write software. Engineers are what people called themselves after business started making the decisions about how to write software. Guess what? People who write software aren't engineers, they are programmers. You have crap programmers and you have exceptional programmers, but you they are paid to write programs. "Software Engineer" is as valid as a "Sanitation Engineer." Coder is a slang for programmer because they write "source code." it dates back to at least the 80s, probably earlier. It is also acceptable term for programmer. If you have to make up a fancy term, call yourselves software developer or software designer. If you want to be called an engineer, go to engineering school. https://www.theatlantic.com/technology/archive/2015/11/programmers-should-not-call-themselves-engineers/414271/ https://www.theatlantic.com/technology/archive/2015/11/progr...
- adjkant 9y agoThe terminology is shifting though, and has been for some time now. While I agree that CS/SE is not "engineering", it's the common term across the top companies, with words like "developer" now fading in use. For me, I have the opposite reaction to coder vs engineer. For a coder, I think code monkey, someone who writes boilerplate MVC apps and can't handle algorithmic complexities, write code that others can understand, or consider lower levels of a system they are interacting with. Also synonymous with hacker, which I would bet also has a reversed connotation for those who see coder as a good thing. When I hear engineer, it's synonymous with the jobs at the big name companies and implies the person thinks their job is complex enough to warrant the title, even if not deserved by the standards of other engineers. Of course, all of this is semantics, including the debate over what is an "engineer". In the end, it's pretty meaningless in terms of impact. CS vs SE I think should be the focus, as yes, the two can be quite different, even if most CS degrees end up working in SE.
- Clubber 9y ago>The terminology is shifting though, and has been for some time now. Yes, I agree. "Coder" and "Programmer" are grey beard terms. >Also synonymous with hacker, which I would bet also has a reversed connotation for those who see coder as a good thing. Yes; a hacker is someone who can bend the computer to their will, even when it isn't supposed to do it. That's one of the reasons people who crack software and infiltrate systems sometimes get that moniker. >implies the person thinks their job is complex enough to warrant the title, even if not deserved by the standards of other engineers. Ya, that's kinda the problem. It has an inferiority aura about it. > In the end, it's pretty meaningless in terms of impact. CS vs SE I think should be the focus, as yes, the two can be quite different, even if most CS degrees end up working in SE. It absolutely is meaningless, I guess that's what bugs me about it. CS is for creating an improving algorithms. John von Neumann discovered/created merge sort in 1945 (among other things). He is CS. "Engineering" is taking merge sort and using it for efficient joins in an RDMBS; applying science to an actual thing.
- hueving 9y agoIt's sad to me when people try to trivialize the profession of the people responsible for the information age like this. Why does the term 'software engineer' hurt your feelings so much when these are the people responsible for taking mathematical concepts and turning them into working marvels like the Internet, wifi, cellular data, networks, etc?
- zerr 9y agoYou seem to be labeling overworking as "good" and in-time as "bad"... Here's an alternative perspective - I've seen underperformers who try to make it up by staying late and even allocating weekends for their employers, on the other hand, I've seen brilliant engineers who do the job and leave the office at 5PM, spending personal time on recreation, including learning other tech/stuff not relevant to their employers...
- ChuckMcM 9y agoIf I gave that impression I apologize it was not my intent. I don't attach any judgement to either hours invested or method of code construction. I was just sharing my observation that it is a multi-variable spectrum. That leads directly to your exact observation. Very little correlation between hours spent 'at work' and the quality of code produced. When I started managing programmers I realized the best thing I could do was to manage people by agreed upon deliverables for their capabilities, quality, and maintainability. And if it took them 10 hrs to do it or 70hrs didn't matter. As long as I understood, and they understood, how long it would take them to do something we could manage to that schedule.
- hueving 9y agoThat's because you just fixated on the 5PM and not the rest of the words in each sentence.
- zerr 9y agoI don't think so, since the examples mention overworking towards the current assignment. Anyway, 5PM stigma exist and there is no harm to reiterate this topic.