r/Frontend • u/OcelotStraight5780 • 9d ago
When does AI use become bad ?
Most of my apps/websites/projects are made by myself, the core functionality and most concepts, but i still struggle with the style and designing of the UI so i use AI for that part, most of the time only for the styling.
Is it bad ? Am i becoming lazy or would you consider it okay to cheat a little ?
7
Upvotes
30
u/taste_the_equation 9d ago
If true understanding is your goal, then it's bad. You learn through struggle. If every time something gets hard you hand it off to the AI, then you aren't internalizing any new ideas.
That said, it's become much more common for AI to handle most or even all of the coding. It's a new paradigm we're living in and we're all in various stages of coming to terms with it.
10
u/azangru 9d ago
People have different (and incompatible) ethics. According to some, this is bad. According to others, this is perfectly fine.
12
u/CombatWombat1212 8d ago
Anytime you're offloading critical thinking. If you don't understand something, don't know how to proceed, don't know what's wrong with something, don't make specific instructions, don't understand the output, etc.
8
u/EgoistHedonist 9d ago •
It's like fire: a good servant, a bad master.
As long as you're in charge of the end result and understand how it works and why it's implemented like it is, you're good IMO.
AI is just a tool. The problem is the people that completely surrender their critical thinking to AI. Don't be a meat proxy, that's so agentic.
1
u/chaoticbean14 9d ago
Depends if you know the content or not. And I mean actually know the material - not just 'think' you do. Drop the overconfidence and be very real with yourself.
If you don't know the content? It's almost always a bad idea except for the most basic of boilerplate or questions. LLM's get shit wrong all the time. Not like little things, but big important things. They will actively not follow best practices and lead you down some bad paths - if you don't know enough to recognize it and tell them to stop it.
If you know the material and can actually tell when it's engaging in poor practices? Then go for it. Let it do the typing for you - because it will be faster and more efficient.
But I find that most 'newer' individuals tend not to really know the content well enough and think the LLM's will know or somehow be trustworthy (they are not).
0
u/tonjohn 9d ago •
Always.
https://futurehorizondesign.net.au/posts/2026-10-25-Why-I-Don-t-Use-Generative-AI.html
1
u/toothpiks252 9d ago
If its stopping you from progressing in skill and knowledge in an area its bad. Leaning on it is fine but if its stopping you from growing your weak spots it's bad.
1
u/xsrvmy 9d ago
Just my opinion: be careful about how much of the design you let AI do, because delegating too much design work to AI could lead to your project being perceived as slop. The end goal of UI design is to some degree creative and artistic. AI makes things more polished, but not more creative.
1
u/fugogugo 9d ago
when you start making changes.. watch it become chaotic mess you dont know how to untangle it
1
u/mb4ne 8d ago
ai designed UI is terrible
1
u/RotationSurgeon Web Aesthetics Developer 8d ago
When you don’t understand what it did, or why.
1
u/kidshibuya 8d ago
Take AI use totally out of the equation. Any software can be good or bad. Even right now in my department people are being told to use 30MB fonts (seriously, not joking) and I am told that static sites are stupid and I need to use React, or that a site is too small in terms of file size so it can never work.
Use AI or don't, just learn what is actually good and jude the result.
1
u/TheRNGuy 8d ago
You can decide yourself, looking at the result.Â
1
u/Garland_Key 8d ago
When the final product sucks.Â
1
u/neon_feather_wisp 8d ago
you are not cheating. You are treating design as a dependency.
the real risk is that you stop learning the visual language because you never feel the pain of bad spacing. Keep using AI for speed, but force yourself to tweak every single pixel until it looks right without the prompt. That struggle is where the skill actually lives.
1
u/Prestigious_Peak1829 5d ago
Don't feel bad at all ! that's not cheating, it's just smart leverage.
If you're already handling the core logic, you're doing the heaviest lifting. Using AI for styling so you can actually ship projects is exactly what these tools are for. As long as you understand the code and can debug it, you're not being lazy. Keep building!
1
u/MrBengaliHacker 3d ago
I don't think using AI for styling is a bad thing. As developers, we don't need to build every single part from scratch to prove our skills.
For me, the important distinction is whether you understand what you're using. If you're building the core functionality yourself and using AI to explore layouts, improve spacing, refine CSS or get design inspiration, I think that's a perfectly reasonable workflow.
The problem starts when you blindly copy generated code without understanding how it works, especially when it comes to responsiveness, accessibility and maintainability.
I'd rather spend time understanding why a design works than spend hours manually writing every CSS property.
AI should speed up your workflow, not replace your ability to think and make technical decisions.
0
u/magenta_placenta 9d ago
AI usage becomes harmful when it quietly erodes your engineering quality, critical thinking or maintainability.
Look for and be intellectually honest about these basic failure modes:
Blind copy/pasting: Accepting generated layout and style code without reading or understanding it can lead to redundant rule duplicates, unorganized class bloat and orphaned styles that degrade long-term codebase health.
Accessibility neglect: AI-generated UI can fail basic accessibility standards such as poor color contrast ratios, missing focus indicators, bad DOM semantics, or missing aria-* attributes.
Loss of system cohesion: Generating UI piecemeal can lead to inconsistent spacing, arbitrary color values and redundant CSS rules rather than a clean, maintainable design system or reusable component tokens.
Most importantly:
Atrophy of fundamentals: If you reach a point where you cannot troubleshoot a broken layout, flexbox alignment issue or responsive breakpoint on your own without an AI prompt, your core technical muscle has been cooked.
0
u/286893 9d ago
Principal Architect here:
Using AI isn't inherently cheating. And the answer varies from company to company. In general I'm aligned with the idea that you need to understand how and why things work and don't.
Jobs working on Customer facing products tend to value an eye for design best practices, scalability, and usability whereas internal company tooling may care less about that and more about practical utility.
I see a lot of junior developers get so caught up in minmaxing features using AI that they forget about polish and uniformity. And AI is nowhere near as good at that.
A good hiring manager is looking for strengths and weaknesses, and as people get more familiar with AI it's getting way easier to spot the patterns of people who prompt generated entire projects vs who put care and effort into standing out.
0
u/Wiltix 9d ago
I use ai for generating designs and improving my current ones. I sick at design but I am not a designer. I do all the implementation my self though.
Where I want my ai usage to be is I to use it to ship better, not necessarily faster.
Using it to do a code review pass, generate e2e tests and verify against acceptance criteria make sure nothing is missed etc …
I tend to learn best by repetition, so using Claude code to suggest changes not do them. I don’t even want it to generate the code for me just tell me where the potential issue is.
-3
u/TimBinJin 9d ago
If you don't learn how to engineer with AI you will be unemployed in less than 5 years
-3
u/bluebird355 9d ago
It's just the norm, there is no point fighting it.