I would tend to disagree. Anyone can be a developer but not everyone is a software engineer. With the distinction around the discipline. The software development world is multi-variate. I've seen some great developers but they lack architectural disciplines or focus completely on optimization and less on maintainability.
I generally bucket software developers and software engineers into two buckets with a gradient of from one to the other demarcated by discipline and craftsmanship. I don't think skill or ability to mentor necessarily plays into their growth, although at the extremes, it does.
I think every entry level software maker is a developer with a very narrow focus towards solving problems. As their skills, scope and ability grow, they become more senior. However, if they science their way through development and grow in skill and discipline, the are actually leveraging engineering qualities.
I usually don't, unless its a medical transcription term (I work in healthcare). I think if I had to draw a venn diagram of the roles, a coder and a junior dev are the same. How one would identify doesn't really matter to me when I'd hire for that role. If a person said, "I'm a coder" and they applied for a more senior position, I'd also lean towards asking if they a mentor as well or where they see themselves. If they do more, they are more but they may be underselling themselves.
I see. In this case, this is merely a misunderstanding: What you call "developers" is what I call "coders" - because they aren't really deeply involved in the concept of what they "code".
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 would tend to disagree. Anyone can be a developer but not everyone is a software engineer. With the distinction around the discipline. The software development world is multi-variate. I've seen some great developers but they lack architectural disciplines or focus completely on optimization and less on maintainability.
I generally bucket software developers and software engineers into two buckets with a gradient of from one to the other demarcated by discipline and craftsmanship. I don't think skill or ability to mentor necessarily plays into their growth, although at the extremes, it does.
I think every entry level software maker is a developer with a very narrow focus towards solving problems. As their skills, scope and ability grow, they become more senior. However, if they science their way through development and grow in skill and discipline, the are actually leveraging engineering qualities.
So where do you draw the line between "coders" and "developers"?
I usually don't, unless its a medical transcription term (I work in healthcare). I think if I had to draw a venn diagram of the roles, a coder and a junior dev are the same. How one would identify doesn't really matter to me when I'd hire for that role. If a person said, "I'm a coder" and they applied for a more senior position, I'd also lean towards asking if they a mentor as well or where they see themselves. If they do more, they are more but they may be underselling themselves.
I see. In this case, this is merely a misunderstanding: What you call "developers" is what I call "coders" - because they aren't really deeply involved in the concept of what they "code".