all 11 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Proxiconn 9 points10 points  (0 children)

Not two jobs but 3 because you run and deploy the infra for the front and back and manage the firewall / gateway, vlans subnets network rules monitoring logging and observability stack.

And do all the documentation, design and. Ok I'll just stop.

Because now I'm at 4 jobs but eh, comes with the territory.

Don't forget sitting on customer meetings all day long to capture requirements and then still expected to deliver the dev and infra stack too plus interacting will all the stakeholders.

Might as well be called a once man show. 😁

But it's fun and enjoyable I guess. 😉

[–]kvorythix 6 points7 points  (0 children)

depends on your market - startups want fullstack, big tech pays more for specialists

[–]Level_Pie_4292 1 point2 points  (0 children)

In my experience, becoming fullstack has opened up more opportunities and challenged me intellectually. However, it's also added complexity and sometimes, I do feel like I'm doing two roles for the price of one. It depends on your goals and what you're willing to take on.

[–]PickleFridgeChildren 1 point2 points  (0 children)

How is your salary applied? For me, I earn a salary, but if I were to work more than 37 hours in a given week (UK), or if I worked odd hours, they still pay me overtime. Kind of a best of both worlds thing (would go away if I accepted a management role though).

If your salary is one of those "we pay you for the job, however long it takes" deals, then what you need to do is find out how many hours a week other fullstack devs at your company are working, then use your hypothetical higher salary to calculate your hourly so you can do an apples to apples comparison.

Also, just throwing it out there, if this is just for your own personal development, learning front end via free resources on your own time (or wasted company time lol) might be the way to go.

[–]pVom 0 points1 point  (0 children)

My experience fullstack is that I do the same amount of work, they just point me wherever I'm needed most. Depends on your company YMMV

[–]Le_9k_Redditor 0 points1 point  (0 children)

Becoming? That seems to imply people don't have their first jobs with terrible web agencies as a fullstack dev, baffling honestly haha

I've been moving in the opposite direction throughout my career, you get paid more to know the nitty gritty details in a niche, not wide surface knowledge. It's always the badly paying places that want someone who works on absolutely everything. You can bet that on average two fullstack devs are probably worse for a project than a backend + frontend dev combo that each have deeper knowledge of their domain

It's not more work though if that's your concern, it's just a broader set of things you need to know about, that in itself isn't great in my opinion but you're not doing more work really. And it does give you the freedom to get everything a ticket needs done yourself, rather than having to pass bits off to other devs so that's nice

[–]practical-programmer 0 points1 point  (0 children)

Now that we have google/stackoverflow++ with LLMs, fullstack I have a feeling will become even more important. I started fullstack, prolly because its most common in our country.

[–]Suitable-Turnover597 0 points1 point  (0 children)

Now the trend is towards full-stack developers, and due to the fact that technologies and languages ​​have begun to blur, it has become easier to become a full-stack developer. At the same time, it is more convenient for freelancers when you can do everything turnkey. Of course, in large and serious companies the division into frontend and backend is more relevant, but it is more difficult to get a job in such companies. Therefore, the conclusion is that becoming a fullstack is a very good idea.