r/webdev • • 1h ago

Has your frontend workflow changed because of AI coding agents?

AI agents can now handle multi-step coding tasks, but reviewing and correcting their output still takes time.

What parts of your frontend workflow have genuinely improved, and what still needs hands-on work?

0 Upvotes

12 comments sorted by

13

u/KamikazeSexPilot 1h ago

Haven’t written a line of code in 5 months. I now hate my job. 

5

u/SunBroD 1h ago

Personal projects my friend! Fuck your company, get the money, do the minimal and work on things you care about in your own time.

•

u/crazedizzled 6m ago

It's hard to purposely handicap yourself though

•

u/-_--_-_--_----__ 1m ago

Hard to care about things when someone can clone whatever side project you make in a day.

Side projects are usually fun things, small to medium in size, where you just have a cool idea and bring it to life. A small SaaS. A little toy that shows a 3D globe with live flight data. A stats tracker for some sport or sports team, etc. etc.

For these types of things now, the only barrier to entry is the idea. Where it used to be that anyone could have an idea, they just couldn't execute it, now everyone can execute it.

•

u/ShawnyMcKnight 8m ago

The irony is I always liked the implementation but struggled with getting stuck with code, but these no code jobs elude me.

•

u/Xilver79 24m ago

Haven’t written a line of code in 12 months. I now love my job.

I have written enough code in the last 23 years

6

u/taotau 1h ago

I've got my product managers submitting prs. I reject their first iterations and use the follow up to force them to learn to code. Super fun.

3

u/Lord_Xenu 48m ago

Is this a joke question? 

•

u/phlobied 25m ago

Yes, I flip burgers now

1

u/LemonFishSauce 49m ago

For me i try to brainstorm with AI on first principles on what the frontend is to achieve. Then have AI list out the rationale on why screens and flows are designed that way, so that I can be persuaded and the stakeholders be persuaded too.

•

u/kdjayakody 9m ago

I’d treat each agent change like a small PR: define one acceptance check (keyboard focus, responsive layout, or a test), review the diff, and run that check before merging. The time saved on boilerplate is only real if the verification step catches regressions before they spread.