For Sr+ Engineers: Frontend, Backend, or Full-stack?
For the engineers that have been around a while, been successful in what they started with, and started to get more opportunities. How did you navigate yourself through what you wanted to get better at as your career progressed?
For example: I know some engineers who start in UI and then be moved to the backend because either that business' harder problems are in the backend and/or the manager thinks that is where the harder problems lie. (Seems to be an anitiquated belief amongst older tech managers that backend is inherently harder)
Or: You start on either end of the stack and move to being more "full stack" to make yourself theoretically more flexible and definitely more valuable to smaller companies that need breadth more than they need depth.
Finally: There's those that seem to go super deep in what they're doing. I kind of put library devs in this bucket due to how well they need to know their domain to build the tools that they build. However, there is just a different form of breadth that emerges there with needing to think through all the possible use cases of your library and how people will interpret it.
Anyways, I think this is a topic that a lot of engineers have to address as they mature and am just curious to hear how people approach this.
For example: I know some engineers who start in UI and then be moved to the backend because either that business' harder problems are in the backend and/or the manager thinks that is where the harder problems lie. (Seems to be an anitiquated belief amongst older tech managers that backend is inherently harder)
Or: You start on either end of the stack and move to being more "full stack" to make yourself theoretically more flexible and definitely more valuable to smaller companies that need breadth more than they need depth.
Finally: There's those that seem to go super deep in what they're doing. I kind of put library devs in this bucket due to how well they need to know their domain to build the tools that they build. However, there is just a different form of breadth that emerges there with needing to think through all the possible use cases of your library and how people will interpret it.
Anyways, I think this is a topic that a lot of engineers have to address as they mature and am just curious to hear how people approach this.
