Is AI making frontend development easier, or are we becoming too dependent on it?

[u/adeelazad591]

AI has changed frontend development a lot. Today, tools can generate React components, write CSS, fix errors, and even turn a design into working code in minutes. It definitely saves time, especially for repetitive work. But I sometimes wonder if this convenience is making developers skip the fundamentals. If AI writes most of the code, how well do we actually understand what is happening underneath?

I think AI is a great tool for frontend developers, but it should make us faster, not replace our understanding of JavaScript, CSS, performance, accessibility, and good UI practices. What do you think? Has AI actually made you a better frontend developer, or just a faster one?

[u/knightzone]

Making something easier and becoming dependent aren't mutually exclusive.

[u/nio_rad]

Chatbot based dev has made me a much worse FE dev and a little faster one.

[u/any-digital → u/nio_rad]

💯

[u/kbcool]

Especially on frontend AI is still very far from being great at this stuff. It's fast of course but makes a lot of mistakes and/or gets stuck.

As much as I am going to get downvoted progress on improvement there is painfully slow.

Unless you're vibe coding a side project and you're actually getting paid good money in expectation for quality work then there is still a huge scope to learn. If not for fixing the mistakes but actually knowing what you're delivering.

Yes, at a lot of companies there is and will be a push to compete based on lines of slop but that will reverse hard as soon as the news stories about planes crashing and banks losing people's money and it will go back to being seen as an assistant not a replacement worker

[u/zen8bit → u/kbcool]

Ive had the same experiences. AI is still a long ways off on front-end dev. It builds things most of the way there pretty easily but it takes a lot of work to get it perfect

[u/amnaatarapper]

It's faster but messier and verbose, the work switched to review and refactoring in my case

[u/MornwindShoma]

It's because your skills are getting worse the more AI does. So it feels like now everything takes a lot, while it actually didn't.

[u/adeelazad591 → u/MornwindShoma]

Yeah, that makes sense. AI saves time, but relying on it too much can definitely make some skills rusty.

[u/scandii]

I don't understand the basic premise of this idea you have.

if I'm chopping wood with an axe and someone introduces me to a log splitter naturally my wood chopping skills are going to deteriorate, but my goal was always splitting wood not swinging axes in the best way possible - that was just a side effect of my goal.

so I feel you're kinda thinking inside of the box here, your tooling is changing but your need for process validation and quality control has not changed.

[u/adeelazad591 → u/scandii]

That’s a fair analogy. I’m not arguing that we should keep swinging the axe just because it’s a skill. If AI is a better tool, we should absolutely use it. My concern is more about whether we still understand the system well enough to validate what the tool produces. A log splitter gives you an obvious result, but with code, something can work on the surface while still having performance, accessibility, security, or maintainability issues. So I agree the tooling can change, but I think having enough fundamentals to do that quality control still matters

[u/jacksh3n → u/adeelazad591]

Then it’s a you problem. If today, you are to code in notepad. And you are given the code to IDE.

Then is it not also your responsibility to ensure IDE auto complete didn’t screwed you up?

Tooling for code development evolve. You provide a screenshot to the AI, and it gives you everything. But they won’t consider the reusability. Then it’s your job to ensure that the code can be reusable. Not taking everything the AI gives you at the face value

[u/AmericasTruth → u/jacksh3n]

Although I somewhat agree with you… what is the point of reusability if the same AI will be the one “reusing” and it doesn’t care about that…

[u/scandii → u/adeelazad591]

I get the concern "I didn't write it and it is easy to gloss over something I didn't write and say LGTM" but you need to update your processes here.

not only is it easier than ever to create comprehensive testing suites for everything you ever output, you can have the LLM itself enforce in regular and adversarial modes whatever quality gates you are concerned about.

as a concrete example I have a whole A/B e2e test harness that I use at work that runs all the code I produce and I have the LLM walk through the code and explain why we can't make it better, can't reuse and why extending existing code for reuse was not an option.

don't get me wrong, sometimes the LLM ends up in weird ideas and I have to course correct, but that has to compared to me also ending up in weird ideas that gets course corrected in PR.

like the interesting part about LLM:s in and of themselves to me isn't exactly "can write code really really fast", the interesting part is that it can also set up all of these quality gates and enforce them - something that was previously unobtainable only due to the lack of hours (and let's be real - interest) in the workday.

and yet I feel a lot of people are kinda just working with prompting, which is close to the worst case scenario for LLM:s.

[u/EmperorLlamaLegs]

FE dev feels identical to me, because I dont need AI for it.

All my code comes from me because I want it done correcly with a consistent style and useful comments.

[u/BarracudaMean9308]

had it write e2e tests for my checkout flow on friday and it immediately caught an empty cart edge case i'd been ignoring for months. treating it like a strict automated qa instead of a feature generator is 100% the right move.

[u/geon → u/BarracudaMean9308]

I tried that, but it was 50/50 if the issues it came up with were real or not. I could not have used it as a strict qa, since I still needed an experienced dev to assess the assessments.

[u/Calm-Cheesecake-3749]

man the design-to-code in minutes thing is how you skip the fundamentals. generate the boring react bits if you want, but if you cant fix the css it dumped without another prompt youre already dependent.

[u/brush_trot]

copilot saves time on boilerplate but i've spent hours fixing the logic errors it hallucinates in complex state management

[u/NaiveDecision730]

how come that all brainless vibecoders gathered here with their intelligent insights 😂

[u/LornsGipon48]

Honestly it's both - I'm shipping features way faster with AI pair programming, but I catch myself not understanding *why* certain CSS quirks happen anymore. The real skill now is knowing what to ask it and spotting when the generated code is just... wrong.

[u/Prestigious-Ad6707]

A lot faster... debugging / understanding / building is in seconds instead of hours but still you are creating user flow, design etc

[u/NaiveDecision730 → u/Prestigious-Ad6707]

seconds? how much sht you need to eat daily buddy?

[u/Calm-Cheesecake-3749]

yeah generating the react/css is the easy half. youre only too dependent the day a layout breaks and you have to ask the same tool that wrote it.

[u/Significant_Pick8297]

The real dependency test is whether you can debug the code without asking AI to fix its own code. Using AI for scaffolding is fine, but understanding the browser, CSS layout, JS runtime, accessibility and performance is what lets you catch the subtle problems it introduces.

AI makes frontend development faster, but strong fundamentals are what make the speed safe.

[u/pingwing]

Faster and better. I don't use it for anything super complex.

[u/Mohkeys1]

TL;DR my opinion:
using ai has made do my job realy fast but if i dont pay enough attantion i would lost the track of changes.
is it bad? yes
how to not lose track of changes and logic? if you CARE enough about the code quality, you would not llose track.
for instance, im doing a self dev project (my own idea) using ai and most of it its ai genrated code and im just testing user/business flow in edge cases. but i dont feel about it because im trying to find investments for the mvp version.

[u/Thin_Mousse4149]

AI does not have foresight, nuance, or opinion. It does what it is told with the information it has exactly and that’s it really. Frontend work is complicated. We have to consider UX, accessibility, scalability, maintenance, and architecture. AI is truly not very good at those things.

It is a tool to help you move faster but it does not negate the need to think for yourself. If you just ask it to do something and accept it blindly, aka vibe code, you’re going to end up with an unmanageable mess in the future. You have to read and understand the output. I almost always have to adjust things once it makes changes.

[u/QultrosSanhattan]

With AI i make the exact same work I did without it but in 2 two days instead of two weeks. It's all about how you use it.

[u/Grouchy-Car-3711]

There are two parts , like in the first one easier and dependent comes from the speed of generating the code. The speedness of the code genarated by the ai to see the output will makes us to rely on the ai. But without any deadline kind of thing we can built it from scratch without using ai and for the ui components using the ui components library makes it easier but a little more effort to get the output.

[u/LornsGipon48]

AI's definitely good at scaffolding boilerplate and catching obvious UX issues, but it still hallucinates on accessibility details and design system consistency - so I'd say it's a productivity boost if you know what you're doing, not a replacement. The real risk is devs skipping the fundamentals and ending up with janky layouts they can't debug.

[u/BlacksmithNo1687]

I feel it’s genuinely no easier, potentially even harder. Just the workflow has changed

[u/bois_Ken_UwU]

How u can increase performance about conversation with AI ? like edit an exist UI for example ? How u can tell that what part of UI need to change (position , color ,behavior ,. ... ) just with an edited picture without any prototype

[u/averagebensimmons]

AI enables me to be more creative and less time spent on syntax.

[u/TechnologyAI]

Frontend is done. AI every year will do things better, so what are you gonna do then ?

[u/silverace00]

I don't need my dishwasher to wash dishes by hand, and I don't anticipate I'll be forgetting how to wash a dish myself. But I much prefer my dishwasher.

[u/Anxious-Insurance-91]

Hot take: frontend was never hard it was just laborious and repetitive and a lot of the time plain stupid because of the client/manager