3 ms·
There's several directions you could take. I was a full stack engineer most of the 2010s then took some time off to pursue my own venture. Now I'm working as a
by geuis 2y ago
There's several directions you could take.
I was a full stack engineer most of the 2010s then took some time off to pursue my own venture. Now I'm working as a backend engineer. It's a nice change.
If you have any interest in app development, you could pick up Swift or Scala (or whatever is used for Android development) and move in that direction. Conversely, Mac/Windows/Linux desktop apps is an option.
You might look at changing into more infrastructure roles.
- abje 2y agoThanks for the reply, how did you initially change roles to backend? Did you do it at the company you already worked for or was it an external change?
- geuis 2y agoI spent 2021 to about a year ago working on my own service. Since it was just me and the service was an api, I had to wear many hats. Had to learn more about backend needs and infrastructure than I had needed to know when I was just doing full stack work before. There's never a direct path. I'd suggest that if you want to move in that direction learn more about databases and api design (REST and graphql unfortunately). They're among the more popular api types these day. Not a graphql fan myself. At your current job, try to pick up tasks that are more backend focused. It's nice to get paid while learning. It also makes you more valuable to your company and may make you happier because you're doing a broader spectrum of work. Don't ever be afraid of asking questions from other people in different roles. Most people would be happy to spend a little time talking about what they're doing. Everyone is always stretched on time and if you can contribute to helping them solve some small problems that are in their backlogs, that's a good start too.