Won't most library developers (working in a company) have a title very similar to SDE?
By backend role, SDE is the position most people refer to - which has a familiar recruitment process and then you might land up working on some library. Its very hard (i would imagine) to plan your whole career exclusively as a library developer.
The point i am trying to make is - many of these are sub-track of backend developer track, because of how recruitment process works. Sure, it's good to think about them, but very hard to plan your career around one specific sub-track.
I've been coding for over 20 years now! (WOAH, do I feel old)
I've touched just about every resource imaginable under the Sun (too bad they were bought out by Oracle)
Not necessarily. For instance, in my current role, I'm the lead database administrator for a company. Nowhere in the job description or hiring process was programming apart of it. However, the role was mostly open-ended to "solve things as you see fit". There were some internal tools already in place, as well as 3rd party tools. I lead the initiative to replace the external tools with internal tools that better met the company's need, as well as re-write the internal tools. This lead to the creation of some re-usable libraries that are now available to other teams.
And this is a trend I've repeated countless times in the tech industry. My first "real job" ~16 years ago, I was hired to simply do data entry for an early ecommerce company. I wrote some code there to automate most of the process.
None of this is what would traditionally be thought of as "back end" development, as none of this had anything to do with web dev at all. These would be more categorized as "process automation" which historically landed under titles such as Systems Analysis and Design.
There are many paths to becoming a dev, and many destinations that are not even remotely related to web dev. :)
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.
Won't most library developers (working in a company) have a title very similar to SDE?
By backend role, SDE is the position most people refer to - which has a familiar recruitment process and then you might land up working on some library. Its very hard (i would imagine) to plan your whole career exclusively as a library developer.
The point i am trying to make is - many of these are sub-track of backend developer track, because of how recruitment process works. Sure, it's good to think about them, but very hard to plan your career around one specific sub-track.
Not necessarily. For instance, in my current role, I'm the lead database administrator for a company. Nowhere in the job description or hiring process was programming apart of it. However, the role was mostly open-ended to "solve things as you see fit". There were some internal tools already in place, as well as 3rd party tools. I lead the initiative to replace the external tools with internal tools that better met the company's need, as well as re-write the internal tools. This lead to the creation of some re-usable libraries that are now available to other teams.
And this is a trend I've repeated countless times in the tech industry. My first "real job" ~16 years ago, I was hired to simply do data entry for an early ecommerce company. I wrote some code there to automate most of the process.
None of this is what would traditionally be thought of as "back end" development, as none of this had anything to do with web dev at all. These would be more categorized as "process automation" which historically landed under titles such as Systems Analysis and Design.
There are many paths to becoming a dev, and many destinations that are not even remotely related to web dev. :)