I think that in a lot of ways it already has and this is totally fine by me. I've always had a lot more fun coding as a mechanic, getting lots of different pieces to fit together and work in together, than an "engineer" per say. The reason I know this has not been embraced is coding interviews are still horribly theoretical and catered to those with a classical education by and large. Most organizations need to be honest with themselves and decide are we just going to use google/amazon/ibm/microsoft services to get to our goal or are we going to be writing our own algorithms and forging new pathways in computing. In my experience everyone interviews as though they are building image recognition but what they really want is someone that understands API's, protocols, performance, UI tooling, etc.
Case in point a lot more of us use React, rails, typescript, webpack, django etc. than contribute to it and that is totally OK. There are craftsman and there are engineers, we shouldn't be ashamed of that dichotomy. Soul of a New Machine has an amazing quote for this I just can't recall it at the moment.
I think some of the resistance comes from people thinking salaries are going to drop if this happens as well and I don't think that is necessarily true either. There are plenty of carpenters that make as much money as the person designing and constructing the table saw (probably even more in most cases). In fact oftentimes the craftsman are better at using the tool than those that built it.
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 think that in a lot of ways it already has and this is totally fine by me. I've always had a lot more fun coding as a mechanic, getting lots of different pieces to fit together and work in together, than an "engineer" per say. The reason I know this has not been embraced is coding interviews are still horribly theoretical and catered to those with a classical education by and large. Most organizations need to be honest with themselves and decide are we just going to use google/amazon/ibm/microsoft services to get to our goal or are we going to be writing our own algorithms and forging new pathways in computing. In my experience everyone interviews as though they are building image recognition but what they really want is someone that understands API's, protocols, performance, UI tooling, etc.
Case in point a lot more of us use React, rails, typescript, webpack, django etc. than contribute to it and that is totally OK. There are craftsman and there are engineers, we shouldn't be ashamed of that dichotomy. Soul of a New Machine has an amazing quote for this I just can't recall it at the moment.
I think some of the resistance comes from people thinking salaries are going to drop if this happens as well and I don't think that is necessarily true either. There are plenty of carpenters that make as much money as the person designing and constructing the table saw (probably even more in most cases). In fact oftentimes the craftsman are better at using the tool than those that built it.