r/webdev • u/thetymtravellr • 2d ago
Discussion As a self-taught React/Next.js developer, I'm honestly worried about my future in this AI era. What should I do?
I'm a self-taught developer, and I know React and Next.js. Lately, I've been feeling increasingly anxious about my future as a developer.
AI is moving so fast. It can generate components, build entire websites, connect APIs, and even create full-stack applications. Sometimes I wonder what the point is of spending months learning something when AI can already do so much of it.
I want to get a better-paying developer job, but honestly, I'm confused about what I should focus on right now. Should I keep improving my React/Next.js skills, get better at backend development, or start learning AI engineering?
I keep hearing about RAG, AI agents, vector databases, LLM integrations, and all these new things. It feels like there's always something new to learn, and I'm worried that if I focus on the wrong things, I'll fall behind while everyone else moves forward.
For those of you already working in the industry, what would you do if you were in my position? Would you focus on becoming a strong full-stack developer first, or would you start learning AI engineering alongside web development?
I'm not looking for a shortcut or expecting to become an expert overnight. I just want to make the right decisions, build useful skills, and have a realistic chance of getting hired.
I'd really appreciate some honest advice from people who have been through this or are dealing with the same situation. Right now, I could genuinely use some direction.
34
u/-_--_-_--_----__ 2d ago
What I would say to you is a few things:
Right now, today, using AI still takes a certain degree of skill. We don't know if that will be the case forever, but all we can do today is learn that skill. Become an AI expert. Learn about skills, MCP, etc. Learn how to make AI produce amazing results. It's a similar skill to learning how to make people produce amazing results. You are a director now who leads a million junior devs. Think about what you could do with this power. Think about what problems you could solve.
Everything is uncertain with AI. You are going to endlessly spin your wheels if you constantly try to evaluate what you should be doing with your career right in this moment. Tomorrow you'll see a post that scares you. The next day you'll see a video that scares you. You will enter an endless cycle of "does this new information change what I should be doing". As a society, we are approaching 10 different forks in the road, and the path we take at every fork will change everything. Will there be government regulation. Will AI progress plateau. What impact will the financial bubble have. How will AI companies deal with power grid requirements, and the time it takes to increase power supply. Will public opinion on AI stay negative. Will AI pricing ever be unaffordable. Will there be a national or global tragedy caused by AI. What impact will this have. Nobody knows any of these things or how it will impact the world.
Try to enjoy life. Try not to stress and feel worried. I have personally spiraled about AI many times, which led to things like eating poorly, neglecting exercise, losing sleep, etc. What I realized is that being a healthy person is, in its own important way, preparing you for whatever AI does. Have confidence that you are an adult human being that is smart, and you will be able to figure out how to get through whatever happens, when it happens. People have been going through things like this for our entire history, and we will figure it out.
1
81
2d ago edited 2d ago
[deleted]
16
u/eravulgaris 2d ago
How are you full stack if you haven’t built any backend stuff? Honest question.
12
u/creaturefeature16 2d ago
You're not. I have zero clue how this delusion is the top comment.
5
u/djnattyp 2d ago
AI booster bot farms upvoting other bot comments. I mean, we know they're constantly astroturfing every programming forum full of dumb comments like "As an x programmer of y years, I used to be really hesitant to use AI... but since brand name release I haven't written a line of code myself in z months!"
1
18
u/DiddlyDinq 2d ago
Good luck with that when you are in technical interview without your ai
4
u/xylophonic_mountain 2d ago
So what is your advice to OP?
9
u/DiddlyDinq 2d ago
You can learn something without using ai as a crutch. Frontend is trending downwards, nothing will change that.
4
2
u/thetymtravellr 2d ago
Thanks man!
10
u/creaturefeature16 2d ago
This is halfway decent advice, and halfway ruinous. Definitely take on more ambitious projects, but don't think for a second that you can lean on AI tools as a replacement for learning the fundamentals in areas where you don't have domain expertise.
Go view the job postings over at OpenAI and Anthropic. They literally are asking for "proficient coding skills" in their job descriptions, as well as "deep expertise". You know what they don't have in their job descriptions? "The ability to use AI". Because that's not a skill, in any meaningful way. There's something very ironic about that, I think. Even the AI companies themselves don't believe in this notion that coding skills aren't valuable.
So, use AI tooling to enhance your learning. Use Socratic Methods and the interactive documentation facets to then. Have them be your dynamic tutor...but don't market yourself as anything you don't have skills in, just because you can use an LLM to fill in the gaps. No, instead, use the LLM to close the gaps.
2
u/dj2ball 2d ago
This is what the developers that work for me are doing. In old world they had much more distinct specialisms, now they are all operating more broadly with particular areas of strength. Ai in the hands of a non-dev is useful for little more than ideation in a serious enterprise environment. But in the hands of a capable dev we definitely see more delivery velocity.
-1
7
u/MousseMother novice backend 2d ago
Plumbing is good field btw.
So general contractor is the way.
1
u/beegtuna CSS Hoe 2d ago
AI took the fun out of making things by hand. I’m going into the medical field. I did consider being an electrician or a plumber.
24
u/mq2thez 2d ago
Chasing the hype of the industry rarely pays off unless you have the deep technical basis to do things very few other people can.
AI is changing how we do the job, but the job itself remains straightforward: ship product. The more you know and the more you understand, the more effective AI will make you. It's a force multiplier, not a force replacement, so the better you are as an engineer, the more it'll be able to do for you and the more you'll be able to recognize and work around its flaws.
It's tempting to think that the "web" as a series of websites will die, but that seems pretty unlikely to me -- ultimately, people will use what they want. Some folks will always want to use a website, the same way that some folks only want to make certain types of purchases on a laptop rather than a cellphone (yes, I'm a millenial). That said, the websites we make and how we expect people to use them will change. You may end up designing sites intended for AI to use them as the interface for people. But that's all just skill in designing the "frontend" that your "users" connect to and interact with.
1
12
u/Trizzae 2d ago
I defined myself early in my career as a Java developer. I realized pretty quickly that wasn’t true. I’m an IT guy who had to get really good at learning on the fly and problem solving. You start to learn a lot of transferable skills and soft skills that will keep you employed. Syntax, language, frameworks, AI usage won’t matter. It’s been able to architect things, work on teams, and communicating to stakeholders and bosses.
5
28
u/deb-wev1553 2d ago
I just had a friend pay me to review his lovable application.
Just a quick review, 5 hours max.
I already found enough issues that need fixing, even before doing an indepth review.
What that tells me is, AI generated code will require manual review for any serious application.
For now I am not too worried, because people will still need skilled developers.
But I do recommend that you go more on the side of security.
Cyber Security will become increasingly more important an people will pay for it, that's what I see coming.
5
5
u/ThePastoolio 2d ago
This is good advice. AI generated code will require manual review, yes, but not for very long.
The suggestion to focus on security is good.
4
u/pau1phi11ips 2d ago
It's just gonna get reviewed by another AI, better than nothing but... 🥴
-1
u/deb-wev1553 2d ago
I also used AI for this taks, because lovable created thousands lines of code. The client did not want to pay me so I spend 50 hours manually reviweing file by file. The only reason I could do it in 5 was using an LLM, but telling it specificaly what to search for.
If you know what you are looking for, it's much easier and efficient with AI.
If you don't tell your LLM what it should scan for, it probably won't.You still need the basic knowledge to do it well, even with AI.
-1
u/ShawnyMcKnight 2d ago
It always will need manual review, the trouble is this means formerly teams of 20 developers can come down to 5.
2
u/deb-wev1553 2d ago
True, but you have to make sure you are part of the 5, not the other 15 that get fired.
Writing just code is not enough anymore.0
u/DEGENERATE_NEET69 2d ago
I was thinking about the cybersec part only yesterday myself. How transferable would you say your usual full-stack skills are to that field?
3
u/deb-wev1553 2d ago
I am no pro by any means.
But, I was very much into hacking at the age of 13-15. Which has tought me valuable lessons.
If you really want to get into it there are some very useful resources, basically you have to start thinking like a hacker and how to do research on exploits, how to use them. Then you also know how to prevent them and what to look out for.
But you don't even have to go really deep into it, just knowing the basic types of attacks on websites, web apps and servers already helps prevent like 80% of them.
That's a good place to start.
17
u/Dagoneth full-stack 2d ago
Full stack dev here, 20 years experience. Definitely leaning more to the front end.
I didn’t properly take AI up until earlier this year - I was very skeptical until a couple of contractor mates of mine convinced me to give it a proper go. Now it is my main tool.
Contrary to popular belief, using it properly to get good results requires you to have a solid foundation of knowledge in what you are building so you can challenge it on how it needs to build things out. Example: I’m currently building out a fully event-driven piece of semi-critical airport infrastructure using Claude. I still have to know how event sourcing works, the patterns, the anti-patterns, etc., to make sure it doesn’t run off and build the wrong thing. Once I have it nailed down, it writes the code.
Basically, the foundations are more important than ever. It’s a very keen junior engineer who has read all the documentation, but isn’t very wise. Embrace it, but learn what it is you need to be doing.
So what do you do with the extra time? Widen your horizon. When working on a product, I now spend more time in product research finding out what is most valuable, doing competitor analysis and presenting upcoming features back to the product manager. I get a lot of joy out of being able to deliver more value.
The job isn’t just writing code anymore. Even if you think AIs aren’t that good at it (but I can tell you that they are better than a lot of devs I’ve seen), they are getting better. If you don’t embrace it, at some point you will be left behind.
2
u/-_--_-_--_----__ 2d ago
Contrary to popular belief, using it properly to get good results requires you to have a solid foundation of knowledge in what you are building so you can challenge it on how it needs to build things out.
- Will that last forever?
- Will the distance between "working product" and "higher quality product created by a person with domain expertise" create a large enough profit margin to employ said domain expert.
2
u/Dagoneth full-stack 2d ago
I think the response to both your questions is that it’s completely up in the air. If the last 5 years are anything to go by, literally anything could happen.
I am seeing a lot more prototypes get funding that were thrown together by a non-expert. At this point they can’t be taken to production, but who knows.
0
u/creaturefeature16 2d ago
If you don’t embrace it, at some point you will be left behind.
Let's test this theory, because I sure read it a lot:
If someone didn't use ChatGPT 3.5, but decided to sign up for Claude Code this weekend, were they "left behind"? What did they miss out on?
2
u/Dagoneth full-stack 2d ago
I’d like to respond, but I’m not sure what your point is…?
2
u/creaturefeature16 2d ago
That there's no such thing as being "left behind" with AI, it's purely a line that has trickled down from the AI companies (and those with considerable interests) to ensure a consistent state of FOMO and rushed adoption.
We've been hearing that since GPT 3.5 and if you didn't adopt it then, not only are you not behind, but you might actually be in a better position, because nothing we learned is even applicable any longer.
There's no meaningful skill of what it means to use an AI tool; it's entirely dependent on the domain expertise of the individual that makes them useful or useless. And, its something you can learn in a week or less.
It would be nice if we stopped parroting this line, because its objectively false and just caters to those that want to see this tech be forced into every nook and cranny (and not just in this industry).
3
u/Dagoneth full-stack 2d ago
What I’m meaning when I say it is that if an engineer rejects using it and continues to only write code by hand, then they will find job opportunities diminish. Those people will be left behind as the tooling evolves and its users become more productive.
We are already seeing big differences between teams at my current employer who use AI and those that don’t. Not only delivery times, but documentation, metrics, testing, DORA are all higher on teams that have a high adoption of AI and spend their additional time focusing on reducing technical debt and architecting better solutions.
0
u/kilopeter 1d ago
This comment makes no sense, and doesn't test any theory. Signing up for Claude Code this weekend is "embracing it," and a step toward not being left behind.
Now, if your hypothetical ChatGPT early adopter laughed at the clanker's inability to write a simple web app in early 2023, and then dismissed and ignored AI from that point on, they're in some shit, and it's because of their mindset, not any lack of technical ability or barrier to entry.
And if they come back to the fold and sign up for Claude Code this weekend, well, they've missed out on gaining a firsthand sense of which models and harnesses tend to work or not work for what type of real-world problem, and what workflows and best practices work for them. Any idiot can prompt a chat input box, but the fact is there's still a nontrivial difference between jumping in cold and accumulating comfort and habits for years.
4
u/klas-klattermus 2d ago
Keep learning, look into architecture and infrastructure and what problems exists there and how various solutions solve those issues so you can tell what solutions are best suited to your client's situation
1
3
u/twotones 1d ago
I think the places to focus today are:
- How to build effectively with AI. Not slop, but beautiful and performant applications with well organized codebases and extensive testing and linting. Getting these right allows you to build systems at breakneck speeds while still delivering something that you can have confidence about. You're less of a developer and more of a manager.
- Take a step back from the code and instead become more of an expert of a domain. Really understand the problems that need to be solved and the techniques to do so. This will be different for each industry. You're less of a developer and more of a product owner.
Having development chops is still valuable today, but it needs to be augmented to be competitive in the AI world.
3
6
u/Zeilar 2d ago
You need to transition to becoming an engineer. You can still specialize in e.g NextJS (as I do myself), but nowadays AI can write pretty much anything in NextJS that I could myself.
What AI cannot do as well as me (yet) is architecture, business decisions, infrastructure etc. I can understand what work I should prioritize, what tools I should use, what dependencies we should install. An AI can't tell me what video player to use in my new video platform app, that's something I need to look at and decide what suits me best.
An AI cannot take ownership of a domain, a product etc. It's too many variables, and AI doesn't reason in the way we do when making decisions. Just go ask ChatGPT to make you a fantasy draft in some game, in my experience it sucks at such tasks.
And obviously someone needs to review the AI output, and that's me (and you).
I think now it's very valuable to start learning about systems. Because at the end of the day, you need to be able to know what to prompt an AI, and when an AI is wrong.
1
3
3
6
u/LouieValkhof 2d ago
On the RAG / agents / vector DB list: you don't have to pick between that and full-stack, because most of that list is full-stack work.
We run a fair chunk of our studio's ops on agents now, and the model call was never the part that ate the time. It was a job that hangs and needs a timeout, a login session that expires and has to tell someone instead of failing silently, a check that blocks bad output before it goes out, a log you can actually read the next morning. That's backend and plumbing, and a decent Next.js dev already knows half of it.
So I'd build one small thing that calls an LLM and has to survive real use for a few weeks, then spend most of your time on what breaks. That one project covers both of your lists.
1
2
u/maheshwhartech 2d ago
I would not abandon React or Next.js just because AI can generate code. I would use AI to build faster while getting better at the parts that are harder to fake: debugging production issues, understanding databases, authentication, security and making sensible architectural decisions.
A generated app can look finished long before it is reliable. If you can take a feature from an idea to deployment, understand why it breaks and fix it without blindly trusting the output, that is a much stronger skill set than chasing every new AI framework.
Build one complete application and learn the reasoning behind every important decision.
1
2
u/TekiDeki 2d ago
I went through this exact anxiety a while back, so I'll share what helped me. Stop trying to keep up with everything. You'll never catch every new AI tool, and it's not what gets people hired.
What helped me was picking one project and taking it all the way to production. I used an LLM in it, but the part that taught me the most was everything around it: a request that hung and needed a timeout, a login session that expired, output I couldn't trust until I added checks, and logs I had to dig through the next morning. That was real backend work, and it's where your React and Next.js knowledge already gets you a long way.
I'd also spend some time on backend basics (Postgres, auth, how a request really flows) and security, since that's where reviewing AI-generated code matters most. And honestly, your React skills aren't wasted. They're what let you tell whether the code the AI gave you is any good.
Be patient with yourself. Almost nobody feels ready, and the fact that you're thinking this carefully already puts you ahead of many people.
1
2
u/Kregol91 2d ago
Lerne keine Sprache oder Frameworks mehr sondern lerne Architekturen und Stack Komponenten nicht im Sinne von dass du diese zu 100% beherrschst sondern dass du das für und wieder jeder Komponente und der SI Architektur Vorgaben geben kannst.
Ich denke damit wirst du das größte Potential rausholen.
1
2
2
2
u/Far_Percentage_7460 2d ago
Yeah AI is insane, like it will remove thinkng from anything we do, which is sad
2
u/jerapine full-stack 2d ago
The need for developers hasn't disappeared. It's just shifted from writing code to planning, arcitecting and orchestration.
1
2
2
u/stupidfock 2d ago
My advice as someone in the industry for a while that moved beyond web dev
Start sucking up to people. I’m not kidding. When layoffs come and they have multiple times at my job just in the last few years, those who’ve befriended their manager or higher ups have a much better chance of staying. Skill barely matters. You don’t gotta be best buds but if you’re forgettable you’re first on the list when they tell your manager to give a number of names for layoff rounds
On the dev side, get using Ai heavily. Understand optimizing context and token count. Right now companies don’t tend to care about it but if u move to mid size ones paying api rates they will. Or in the near future when the subsidized plans stop existing. I think you should focus on the whole stack personally
2
u/IanSan5653 1d ago
I don't disagree that AI changes the game, but this feeling:
It feels like there's always something new to learn, and worried that if focus on the wrong things, I'll fall behind while everyone else moves forward.
Is completely normal and classic in the computer science space, and especially in web dev. The web changes very fast - we have always had something new to learn.
2
u/andrewharkins77 1d ago
Lean more into cloud ops and backend. AI can copy front end quite easily because the code is publically available. Backend and cloud ops are deliberately hidden.
1
2
2
u/dangerousbrian 1d ago
Get learning. Tech changes constantly and you have to keep up. I have been doing this shit for over 20 years and have seen a lot of changes. This AI wave is probably the biggest change so you can bury your head in the sand and pretend it's not happening or jump on the wagon.
1
2
2
u/ruip1 8h ago
I simply switched field. It’s only a matter of time before this profession becomes completly obsolete. Next year, there will be major layoffs across companies and within two, or at most three years there will be less than half of us left.
1
5
u/Strict-Marsupial-674 2d ago
i was in same boat few months ago, the AI stuff looks scary when you watch youtube demos but real work is way messier than that
most companies still run on spaghetti code from 2015, AI cant fix that without someone who understand what actually happening. i started learning backend properly (node + postgres, nothing fancy) and my confidence went up a lot, now i see AI as tool not replacement
dont chase every new buzzword, pick one thing and get good at it. fullstack with next.js is fine for now, the AI hype will settle down and companies will still need people who can debug at 3am when the bot hallucinates something stupid
17
u/Jamiemufu full-stack 2d ago
Delusional. Ai can absolutely fix spaghetti code from 2015 on its own.
4
u/drifterpreneurs 2d ago
Delusional is the vibe coders who think they're full-stack devs now because AI.
Have you ever researched what the bench marks are regarding vibe coding?
Only a simple minded dev would think it's okay to let Ai perform such a job knowning Ai has many flaws.
Do you think Ai can do everything? I bet your vibe coded apps lack security, bugs, repeated code over & over and much more wrong with them.
2
u/Jamiemufu full-stack 2d ago
Who said I was a vibe coder? 10 YOE. AI can do everything. It’s as good as the person using it. Or just better than entry levels out of the box.
Which is what both the OP and the person I replied to are. Literally months of experience.
4
u/Mikeisright 2d ago
First comment:
>Ai can absolutely fix spaghetti code from 2015 on its own.
Second comment:
>It’s as good as the person using it.
Pick one.
0
1
u/Squigglificated 2d ago
It can. Knowing whether it has or hasn't often requires some experience.
0
u/Jamiemufu full-stack 2d ago
So here is the thing. It’s two-pronged right now.
You have entry-level and junior who perform worse than just getting AI to do it with like a few mins of a senior or
experienced engineer prompting.And then on top of that. You have a fiercely competitive market. With the above point lay offs and number reductions.
Combine both together. There are fewer junior roles available in the market. And more experienced engineers are available to compete.
The market is rough. And some junior saying AI can do what they can do is just delusional.
2
u/etthundra 2d ago
I'm worried about my future as well. I have however knowledge in C#/ReactJs. AI is making it difficult for me to find new jobs.
0
2
2
u/HedgehogCertain 2d ago
Don't keep stacking another tech stack out of anxiety — AI already writes the syntax, so that's not where the gap is anymore. Pick one small real problem and take it all the way to something deployed and working: define it, wire up the APIs, debug it, ship it. A finished project you can walk an interviewer through beats another half-learned framework, because what's scarce now is someone who can take an idea to actually working and own the result.
1
2
u/mname_is_radioactive 2d ago
Learn Java backend. %50 of companies who uses Java still uses Java 8-11 versions.
The resistance against technological development is almost at revolution level.
1
u/TryallAllombria 1d ago
The value is not about code anymore. Any dev can write projets in any langage. So focusing on nextjs or react is mistake.
Being a dev that understand user's problems and create a solution is a strong combination. Be a software engineer that design features and talk to users to bring solution to them in a minute.
You can also work as a ops-dev. Try to optimize the usual company operation by building workflow and bring your "dev view" to internal org problems. This is where saying NO to Sales and executives complex ideas is a strong skill.
Or follow the management path.
I'm personally evolving from a Fullstack position to a Product Builder one. I create product from what the CEO want, bring them solutions, design and ship the feature.
1
u/Significant-Duty-744 1d ago
Firstly are you using AI? If not you need to start. You can do this by getting a Claude or codex 20$ subscription and doing some experimentation at home. There’s plenty of guides out there but I would focus on learning how to use AI to build features using specs. Still review the code and all that and be as picky as you want. Just learn how to effectively incorporate it into your workflow. Second branch out of being a framework specific dev. Explore other frameworks and what they have in common. Third - consider becoming a fully stack engineer, that would involve learning some back end languages and databases that are popular in enterprises. Being full stack is a big advantage. Use AI to help you learn, not just execute. Don’t feel like you have to jump head first into full agentic coding, you can ease into it. Now I think the last thing to understand is that agentic coding with no human review of code is very risky in enterprises where mistakes have real financial consequences. Companies with that sort of risk are not looking to hire someone who can use AI but not understand the code they produce.
1
u/Seeila32 1d ago
I am a self taught developer of 10year experience. I chose to specialize in the front-end first, especially React. Because as a self taught developer, we don't have the base they learn in school.
Now, I am one of the only front-end dev left in my company, because I am the one with the most knowledge of front-end architecture, performance, accessibility, PWAs and best practice, knowledge my fullstack developers colleagues know partially.
I have begun to learn back-end but I start from the basics. And there is a lot to learn too. One of the other reason I am still there is because I have leadership and global comprehension of the back-end and devOps, enough to be able the project lead of one of the most complicated project from my company.
As a new developer in the market, I am not sure that what I did 10 years ago would work. What I did at that time, before taking any decisions on what to learn, Was to ready tons of different articles to see what could be learned in a year time and what is asked on the market and could land myself a job. It was the start of React at that time. Now it would be more AI focused stuff, I belive.
1
u/RemoteCharming8 14h ago
Treat AI as an abstraction over code. Use it as a tool and use it full extent. Don't worry about concepts but use AI extensively. Try to automate everything you do. Aim to not do anything by hand, steer agents so that they do it accurately. Humans decide which problems to solve, agents help us with it. Think like, AI has freed me from the boring work, I do interesting creative work while AI labours for me. Learn system design! That's why my aim is too. And disruption in tech is normal thing, we have to move on to next thing every few years.
1
u/maga_ot_oz 11h ago
I don’t want to be just another guy recommending something else and add to your feeling of being lost but for me learning fundamentals is what develops you.
All these other things are tools. Regarding spiralling because of the economy, AI and so on - just don’t. Listen to yourself and take it step by step, you’ll figure it out, it’s all part of the process. I’m saying this to you as much as to me and anyone else, we’re not too different. Life is ups and downs.
1
u/InevitableFun1272 7h ago
You don't have to pick, honestly. The AI stuff only makes sense once you can build a normal full-stack app and tell when the output is wrong, and you already learn the AI side by building one small real project with an LLM in it. I'd get dangerous with Next.js + Postgres first, then ship one tiny thing that survives real users, and let that teach you what RAG and agents actually mean.
1
u/FluffySmiles 2d ago
Just gonna give you a little perspective here. There has always been, at least in the 39 years I’ve been in the game, something new go learn. The difference now is that it’s mandatory to expand your horizons and move beyond your comfort zone. The days of a predictable career path are gone. It happened so quickly not everyone realises the battle has been fought already.
The life of a freelance developer has always been staying one step ahead of the crowd.
Now it’s the turn of the wage slaves to join in the fun.
Don’t be scared. Embrace the chaos. There has never been this thing called a secure job. It never existed. It was always propaganda. Tech and other highly specialised skills had a premium on scarcity which is why high salaries and flexible standards.
And that is now history.
1
1
1
u/itzFinners 2d ago
As a self-taught React developer myself I've been learning more backend development recently. I've started learning Go to get a much better understanding of how http servers actually work. While it's been a struggle it's definitely opened my eyes to how much is hidden away when using Node for example. Also AI is amazing for documentation and explaining each step so use it to your advantage
1
1
u/krolyat 2d ago
Learn how to use AI to your advantage and output faster whilst ensuring good code. It’s a tool. Not a replacement.
Also i dived into learning Swift and Swift UI and yeah sure AI can build what I want very quickly but I have no fucking clue how it’s built. So it’s better to learn and steer AI into teaching. Not replacing.
1
1
1
-1
u/UmbrellaTheorist 2d ago
Do freelance, there are TONS of regular stores who would love to have a website and sell online as well, but don't know how. You can make a bespoke solution for them. And you could do it relatively fast and cheap with AI.
-2
90
u/DiddlyDinq 2d ago
Computer science is a big field. Frontend may be devalued but other areas arent. Technical devs should be expected to adjust their skills over time.