logoalt Hacker News

Brendinoootoday at 2:29 PM6 repliesview on HN

>e.g. front-end web development

It's kind of funny that you say this, because I am a frontend developer and I tend to see the state of the art as being very good at doing the boring behind-the-scenes plumbing that I don't care about, and not great at doing the kind of bespoke design work that my day job's clients want.

I'm not saying that either of us are definitively right or wrong, and I agree that having a more generalist skillset is probably the best way to succeed in this new era; I'm just pointing out that LLMs don't really own any part of the stack so thoroughly that specialists in that segment will just go away.


Replies

tracerbulletxtoday at 3:18 PM

Yeah everyone thinks its great at the things they don't personally know that much about or appreciate and I think it's kind of embarrassing to proclaim its going to do someone else's speciality great but not theirs and just reveals an underlying ignorance.

show 3 replies
sdellistoday at 5:22 PM

I agree with you. Maybe AI can generate designs that look moderately good and aesthetically pleasing for UIs that solve known problems in a prototypical way.[0] That is useful, especially for simple utilities, internal tools, or hobby projects. However, I have yet to see AI solve new design problems, improve on old problems, and create a unique design style that defines a brand and separates it from competition.

[0] https://research.google/pubs/the-role-of-visual-complexity-a...

tripleeetoday at 3:53 PM

I feel people saying this are imagining front-end web dev is all just HTML tables and centering divs. AI does better with back-end in my experience

JimDabelltoday at 3:58 PM

Most organisations need a high quality design system and to be able to assemble pages from it. Totally bespoke design will start with the designer using an agent. So the way I see it, the everyday stuff will be the first to go, followed by designers taking the rest of it. Front-end developers have their area eroded from the bottom then the top.

As far as frontend vs backend, there’s a greater scope for fuckups when dealing with the backend. Frontend problems tend to be more transient. So the stakes are lower, which means that the accountability of humans has less value.

show 1 reply
avgDevtoday at 3:37 PM

Codex has been great for me for backend wiring, mapping and creating boiler plate code in C#. However, it seems when I go in to fix things its 60% front-end.

Idk, I like AI when it works, but it drives me insane when it keeps making errors. I've had a few errors which I figured out from documentation fairly quickly, provided said docs but the AI would still mess it up somehow.

show 2 replies
evilducktoday at 4:59 PM

I'll second this, with the caveat that I've not yet tried to build anything with Fable.

Every engineer can now produce things in the front end that doesn't look like complete and utter garbage, sure, but everyone is also producing the new-era of Twitter Bootstrap pages. It all has the same touched-by-AI look and it might as well be customer kryptonite from everything I've experienced at my workplace with customer surveys and collaboration. It has raised the floor substantially for internal tools and admin pages though.