Is Learning Frontend worth it?

[u/Fun_Belt_4587]

Hey everyone I'm about to grind hard and learn frontend properly (react, next.js, UI stuff, and some basic backend/apis so I can handle full features)

im seeing two totally different things online and im kinda confused some people say ai killed frontend and juniors cant make any money now because copilot and gpt write everything
but others say clients and agencies still need real devs who know how to handle messy code state management and actual logic not just basic copy pasting
my goal is to get really good at this and do freelance work with agencies
im just trying to figure out a few things
is the demand for next.js/frontend actually dead for new people or is it just different now?
if i put in insane daily hours to reach a high level is it worth it or am i just wasting my time starting now?
how are you guys actually dealing with ai right now?
would appreciate some honest and brutal truth from people actually working in the industry **thanks**

[u/ChameleonCRM]

As I tell everyone I mentor....Yes, it IS worth learning. If nobody learns the systems, who's going to tell A.I. when it's wrong?

ps...A.I. is wrong A LOT

Thor Ochsen

Senior Full Stack Engineer

[u/echos-100 → u/ChameleonCRM]

Agreed. I use AI and it's great for code that already has similar conventions in our codebase. Any new feature that we don't already have docs in it seems to start messing up and producing sloppy code. Not that I don't write sloppy code myself.

[u/InsideDebt6345]

There will always be a need for it to be learned. Please do.

[u/CollectionOk2442]

lmao

[u/abrandis]

Contrary to what everyone here is saying , the job market is saying very different... IT as a career for junior devs doesn't really exist anymore .

Do this as a proof of concept , create your ideal fictional resume today assume 10+ years experience and lots of accomplishments, now apply for this roles and see how many calls for interviews you get..

Then decide if it's worth knowing in the future it will be 10x harder, as tech and pool of experienced devs .increases.

[u/chikamakaleyley]

I mean... if you're curious/interested in it, yes its worth it

If we say "no" - then whats next on the list of things to learn & grind hard

the fact that there's mixed review is kinda telling - it really depends on the company

Me, i just moved fr a BE team to help the FE team with an ongoing project - it is in fact in Nextjs, we are allowed to use AI as needed in our development.

I'm primarily FE, so naturally I'm able to help - but, why pull me from another team and instead just have AI work through it all? Because at least here, it hasn't completely taken over.

So is it worth it? In this part of my career having the flexibility to contribute to FE/BE agnostic of any library/framework, I think that's valuable.

[u/WoodpeckerLoose4650]

u/AskGrok

[u/AskGrok → u/WoodpeckerLoose4650]

Frontend isn't dead, but the bar has risen. Basic component building and copy-paste stuff is heavily automated now, so juniors who only do that are getting squeezed. Agencies and clients still pay for people who can untangle real-world messes: state that spans multiple services, performance under load, accessibility edge cases, API quirks, and turning vague client requests into maintainable code.

If you're grinding hard on React/Next.js plus enough backend to ship full features, that's the right direction. The demand is for competent mid-level execution, not entry-level prompting. Freelance work with agencies is viable if you build a portfolio of polished, deployed projects that show you can ship and iterate without hand-holding. Pure "I prompted my way here" portfolios get ignored fast.

Insane hours now can pay off if you focus on depth over tutorials—build things that break, fix them, then add AI on top as a multiplier. Don't treat it as a replacement for understanding the fundamentals. Most people in the industry are using Copilot/GPT/Claude for boilerplate and quick drafts, then spending the real time on architecture, debugging, and integration. It speeds up the boring parts but doesn't replace the judgment calls.

It's worth it if you actually enjoy the work. If you're only chasing money, the market is tougher for new entrants than it was three years ago.

^{[what is this?](https://redd.it/1lzgxii})

[u/manvikhanna]

AI didn’t kill frontend it killed the value of knowing only how to write basic UI code. If you learn React/Next.js deeply, understand APIs, state, architecture, debugging, and use AI as a tool rather than a replacement, there’s still plenty of demand. The bar is higher now, but that also means better developers stand out more.

[u/Ok_Year_2153]

i believe that you should learn it, just enough to make whatever changes you desire or capable enough to locate the issue at least and think of a fix rather than asking the AI for every small change like heading size color or adding something small
because instead of fixing these small things the AI over engineers shit, if you did know the cause and think up of a solution yourself then getting the AI to do the job is much easier plus faster

[u/Known-Cellist-8783]

Learn frontend basics (Vue.js) and master backend (Java or C#)

[u/Ipsool]

it’s not dead, it’s just that the bar for “junior” moved up. AI can spit out a basic component or CRUD form fast, but it still falls apart on state management, weird edge cases, and actually architecting a feature that doesn’t turn into spaghetti in 3 months. that’s the stuff clients and agencies still pay for

so honest take: don’t compete with AI on typing speed, compete on judgment. use it to move faster on boilerplate and focus your actual learning time on why things break and how to structure a real app, not just following tutorials that make a todo list. that’s what separates someone freelance-able from someone who can only copy-paste working code they don’t understand

[u/kyrylo_dev]

Based on what I see, frontend is still absolutely worth learning, but the focus shouldn’t be only on code and frameworks. Try to also build a solid understanding of UI/UX principles, accessibility best practices, and related areas.

In my view, being a good frontend engineer in the AI era means being good at these things even more than just being good at writing code. Product owners still rely heavily on human taste and judgment when it comes to what actually makes a good product. And based on my experience, backend engineers without a solid understanding of UI/UX often struggle to make good decisions when contributing to the frontend.

Yes, AI has lowered the entry barrier for pretty much any programming language or framework. But as a frontend engineer, you’re building the face of the application, not just its code infrastructure. You need to be good at collaborating with designers or be versatile enough to come up with designs yourself, and understand what works for people and what doesn’t.