Please don’t study these things if your goal is to futureproof your career.
Yes, they are all shifts in thinking (graphql takes us back to soap, for example, just with json this time instead of XML).
But in tech there are CONSTANT shifts in thinking. These aren’t special.
Yes, they are all shifts in thinking (graphql takes us back to soap, for example, just with json this time instead of XML).
But in tech there are CONSTANT shifts in thinking. These aren’t special.
Now if you can get to a place where you see the shifts more generally, that might be useful.
But you can build super cool & useful things even if you don’t. Even if you just go deep on what you know now, you can have a long, fulfilling, remunerative career.
But you can build super cool & useful things even if you don’t. Even if you just go deep on what you know now, you can have a long, fulfilling, remunerative career.
p.s. The tech skills themselves are the least important thing long term.
I know they seem like everything when you’re starting out, but the more you’re here, the more you’ll see that the main career-limiter for most developers is communication skills.
I know they seem like everything when you’re starting out, but the more you’re here, the more you’ll see that the main career-limiter for most developers is communication skills.
Anyone who tells you to study certain tech areas must be so early in their career that they haven’t figured out yet - communication with other humans is the only constant.
Just saying - might want to take that into account when choosing whose advice to consider. 🤔
Just saying - might want to take that into account when choosing whose advice to consider. 🤔
