I've never met a software engineer that didn't code. In fact, the idea is ridiculous to me at first brush. What else would they do?
Maybe there could be an organization where software engineers are in charge of designing and planning out code entities (e.g. classes and their interactions) and developers are in charge of implementing those designs, but that would be very unsatisfying to both parties. It would deny the engineers the hands-on fun of writing good code, and it would make the developers feel like "code monkeys", always implementing someone else's idea and not allowed to think creatively and make decisions. I don't know of any company that works like that and I hope I never work for one.
As far as I know, the most accurate rule about job titles in software is this one:
Justin Searls
@searls
In one tweet, I shall reveal the meaningful distinction between all these software roles:
Here it is: nothing. Popular use is so wildly inconsistent that the words don't matter
02:52 AM - 14 Mar 2018
127386
Inside of a given company, they can decide that specific titles mean whatever they want, but across the industry there's no real standard, at least not in the U.S.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've never met a software engineer that didn't code. In fact, the idea is ridiculous to me at first brush. What else would they do?
Maybe there could be an organization where software engineers are in charge of designing and planning out code entities (e.g. classes and their interactions) and developers are in charge of implementing those designs, but that would be very unsatisfying to both parties. It would deny the engineers the hands-on fun of writing good code, and it would make the developers feel like "code monkeys", always implementing someone else's idea and not allowed to think creatively and make decisions. I don't know of any company that works like that and I hope I never work for one.
As far as I know, the most accurate rule about job titles in software is this one:
Inside of a given company, they can decide that specific titles mean whatever they want, but across the industry there's no real standard, at least not in the U.S.