If you are really good at something, you'll find AI sucks at everything.
Why AI Sucks at Front End
101–110 of 183 posts
Re: Why AI Sucks at Front End
#102Earlier quoted context omitted.
[flagged]
I mean, there's a fundamental missing understanding of how to build a coherent design, then there's also the problem of just poor implementation such as the animations. The Lua site has some problems as well, like an uncessary border, text size and spacing, even when it's this minimal. You can get much faster and better results from using or taking inspiration from something like Astro Starlight or UnoCSS Astro Starl…
Re: Why AI Sucks at Front End
#103Earlier quoted context omitted.
I started with a boilerplate but AI has been huge at letting me get what I want in terms of frontend building when I was never talented at design or css. I built https://bridge.ritza.co (demo@example.com username and password if you don't want to sign up) as a trello/linear replacement without looking at a single line of code and it's both good enough for me and doesn't have the obvious AI frontend 'look' as it was c…
> doesn't have the obvious AI frontend 'look' as it was copying from the starter. Check out the other reply and scroll down a bit…
Re: Why AI Sucks at Front End
#104Earlier quoted context omitted.
> If you are really good at something, you'll find AI sucks at everything. Nah, just at that something :-)
I think the point is, there's always someone good at what you are evaluating. Anyone with expertise in the domain will recognize how back it sucks in any given domain. Don't get me wrong, AI can definitely be used as a tool by someone who knows what they're doing to avoid boilerplate. But anyone using it in a domain they aren't already an expert in will unknowingly accept AI f ups.
Re: Why AI Sucks at Front End
#105Re: Why AI Sucks at Front End
#106Earlier quoted context omitted.
Please share what you created! I think people have very different views for what is a good interface, or a tolerable one. I think as a front-end developer and designer I notice a lot of problems most people don't care about.
https://poolometer.com I built this frontend with Sonnet 4.5 last Fall and I’m about to “launch” it I used only prompts, but those prompts included ChatGPT’s research on Memphis design ;) Using codex for front end design is like asking the valedictorian mega nerd to paint your portrait. Gemini and Claude are both artists.
Re: Why AI Sucks at Front End
#107I'm a backend dev and I'm always hearing about how LLMs are dramatically better at frontend because of much more available training data etc. Maybe my perspective isn't as skewed as I've been led to believe and LLMs need close supervision and rework of their output there too.
I would trust an LLM with backend much more than front-end. Especially if we're talking monolithic and good type system. Ideally compiled. When I say trust I mean it's not going to break the user-facing API contract, probably, even if internally it's a mess. If you let it do front-end blind, it will almost certainly embarrass you if you care at all about user experience.
Re: Why AI Sucks at Front End
#108If you are really good at something, you'll find AI sucks at everything.
Corollary: if you are bad at everything, you’ll find AI to be the greatest invention in the history of mankind
The people I work with who find "AI" makes every part of their life easier were just bad at everything to begin with. The people who find "AI" making specific tasks easier have specialized skills and were previously relying on less specialized people for some support.
Re: Why AI Sucks at Front End
#109If AI really sucked at front end I'd have a job right now.
Re: Why AI Sucks at Front End
#110If AI really sucked at front end I'd have a job right now.