The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
One starts with a "C", the second with a "D", the third with a "P".
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
When I started out it was the systems analysts who did the design and logic. All the programmer needed to do was to convert the English instructions into lines of code. So it was a fairly basic function and any idiot (me) could do it. Since then the job has developed in line with ever more sophisticated hardware and software. So now, the 'programmer' has to understand much more and use his/her skills to develop products rather than be a 'code monkey'.
Every team needs some code monkeys and I've never seen a successful large project (in this century) that did not have a good balance of analysts, developers, and code monkeys; not to mention some kicka$$ QA people.
Being ancient enough to remember the System Analyst days, I'd modify that a little:
The profession started as Programmers - that meant we understood the mystic language of computers (COBOL, Algol, Fortran etc) and could translate detailed pseudo code into something that actually worked. In the modern parlance this is also referred to as Coders.
Software Engineers - an evolutionary step where the programmers were actually trusted with writing their own pseudo code and doing some design. Of course letting the business people actually meet the coal face workers was still frowned upon.
Developers - The current evolutionary step where the code jockeys actually can influence how the business should be using the software, rather than being told what to write.
An opinion is an opinion, it's my right to be wrong.
I guess it has to do with the image people have of each.
A programmer is someone who is anti-social and types code all day, not rarely for evil intent.
A coder is pretty much the same, but without the evil, maybe? It sounds more akin to script kiddies.
A developer sounds a lot more friendly. We're developing, rather than destroying.
I know I prefer the term developer because it sounds like I do more than just type code.
As a developer I also create UI's.
Or what about an engineer? I think I've had that title in the past.
In the end they're all the same, but managers rather hire developers than coders.
Put full-stack or cloud somewhere in your title and you'll do well among managers and recruiters
Looking at the progression of Programmer => Developer => Engineer...
A sanitation engineer is responsible for the proper handling of sewage and wastewater, as well as the sanitary treatment of wastewater and sewage. They use their skills to perform random sample testing of water in local streams and soil to make sure that the local environment remains safe from contamination.