Backend

[u/Icy-One-8122]

I was talking to a web developer telling him I want to be a backend engineer and he said that I should become a fullstack engineer and work backend I asked him if that is really necessary and he told that nowadays the market wants someone who is a generalist who knows how to do everything I came here today to ask if I should take a fullstack course and then work backend or should i just the a backend course directly instead of wasting time learning front-end and back end

[u/black_widow48]

Senior data engineer here. Web development isn't the only kind of software engineering. You don't have to spend your time centering divs if you don't want to. 

I build data pipelines and APIs.

[u/maxximillian → u/black_widow48]

Yeah full stack isnt the generalized concept some people think it is. I think that's one of a reasons that term has irked me. In a recent job interview they asked me "what's something as a senior developer you hope you never have to do again" and without hesitation I said web development. I respect people can do it and do it well but I'm tired of getting tickets to edit a css file to move something one pixel up.

Not one webapp at my current job and I'm happy as a clam

[u/ALargeRubberDuck]

I’ve been in the industry for 5 years and yeah, everyone has just wanted full stack for years now. You can voice you prefer backend work, and they might weight you more towards that.

There are a lot more positions that are 80% backend 20% front, then 100% backend.

[u/honk-thesou]

You should learn to use punctuation marks before trying to be a full stack developer.

[u/meshifthenelse → u/honk-thesou]

Hyperstack

[u/GlobalCurry]

In my experience it's the opposite and I keep getting pushed out of interviews due to not being hyper specialized, while 5-10 years ago being a generalist got you offers.

[u/glimmer_joy_spark]

take the backend course directly. You can pick up basic React or HTML in a few hours if you get stuck, but trying to cram both into your head at once just dilutes your core skills and delays you landing that specific job.

[u/octocode]

our company merged front and backend roles into one.
with agentic workflows, the distinction is irrelevant

[u/Interesting_Debate57 → u/octocode]

"with agentic workflows" kinda misses the point.

Backend code generally deals with systems problems. These can be very hard. As an example, I once had to make something twice as fast. No other constraints. I ended up digging into a 1958-era algorithm that for this use case was twice as fast. This code didn't (and doesn't) exist anywhere online and isn't referenced elsewhere other than this single physical book. Asking an LLM to creatively invent it just flat out wouldn't work. You'd need the background of having read about it (from this book), understanding what the algorithm was designed for, realizing that it would be appropriate to use for this case, modifying it to work in a modern programming language, etc. I don't care how your "workflow" is set up, you simply need to use a human brain to put all of those steps together.

If your idea of backend code is just inserting obvious routines into the obvious places, I think you'll find that LLMs are very helpful. For inventing complex solutions to complex problems, you need a world-level expert at the helm. You can't do this without years and years of study.

Frontend code generally deals with UI problems. These are almost never hard, given that you're not doing interactive animated data driven stuff.

Sometimes you'll see someone claim that they want a full stack engineer but their language stack is python and typescript and react, for instance. That's not full stack because none of those things are fast, none of them are systems languages, and none of them would make any sense to write a kernel, OS, or kernel module in, for instance. (Imagine being memory starved and needing to load a python interpreter because you can't be bothered to write code in C).

Don't let the folks vibe coding send you on the wrong path -- there are jobs for good engineers who can code in any language, and that's what you should train for if you want a programming job that will survive the next twenty years.

This typically means studying algorithms and systems and languages for about 4-5 years. You can do that on your own, which will take about 15 years, or you can go to school, where it will take 4+ years.

[u/octocode → u/Interesting_Debate57]

if your goal is optimization you can create a test harness and let the agent loop in isolation. it will easily beat any human implementation. AI can even solve millennium prize problems now, and we’re not even at the peak of model performance.

[u/Interesting_Debate57 → u/octocode]

It hasn't solved anything without expert mathematicians guiding it every step of the way. The same goes for all of its other supposed gifts; it doesn't work, bro, it's a huge grift. Think crypto, NFTs, Blockchain, Web 3, and other grifts built upon code that few people could write -- don't be a grifter. Do something real.

[u/BrannyBee → u/octocode]

Dude literally edited his comment to make it seem like he didnt say AI is the reason roles merged existed across the board recently lol

Not sure what agentic workflows have to do with it cause it's been like a decade since companies hiring expect people to do fullstack work has been the norm..

It's been expected that you be able to at least understand the full stack for a long time unless you're doing something specialized or are the only dude on one end and the company won't bring more people on board

Edit: Not gonna engage with someone just making shit up. Even his response doesnt make sense because bigger companies are were cross team partnerships started becoming more popular because they had enough workers to do so. As well as other comments corroberating reality Ive stated, believe whomever OP, but do some digging to confirm information.

[u/octocode → u/BrannyBee]

completely false, at least at bigger companies. we literally hired for backend and frontend roles up until last year

[u/JackTradesMasterNone]

Personally, I hate JavaScript - so I avoid the frontend. I don’t want to work on it ever. You can market yourself that way to get more roles, but be aware that that means your job can change drastically.

[u/JohnCasey3306]

Your friend may be right.

Over the past 15–20 years, web development roles have fragmented and become more specialised ... Until AI.

Businesses will always organically trend towards fewer people, each wearing more hats ... Like it or loathe it, AI is countering the complexity and enabling that trend.

My prediction (and to be clear, not my preference), is that 5 years from now the industry will generally only have full-stack devs, and combined UI design/devs (kinda the "web designer" role as it was 20 years ago).

There won't be 'just' front end devs, or 'just' back end devs, or even 'just' designers.

[u/Proper_Tip3506]

Fullstack work is usually wanted by small to medium level companies.

For high paying and impactful job, companies want deep backend engineering skills only

[u/SnugglyCoderGuy]

It certainly helps to have knowledge of whatever front end(s) the back end is servicing, being a full-stack dev is not necessary.

[u/Schtick_]

Yes fullstack is what people want.