If AI really sucked at front end I'd have a job right now.
In general, AI is not replacing developers yet. It's a convenient excuse to fire people for other reasons, and to pay lower wages.
Why AI Sucks at Front End
111–120 of 183 posts
Re: Why AI Sucks at Front End
#112If AI really sucked at front end I'd have a job right now.
In general, AI is not replacing developers yet. It's a convenient excuse to fire people for other reasons, and to pay lower wages.
If AI is being used to lower salary burdens, it categorically is partially or wholly replacing developers.
Meanwhile, elsewhere in this discussion, you can read examples of people who have used AI entirely to build their product. Previously they'd have had to hire a developer or become one themselves. This suggests to me it is indeed replacing developers - just not where you are choosing to look.
Re: Why AI Sucks at Front End
#113Imo front end is what it’s best at.
It really is, especially with frameworks. The author post reeks of feeling threatened by AI encroaching on his job, especially with the weird AI digs
Re: Why AI Sucks at Front End
#114Earlier 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.
Why don’t these llm’s just allow you to pick from a set of standardised templates and then allow you to customise it from there in terms of both functionality and design?
What you have got as output is what I also get as output from llm’s - they suck the soul out of everything. Which is fine in the right context but that shouldn’t we as a species strive for in design imo.
Re: Why AI Sucks at Front End
#115Ngl I’m reading this article after having used ai to build a beautiful front end that is pixel perfect. Yes ai can’t see, it only understands numbers. So tell it to use image magick to compare the screenshot to the actual mockup, tell it to get less than 5% difference and don’t use more than 20% blur. Thank me later. I built a whole website in like 2 days with this technique. Everyone seems to have trouble telling ai…
We built the frontend for https://brooked.io and https://app.brooked.io using only prompting so I agree!
Re: Why AI Sucks at Front End
#116Earlier quoted context omitted.
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.
Exactly. And this seems more and more to be an inherent property of AI, which is kind of calming.
If we go one step further… this is why we buy stuff from other people and firms - because they specialise in stuff that we can then allocate resources on stuff that we are better at ourselves.
Henceforth the idea that all these SaaS firms disappear due to firms replicating their products internally is stupid.
Re: Why AI Sucks at Front End
#117Earlier quoted context omitted.
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.
Sorry to be the one to break it to you, but no, you did not design a website just fine with AI. It’s not even just “good”. It’s average. Painfully average, to the point of it being easily mistaken for a scam. Very bad results—as expected from an AI. Nothing to brag about here.
I completely disagree. Making a average website is the goal of most businesses that are selling an actual product. His website looks modern and welcoming and does not distract or take away from the actual content. This exactly what most people should aim for. Some actual constructive criticism is some o the icons in the example log mood look weird on my phone, with really small emojis overlapping the face emoji
Re: Why AI Sucks at Front End
#118Earlier quoted context omitted.
In general, AI is not replacing developers yet. It's a convenient excuse to fire people for other reasons, and to pay lower wages.
If AI is being used to lower salary burdens, it categorically is partially or wholly replacing developers. Meanwhile, elsewhere in this discussion, you can read examples of people who have used AI entirely to build their product. Previously they'd have had to hire a developer or become one themselves. This suggests to me it is indeed replacing developers - just not where you are choosing to look.
No, it's the economy that is shifting and the reason developers are getting fired. This causes wage lowering. AI is the excuse that let's companies corporate-speak around the economy.
Re: Why AI Sucks at Front End
#119Ngl I’m reading this article after having used ai to build a beautiful front end that is pixel perfect. Yes ai can’t see, it only understands numbers. So tell it to use image magick to compare the screenshot to the actual mockup, tell it to get less than 5% difference and don’t use more than 20% blur. Thank me later. I built a whole website in like 2 days with this technique. Everyone seems to have trouble telling ai…
We built the frontend for https://brooked.io and https://app.brooked.io using only prompting so I agree!
> Your data,
> irectl in you
> spreadsheets
Go back to human devs.
Re: Why AI Sucks at Front End
#120Ngl I’m reading this article after having used ai to build a beautiful front end that is pixel perfect. Yes ai can’t see, it only understands numbers. So tell it to use image magick to compare the screenshot to the actual mockup, tell it to get less than 5% difference and don’t use more than 20% blur. Thank me later. I built a whole website in like 2 days with this technique. Everyone seems to have trouble telling ai…
We built the frontend for https://brooked.io and https://app.brooked.io using only prompting so I agree!
You could argue that what you built isn't novel or complex in any way -- (politely) it's basically a clone of hundreds of other SAAS homepages. i.e. its a perfect use-case for AI.
Perhaps the results would be different if you had a specific novel design or interaction in mind, and you wanted the AI to implement that exactly as you wanted.
edit: My point proven by the other examples from this thread. Same format, same "feature cards" etc. https://bridge.ritza.co/ https://poolometer.com/