3 ms·

In my humble experience as a full stack dev, backend jobs are going nowhere. Sure stuff like firebase and similar works for CRUD apps but as soon as you want to

In my humble experience as a full stack dev, backend jobs are going nowhere. Sure stuff like firebase and similar works for CRUD apps but as soon as you want to do more specific stuff they usually are worthless. I have never used any of these backend as a service but I would assume you would struggle a lot with all kinds of data processing that needs to happen on the server side?

game_the0ry 6y ago
> In my humble experience as a full stack dev, backend jobs are going nowhere. Agreed, mostly. What I am trying to say is there is a lot of change in the back end of the stack and it's in our best interest to adapt to that change. But if you're not willing to change, your job security will become an issue.
game_the0ry 6y ago
> Sure stuff like firebase and similar works for CRUD apps but as soon as you want to do more specific stuff they usually are worthless. Agreed again, but the fact that you have the option to use Firebase at your discretion is better than not having the option to use. > I have never used any of these backend as a service but I would assume you would struggle a lot with all kinds of data processing that needs to happen on the server side? It depends on the use case, and that is key. Too many engineers spend too much time arguing on a hacker news that their way is the One True Way (Trademark) - that is not always the case. Your business needs should drive your tech stack choice, and no one tool is perfect. So if, like in your example, your use case involves a lot of data processing in the back end, then the choice is easy: favor building the custom server and associated data processing yourself, over using a BaaS or FaaS. However, if you are building a CRUD app where you have like less than 1,000 people using your app, you're time constrained, you don't have enough devs, then Baas/FaaS starts to become a more viable option.
chrismorgan 6y ago
(Language is funny in its subtleties. I read “backend jobs are going nowhere” as “backend jobs are a dead end where nothing interesting is happening, and they’ll dwindle away”. But the sense you intended was “backend jobs are not going to disappear”, which I would have worded “backend jobs aren’t going anywhere”, which should seem to mean the same thing!)

game_the0ry 6y ago

> In my humble experience as a full stack dev, backend jobs are going nowhere. Agreed, mostly. What I am trying to say is there is a lot of change in the back end of the stack and it's in our best interest to adapt to that change. But if you're not willing to change, your job security will become an issue.

game_the0ry 6y ago

> Sure stuff like firebase and similar works for CRUD apps but as soon as you want to do more specific stuff they usually are worthless. Agreed again, but the fact that you have the option to use Firebase at your discretion is better than not having the option to use. > I have never used any of these backend as a service but I would assume you would struggle a lot with all kinds of data processing that needs to happen on the server side? It depends on the use case, and that is key. Too many engineers spend too much time arguing on a hacker news that their way is the One True Way (Trademark) - that is not always the case. Your business needs should drive your tech stack choice, and no one tool is perfect. So if, like in your example, your use case involves a lot of data processing in the back end, then the choice is easy: favor building the custom server and associated data processing yourself, over using a BaaS or FaaS. However, if you are building a CRUD app where you have like less than 1,000 people using your app, you're time constrained, you don't have enough devs, then Baas/FaaS starts to become a more viable option.

chrismorgan 6y ago

(Language is funny in its subtleties. I read “backend jobs are going nowhere” as “backend jobs are a dead end where nothing interesting is happening, and they’ll dwindle away”. But the sense you intended was “backend jobs are not going to disappear”, which I would have worded “backend jobs aren’t going anywhere”, which should seem to mean the same thing!)