Like any generalization of a complex topic, trying to pigeonhole a software developer into one of two categories is going to fail pretty massively at being descriptive of what they actually do. Like they are two separate checkboxes that have nothing in common. The fact that if you ask 5 different people what the terms mean you will get 7 different answers, and that every 5 years those 7 answers change, means to me that the value of these two terms is less than zero.
Yeah agreed, when recruiting we should try and avoid pigeonholing people as much as possible. This is something for me to think about, in terms of trying to get across the experience required > the job title/tools used.
Dividing the two disciplines was something I didn't like, and was quick to change when I started haha.
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.
First reply nails it.
Like any generalization of a complex topic, trying to pigeonhole a software developer into one of two categories is going to fail pretty massively at being descriptive of what they actually do. Like they are two separate checkboxes that have nothing in common. The fact that if you ask 5 different people what the terms mean you will get 7 different answers, and that every 5 years those 7 answers change, means to me that the value of these two terms is less than zero.
Yeah agreed, when recruiting we should try and avoid pigeonholing people as much as possible. This is something for me to think about, in terms of trying to get across the experience required > the job title/tools used.
Dividing the two disciplines was something I didn't like, and was quick to change when I started haha.