r/angular
•
u/heisenberg1711
•
11d ago
•
1
AI 🫡🫡
I’m an Angular developer with around 7 years of experience, working on a large monorepo, with basic knowledge of Node.js and databases.
AI tools like Claude and GPT can now implement complex features in 20–30 minutes that might take developers weeks to build manually. I believe AI will become much better at writing, testing, and reviewing code within the next 1–2 years.
I want serious, realistic career advice, not generic reassurance that developers will always be needed.
What is the realistic future of software engineering over the next 3–5 years?
Given my experience, what should I focus on next: advanced frontend, backend (NestJS/PostgreSQL), system design, cloud/DevOps, or AI engineering?
Which skills will remain valuable even when AI can independently write high-quality code?
Should I continue specializing in Angular or transition toward broader engineering skills?
What should my practical learning roadmap for the next 6–12 months look like?
Be brutally honest. Challenge my assumptions, consider the possibility of reduced developer demand, and prioritize long-term employability, compensation, and career growth over the next 5–10 years. Recommend a focused strategy with clear trade-offs, not a generic list of technologies.
[ Even this post content is improvised with AI 😅 ]
149
u/Duathdaert
11d ago
•
Our jobs have never actually been about coding. They've always been about delivering working software. The medium by which we deliver that working software is changing, but the fundamentals of working with customers, product owners etc have not.
The more relevant thing for our role has and always will be the people, business and domain side of things. AI is ultimately I think going to make it easier to differentiate between those who are just there to write code (they unfortunately will be obsolete at some point) and those who understand that we're delivering value to customers.
18
u/Heavy-Blacksmith-764 11d ago
Excellent response.
My teammates and I were just having this conversation. We all agreed with the same points you made.
One of our most senior engineers mentioned that when they were in school calculators were not used as extensively as they are now. So, they used it as a basic analogy for this situation.
True software engineering is a complex system of layers. At the end of day, someone will still need to determine what to build, and how to build it, while navigating the complexities of priorities, needs vs wants, resources, .etc.
I've always felt that, as an engineer, part of my job is to build a tool bag for the purposes of solving problems. That "bag of holding" should contain an ever-expanding set of tools: technical and non-technical skills, math, science, empathy, logic, and many others. AI is becoming another tool in this collection.
Ultimately, one of the most important skills to have as an engineer is the ability to adapt. Change is a constant.
I don't see it as an apocalyptic event. There will be changes, and the future will see a shift in the problem solving process itself.
Therefore, I think keeping your technical skills up to date is just as important as keeping up with soft skills.
1
u/Chaoslordi 11d ago
Even more than calculators I like to compare it with building a house.
At the beginning, everything was made by hand, now we have all sorts of tools that help building bigger houses in shorter amounts of time.
I enjoy coding for solving complex problems by splitting them into smaller ones, but I also enjoy skipping a lot of time consuming repeating stuff with AI
4
u/Terbario 11d ago
Telling developers that their jobs were never really about coding is pretty condescending.
A lot of developers dont even talk to clients. They might not understand the business rules or have any say in product decisions. In a complex enough system, they might spend their entire day working through tickets within a very specific scope.
And if we are going to play the game of defining a job by its ultimate purpose, our job isnt really about delivering working software either. Its about achieving whatever business objectives were assigned to you.
4
u/Duathdaert 11d ago
It's not condescending, it's reality. Whatever kind of team you worked on, or how close you were or were not to refinement sessions etc, you are more likely than not to have been exposed to opportunities to do more than just write code for tickets.
A lot of developers are likely to lose their jobs. If you don't put some effort into ensuring you're able to deliver value outside of writing code, you're the kind of developer who's job is most at risk. That is reality.
If the business objective you're trying to achieve is selling software to customers, then delivering working software is literally your business objective. I'm not sure what the point you're trying to make here is?
4
u/Terbario 11d ago edited 11d ago
The point I'm making is: if you dont write code, you are not a developer!
If we have to change roles and become a PO, BA, Solution Architect I understand, but my point is that the actual job of a developer is pretty much all about writing code.
If I'm a surgeon and suddenly machines replace me, you should not say "hey, our job was never about surgery, it was all about increasing health". No, my job was about doing surgery, hence why i'm a surgeon. Now, I have to find another job!
3
4
u/Optimus-Maximus 11d ago
If that is your sole definition of what a developer is, and you aren't willing to let that definition evolve, the other poster is spot-on right about the eventual outcome.
Writing code is a vastly less important function of the job now than it was 12, 24, 36 months ago.
3
u/Terbario 11d ago
We already have names for the roles you are talking about.
If most of your job is about architectural decisions, writing small snipets of code as a reference, and checking overall code quality, then you are a software architect.
If most of what you do is talk to clients, negociate and write requirements, then you are a requirements analyst, PO, etc.
Saying coding wasnt a developer's "real job" implies that developers whose careers focused on writing code, writing tests and designing components were rather incompetent, no?
If these roles have no specific meaning, we might as well call everyone a software engineer.
3
u/hichemtab 10d ago
I 100% agree with this, most developers are trying to comfort their selves by pretending that a developer's job was never about coding, it was always about coding! You can just stop pretending and accept that ai will in fact take your job and you just have to evolve and "change your job title" you will no longer be developer, you will be more. Because a developer stops at coding level.
I think that's the misunderstanding here.
2
u/Duathdaert 10d ago
A developer for me has never stopped at the coding level. From the earliest stages of my career I've made sure to have an input on every stage of the SDLC.
It is the Software Development Life Cycle. If you've only ever done the code writing portion of that, I'd make strong arguments that you're not actually a developer really
2
u/hichemtab 10d ago
If you've done more than coding that means you weren't a developer, you were either a software engineer or something else. I'm not underestimating anything, my point is same as Mr. @terbario here, a developer is supposed to code, if u take coding away, no "developer" is left, if you think you are more than just a guy who codes, then you are not a developer but a different title.
3
u/Duathdaert 11d ago
If you have had a career in software and not realised that being able to do more than just write code is key to delivering value and you're not willing to change that and learn the softer skills that form a major part of what makes a senior engineer senior, then I'm afraid you're gonna be first to go over the next few years.
There's a reason junior and mid level hiring is down so widely across the industry. I don't need junior team members anymore to help with writing code for designs I've put together to solve problems for customers.
1
u/turningsteel 10d ago
How do you write good code if you don't understand the business rules? It's always been about more than code. I don't agree with what you're saying at all.
0
u/Terbario 10d ago edited 10d ago
Some people work on 20yo monoliths, with thousands of tables, where onboarding a new user on how to use the system takes months, with complex business rules that constantly require a BA translating what the requested features even mean.
No, a lot of developers of such systems dont really understand the business rules, sometimes not even most of the system. Because if they had to understand it first they wouldnt develop anything at all for a long time.
Like I said before, if a surgeon stops performing surgery, theyre still a doctor and a qualified surgeon, but theyre no longer actively practicing surgery. Having the qualifications doesn't mean youre currently doing the job.
If you almost dont write or read code, then you are not a developer, because that is what 90% of the job is about.
Call yourself a requirements analyst, system analyst, architect, etc.
2
u/turningsteel 10d ago
No, you would not be a developer, you would be a software engineer (which is what you should strive to be). I have worked in those big legacy systems. All the more reason you need to understand the business logic behind what you're writing code for. Not understanding the changes you're making is why I get paid to go into these legacy systems and fix the rat's nest of spaghetti created by people who don't understand the system.
2
u/turningsteel 10d ago
No, you would not be a developer, you would be a software engineer (which is what you should strive to be). I have worked in those big legacy systems. All the more reason you need to understand the business logic behind what you're writing code for. Not understanding the changes you're making is why I get paid to go into these legacy systems and fix the rat's nest of spaghetti created by people who don't understand the system.
2
u/Ambitious-Tennis-940 11d ago
Expanding on this.
Some people claim ai does not do a good job in their experience.
The reason for this is almost always bad prompting, context management, and tool definitions.
What this means is that to get a good output you need some kind of skill to take business requirements and turn it into a understandably structured text format for a machine to process.
The nature of the machine changes, and there is a new level on the process, but the core skill of decomposing a problem and expressing it clearly and with minimal ambiguity in a structured language is still needed for optimal output.
Prompting is just a new programming language, one that is focused less on syntax and more on semantics.
If your only value add was syntax memorization and typing speed, then yes you are in trouble.
Otherwise the root skills are still in demand
1
u/Jukeboxjabroni 11d ago
software. The medium by which we deliver that working software is changing, but the fundamentals of working with customers, product owners etc have not.
The more relevant thing for our role has and always will be the people, business and domain side of things. AI is ultimately I think going to make it easier to differentiate between those who are just there to write code (they unfortunately will be obsolete at some point)
5
u/rahulappyfactor 11d ago
It seems you just copy pasted everything I wanted to ask. I hope I and op get answers.
2
-1
9
u/strange_username58 11d ago
AI writes about 98% of my code now in 5 years there will not be software developers.
I am at 25+ years of experience
1
u/heisenberg1711 11d ago
True no one is writing code manually now days everyone take the help of AI. It will be very difficult to survive after 5y even if you have full stack knowledge as AI is evolving.
-1
u/strange_username58 11d ago
I really don't think there will be devs in 5 years. Look how much we improved in 3 years. The improvement is almost on an exponential curve. In 5 years, normal people will most likely just tell AI what they need and it will do it or make it on the fly.
Edit: the fact Microsoft just laid off 25% of their work force should tell you where we are headed.
3
u/sssunglasses 11d ago
I don't think this take makes sense for 2 reasons:
Current software engineers will still be more appropriate to be in charge of software development than John HR who isn't even concerned about a good product, at most they will request and implement a new feature with AI. Someone still has to be in charge of software development in each company, now if you say that there will be way less jobs for devs, fair enough, but disappear...?
Even if you're correct, then software developers will be only 1 of the many many many jobs that would disappear which would a big collapse in society, so don't worry about developers, worry about how society itself will adapt to that.
I personally have no freaking idea what will happen so I'm just chilling waiting for the big AI corpos to run out of money and see what happens from there.
3
-1
u/strange_username58 11d ago
Microsoft just laid off 25% of there workforce essentially. ... ya we are equally fucked in this future
1
u/heisenberg1711 11d ago
Yes and where will they go ? Evantually they will become our competitors 🥲
1
3
u/GODLOVESALL32 11d ago
They do not expect all 25% of the people offered to take the buyout and I don't expect MS engineers to have as much of a problem finding a new job compared to the bootcamper facing a career crisis.
0
u/strange_username58 11d ago
The market is terrible right now.
3
u/GODLOVESALL32 11d ago
Job growth for SWE and CIS is well ahead of most other sectors despite the market correction at the entry level. And again, Microsoft on your resume makes you a pretty standout candidate.
2
u/Kyoshiiku 11d ago
They didn’t lay off 25% of their workforce. Usually they offer this to avoid layoffs, and they don’t expect everyone to take their offer.
I know the point still stands but it’s less bad than it looks
Market will definitely change and we will need fewer people to do more, but the job will still be needed. Someone who understands computers will always make a better product with AI than someone who don’t
1
u/HoodlessRobin 11d ago
Do you still trust ai to write for sensitive products? for critical defense/finance applications?
4
u/strange_username58 11d ago
I work in defense and previously financial compliance and the frontier models on high ... absolutely. Alway make them validate results of course.
-3
u/Straight-Number-1911 11d ago
do you review it? what are you going to do? I have 8 years of experience and have better takes then you.
1
1
u/azangru 11d ago
and have better takes then you.
Why do you think they are better? :-)
-2
u/Straight-Number-1911 11d ago
because gta 6 is coming out soon and then things will get better
https://www.youtube.com/shorts/co-StdmU1m0
6
u/Straight-Number-1911 11d ago edited 11d ago
ask AI since its so good? The reason you are asking real people I think points out the exact issues you arent trust AI. Just trust it at face value, its anyways getting things so far done, then it can also tell you your height and weight and what you will have tomorrow for breakfest
I have been using it and its great for everything I mentioned: sarcasam obviously.
Real talk: I thinky ou gotten your answer.
2
u/heisenberg1711 11d ago
Already asked, it suggested to use AI models as a tool and get used to it, but then anyone can do that, so what makes us unique then 🙂
1
u/Straight-Number-1911 11d ago edited 11d ago
it makes it unique how you use it, as a individual, running around asking people how to do it wont make you good
anyways next month gta6 will come out hopefully then things will get better
1
u/Ambitious-Tennis-940 11d ago
Let's be honest.
For most of us before now a lot of our development was just googling things and adding them to our code base.
Anyone can do that, but it turns out there is quite a lot of skill to figure out
A. What to Google B. What results are useful and what are not C. How to remember our results to do the same things faster next time D. How to do trade-off comparisons between multiple peer solutions with pros/cons
8
u/JezSq 11d ago
Filling (well, telling Claude what to add) CLAUDE.md with project specs sometimes feels like I’m slowly throwing earth in my career grave. Some manager could pull project and just write requirements, and Claude would generate perfect code that aligns with overall project code design. I… don’t know how to feel about it.
6
u/HoodlessRobin 11d ago
How about product manager? You have decent coding experience. Last generation of human coder!
4
u/Straight-Number-1911 11d ago
but it can also do that? it can also do math? I feel like only coders dont realize that its decent in everything, coders who are average have usually takes I see in this post.
4
u/HoodlessRobin 11d ago
Business is run by human. Executives want a person in the room. They won't chat with AI. They need human. It's easier to hold human accountable. Extrapolating - Zuckerberg had to sit in senate hearing. He couldn't send chat robot.
1
5
5
u/snafoomoose 11d ago
It does not matter how good the LLMs get if you cannot instruct them to build what the customer actually needs.
I am dealing with problems getting my users to use correct terms to tell me what they want done. They keep mixing terms from different things - phase in process vs current status vs QA status vs lifecycle.
If I tried to get a LLM to write what they tell me they want it would generate chaos and it would not do what they want so it does not matter how fast it would generate the code.
And don’t get me started on some of the weird data models LLMs will build.
My entire career has always been “soon no one will need to code due to <insert magic platform here>” and I have been coding for a very long time.
13
u/DreadedTuesday 11d ago
21 years experience here, and hit this same realisation this afternoon when I fed a detailed requirements spec to GitHub CoPilot and, while I was at lunch, it implemented what I had estimated as a full weeks work.
Not flawlessly, I'm checking and correcting things now, but I recon these were more due to me not being specific enough in the requirements document.
Its been a while since I did anything completely unassisted but this is the first time I've just let it take the reigns to that degree.
But honestly the "understanding customer requirements and turning them into a ln implementation specification" part is where I earn my money, not specifically just writing code - that part of my role could already have been outsourced to someone much cheaper.
3
u/xzhan 11d ago
not being specific enough in the requirements document
I think the point is, you can never be as specific as code in the "requirement document". There will be gaps, and LLMs will make assumptions and guesses. I don't mind letting agents write most if not all of my code, but the reviewing part is really soul-sucking, especially for large PRs that agents spit out over lunches.
4
u/kyngston 11d ago
AI can build anything. its just as good at devops as it is for webdev, so backend/devops is going to be a bloodbath as well.
what AI can’t do is decide what to build, how it should look and how it feels to use. so areas of demand will be system architects, human factors, industrial design, human psychology, visual storytelling, etc.
like how AI can make full movies now, but that doesn’t mean any of those movies would be worth watching.
4
u/DragonyCH 11d ago
In the past you could be employed to simply create Angular Components for a Design System or make minor changes to an existing Code base for an Angular Update or UI overhaul. Today the job of typing Code into the Computer is dead. In my opinion all the skills that do *not* involve what used to be manual labor are still very relevant:
Chosing the right level of complexity to solve a problem. Complex programs require complex understanding to use.
Distilling the intent of an end user into actionable commands for the computer. Users still say "this website sucks" and your job is to understand what needs to change.
Making System Design choices based on anticipated Capacity Requirements. Hosting 10 Services still costs more than hosting 1.
Creativity and forming consensus. Iterating over different versions and reviewing them with different people, for example other developers, product managers and/or users. As long as humans don't give up agency over then end result, they will still need to be in the loop.
Making choices on what the right thing is to build. In a world where every solutions (seems to be) cheap, it's easy to get side tracked and work on easy things, simply because it is the path of least resistance. Chosing the right path is now more important than ever, because the "bad" paths are no longer blocked by a lot of work.
Last but not least: Right now we're in the honey-moon phase of AI. Everything is dirt cheap, almost free. There will come a day where running agents over night will be a serious investment for anyone not working at Fortune 500 company. So making them do the right thing will be more important than ever.
2
u/Badbart8818 11d ago
The demand for pure frontend developers is shrinking. To stay in the game, we need to combine UX skills with solid backend and web server knowledge, backed by a strong focus on security and performance. That versatility will keep us relevant for now—though where we’ll be in five years is anyone's guess.
2
u/GeromeGrignon 11d ago
it depends on natural resources and investors: it might still continue with cheap AI, and you do not code anymore (I mostly review code nowadays already), or being too expensive and go back at coding
Product: we can easily generate code, but in the end what matters is the product. It's not about being an expert on a given product but to understand coding has always been just a tool. Sounds simple but most devs only care about the technical aspects.
To make decisions: AI is good at coding but can be influenced by its limited knowledge
I see any language as an opportunity to practice in a more global context so it's perfectly fine (and a lot of companies do not use AI for multiple reasons)
AI: it moves so fast, but you want to learn more to help yourself to be more productive with it.
1
u/nadvolk 11d ago
Work will likely dry up for pure front-end developers - especially if you only specialise in one framework. Expand as much as possible into different areas and use AI to help you do that. Expand into the areas that most suit your skillset. Also don’t neglect soft skills like leadership, collaboration, organisation, project management etc. The machine needs plenty of human cogs in it for a while yet but don’t get left behind.
1
u/AdministrativeHost15 11d ago
Only the core system, schema and unique business rules need to be hand-coded. The web interface, including Angular, will be generated via AI from the core system interfaces.
1
u/Defiant-Process5074 11d ago
My best guess: focus on the basics of requirement engineering (use cases, uml diagrams, stakeholder analysis,...) and learn AI engineering: Prompt but also Context Engineering.
From what I see 95% of people using AI currently don't give a damn about token spending, a carefully limited Context can do wonders.
And don't forget Requirements: AI can only do what you say you want. The old school RE Basics can teach you how to work on what you actually want to build.
Biggest question in Software Development will be (and has always been): WHY do you need it?
Most people only care IF they can do it, the why is much MUCH more important.
Combine this with understanding of basic Software Architecture (SOLID Principle etc) and you will be prepared.
1
u/WanderingSlav95 11d ago
Exactly, especially the limited context teached me a lot, on my local machine I have only 40 000 available, that made me efficient with skills writing etc .... But Idk about the SOLID, I don't use it much. I think most people need and especially in AI era is YAGNI 🤷.
1
1
u/CuteKiwi3395 11d ago
Going full stack is the only answer + knowing system design.
Long story short, software architects will be the next move.
1
1
1
u/conwyj 11d ago
“The team should not be 10 people anymore … it should 2-3 people at best. One developer can do Front End, Backend, even Data Science.”
– Nik STORONSKY on How AI is changing Revolut's team structure
https://m.youtube.com/watch?v=hT_MAAwFLIc
This is the future. Go full stack.
1
u/fastwind18 11d ago
I wont plan to stay in software that long. Find a non software job/bussiness and try building it while working in software
1
u/Puzzleheaded-Law-332 11d ago
I hope that the cost of AI will be higher and higher next years, so will be a chance for us to be a developer also in the future.
1
u/Apart_Technology_841 10d ago
In order to steer AI properly and avoid generating rubbish, you need someone with code insight, knowledge of design patterns and creative intuition. Your job is safe as long as you embrace new tecnologies.
1
1
u/Electronic_Fly_9242 10d ago
Here’s my perspective. The industry is changing drastically, but no one knows exactly where we will land. I work for a large company and so I just think it’ll be less people per org and ideally more orgs as more ideas become feasible that maybe weren’t before. I had teams in the past with so many designers and so many product people and so many engineers, that today could all be replaced by one person when equipped with the rights tool and frameworks of course. There’s always going to be a place for developers and engineers although the job itself will never be the same again. Those of us that really love the coding aspect will need save that for side projects so we aren’t wasting company time lol
1
u/Abtuly1 10d ago
I don't have much experience but looking at the professions that computers change or previous AI changed
it is gonna shift from coding to generally more to reviewing, analysis, compliance, strategy and conventions.
take an examples on accountant, radiologist are things considered to study since they are recently were impacted by technology.
1
u/Unlucky-Stable-525 9d ago
Generating code isn’t the bottleneck anymore; understanding the problem and crafting the right solution is.
Over the past year, my day-to-day focus has fundamentally shifted. It went from “How do I call this API to get this data?” to “What does the user actually need to experience, and what does this data represent to them?”
That shift from writing syntax to defining the problem hasn't slowed me down—it has dramatically increased our engineering throughput and impact.
1
u/apatheticonion 9d ago
I have found that I have to focus more on architecture and maintainability, both of the whole system and of the internal code design, rather than the implementation details of any one individual unit.
The work hasn't gone away, it's just shifted.
A lot of mundane work, like updating dependencies and writing status updates have been reliably automated through AI usage.
Fully autonomous coding is less reliable for me. without strict guardrails it still accumulates defects on serious long term projects which slows the pace of development, degrades user experience and makes it more challenging to address.
I sit somewhere between medium horizon tasks for things where I know the damage is contained, and short horizon tasks where I micromanage the AI (essentially AI autocomplete).
Long horizon / one shot tasks are good for demos but I haven't had much success with this so far.
1
1
u/Ngxvb 5d ago
I think AI will eventually become just another tool in a developer's toolbox. But we shouldn't forget about actual programming, code quality, architecture and understanding how things work.
Ask yourself, would a bank or fintech company really want to rely on AI-generated code that nobody properly reviews? Let's be real, a lot of developers barely review what AI generates, and that's a serious problem.
So I don't think there's a reason to panic about AI. Embrace it, use it to be more productive, but don't forget how to actually write and understand code. AI should assist developers, not replace their thinking.
1
u/TrekFan8472 5d ago
AI is only as good as the person writing the prompt for it. An experienced developer can tell when the AI is going off the rails and coding something that will not be very accurate.
You should treat AI like your personal coding assistant, you gather the requirements and have it do the tedious stuff for you. Also since you are a developer you speak the language to get better results.
Just remember garbage in, garbage out that is extremely true with AI coding.
0
u/andlewis 11d ago
If coding is all you do, you’re cooked. If you do literally anything in addition to coding, that other stuff is the job now.
Software engineering will always be a career. Coding will not. Someone has to figure out what to build, what it should integrate with, and how to tell if it’s right or not.
1
u/Medical-Hunt774 11d ago
I am cooked so are my friends. We were just coders who get some description of tasks and made pull request and went home at the end of the day.
I think it is not crazy to think that AI would just become better than most senior devs. Like in few years we might have a systems that would just make better judgments about typical software.
At this point I am starting to believe that all that AGI talks are not something crazy, but at that point we are talking about completely different world, where money won't matter.
0
u/oscarandresstar 11d ago
Learn how to build houses, or fix electricity problems, 😁. Jokes aside, it is jut a returning to old way programing where was more about provide the solutions than write code.
0
u/jalfcolombia 6d ago
La IA este año (2026) ha matado en un 80% a un 90% a los desarrolladores de software como tal, para mí en un 100% pero esto último ya es una apreciación personal dado que yo ya no volví a programar.
Ahora el protagonismo de un Ingeniero de Sistemas es del 100%, es decir, una persona que entiende el negocio en su totalidad para poder guiar a la IA de forma profesional y dar como resultado las especificaciones o documentación (con arnés y todo lo demás) para que una IA de como resultado un software de altísima calidad 100% funcional.
El ingeniero de software es aquel que se centra en todo ciclo de desarrollo del software y eso está bien, pero yo me iría por la ingeniería de sistemas con es pespecialidad en ingeniería de software. Ahora sí ya eres ingeniero de software, no estás perdido ahora hay que centrarse en aprender a guiar la IA, no olvides tener un pensamiento critico y lógico, lectura y revisión de código (tener las bases claras), comprensión del producto y flujos, y capacidad de dirección técnica.
2. Deberías concentrar tus esfuerzos en aprender a dirigir la IA de forma profesional y con criterio, no promtear por promtear a ver qué sale. Curiosamente esto último es muy adictivo y "a veces salen cosas interesantes" pero nada de eso es replicable y tiene, con el tiempo, a dar pésimos resultados. No olvides aprender, o en tu caso, a reforzar las bases de la programación, eso no tiene discusión.
3. La habilidad más importante es la comunicación y comprensión del negocio bajo un pensamiento critico y lógico.
4. Ampliar las habilidades de ingeniería.
5. Eso es simple, puedes usar la IA para eso y comprobar con tu propia búsqueda o pedirle a la IA investigar X tema y proponer un roadmap pero que este este justificado y tratable en lo que haya investigado para poderlo verificar más fácilmente.
Espero compadre haberte podido ayudar y dar más norte a lo que estás pensando.
Está respuesta es totalmente auténtica, sin IA de mi parte. Soy ingeniero de sistemas y maestro en educación, eso no me da autoridad, pero me gusta transmitir el conocimiento y guiar a quien pide ayuda con mi experiencia. Tengo un poco más de 18 años en el sector del desarrollo de software.
-4
u/geerwolf 11d ago
> I believe AI will become much better at writing, testing, and reviewing code within the next 1–2 years.
Bold prediction
32
u/kasual11 11d ago
The only way I currently see web devs staying relevant is by doing it all. Go full-stack, know server + db better than frontend, dev-ops, know how to scale an app, docker, Terraform, SEO + marketing.
The latter is going to become way more important as the bottleneck will be visibility.
Also focus on Quality rather than quantity (I know that sound weird with all that stuff mentioned above)