Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
As long as you internalize the language fundamentals and good engineering practices, you'll find it easy to jump ship when you need to.
There is risk to being a one trick pony though, learn some spring boot on your spare time.
sleek31361yI was a web developer and they are sometimes split into frontend / backend only as well. Similar to how you are a frontend android dev.
But just like how frontend web devs eventually taught themselves some backend so they can freelance and sell an entire product, you should consider learning some backend as well since its basically the same.
it certainly took me more than a few months to be able to write good frontend web applications, backend apis, and deploy both on virtual servers but being full stack is just more flexible these days.
i was a web dev, and a year ago i changed to backend only which was the best decision i ever did. being specific is more comfortable but being full stack lets u change jobs more easily.
so by all means i advise u to learn backend and dont consider it as spreading urself too thin.
@sleek backend world is so much different. From what i have gathered, There are iaas paas saas which defines the level of work one does on designing the backend. Firebase is a saas backend that i have worked with a lot.
But i can never call myself a backend dev because firebase is limited and not everyone wants a firebase backend. Those aws instances , virtual clouds and vm/docker handling nodejs devs are hot these days and i guess i have to learn that. Plus there is something called postman that idk how or why you guys use it, but its somehow super big company and a very important tool
i have coded APIs, and normal web backends using normal vanilla PHP, Laravel, CakePHP. I integrated several payment providers, auth providers, used many and no ORMs, used relational and non relational DBs, basically any combination of ways u can do a backend probably came up in a project at least once. I have been working as a full time backend dev for 2 years now. and full stack before that.
YET i have no clue what iaas, saas or paas is. I have never used Docker nor do i know how to. I use insomnia not postman :) and both are just fancy UIs for running curls (http requests).
The difficulty related to something u ddnt get into yet always appears hard... once u decide to do just one or two projects with their backend by urself ull find out its really easier than what ur making it out to be in ur head. at the end of the day most of backend logic is "get / add data from / to db", "send data or response msg to app as json"