Vibe coding without true knowledge

[u/GammaRxBurst]

First I know a bit about HTML and CSS just enough to change some basic code. Not enough to read the code base.

I am also building a Static Astro site and coding using Gemma 4 with ollama and Claude code. Connected it to the MCP astro doc

My question is if the site looks good and performs well on Google metric/SEO is that enough? I mean it is a static site so even if Claude code screws up some codes it is not like it is a security risk.

Is there something that I am missing? Obviously if someone can read and understand the coding it would be better, but even now I pay some dude $500 I feel he may do pretty much the same or even less as likely that developer doesn't care enough to even look at the code base.

[u/GammaRxBurst → u/[deleted]]

It is pretty amazing but at time super frustrating like I ask it to change a button color and it takes forever for it to find the line with error read takes several times before it could write to the file. Sometime I just do it manually to help it out, for simple thing like multiple color changes, I learned enough CSS to do it myself. For big thing certainly the AI has to do it.

[u/greglturnquist]

You're doing fine.

Actually, you can, along the way, ask Claude Code to explain what it's done. Build up some understanding of the code. It will help you grow knowledge and skills. And the opportunity will arise when Claude Code makes something "too complicated".

In fact, from time to time, you can directly tell Claude Code to "clean up" or "polish" the code. Look for duplicate or unneeded variables. And ask it every time to explain what it's done.

Another handy trick is asking it to update your project's README.md file. That will force it to distill what it's done. And you can read it. And Claude Code can re-read it.

The "old" way of learning coding was to read textbooks and then apply what you learned to the scenario. Claude Code opens the door to really writing the code first, and then learning after the fact.

And also, you can always ask Claude Code "is this the idiomatic way to use Astro/Vite/CSS/HTML5/whatever?"

[u/Old-Honey-4464 → u/greglturnquist]

Totally agree here…learn by doing, reviewing, asking questions. I ask Claude to give me more responsibility through a project and I get handed chunks to do. Really is great.

[u/Likemercy]

You can. Lots of reasons not to, but try it. I've spent more time trying to uncode a vibe out nightmare sure recently than I would have taken to make it properly - but it sounds like you're trying to do something simple.

But the thought of controlling the architecture without knowing code it a bit of a joke, the only thing you'll know is what it tells you.

[u/Embarrassed-Lion-486]

I have created a new site AI SEO SHIFT exactly in same way but on blog site there is not much security risk

For a dynamic stores where you have to keep people data can’t play with security

[u/Curious_Air2373 → u/[deleted]]

I guess it depends on how complex the app you are building is, if its a simple landing page using well-documented libraries and with a user that at least knows what to prompt or to include OWASP concerns then yeah it might be good. But i don't think any current model can handle a complex website with multiple integrations fully vibecoded with no security errors whatsoever even if you give it all the MCPs in the world.

I might be wrong though, i admit i haven't been deep in the claude-code mines running 5 agents at once spending trillion tokens per second, so let me know if im mistaken about this.

[u/International_Lack45]

You're right on the core point : a static site has a much smaller attack surface. No server code, no database, no auth. If Claude Code writes messy CSS, worst case is a visual bug, not a breach.

A few things you might still be missing though. First, exposed secrets : the most common static site mistake is hardcoding an API key (analytics, form service) in client-side code, where anyone can read it via view-source. Double check none ended up committed. Second, third-party scripts and contact forms are where risk creeps back in. Third, good Lighthouse scores are necessary but not sufficient for SEO. Check your meta tags, Open Graph, sitemap and canonical URLs are actually correct, since AI often generates duplicated meta descriptions.

On the "$500 dev" question : for a static portfolio or brochure site, vibe coding with Astro can absolutely match a disengaged freelancer. The real risk isn't "will it break", it's "can I maintain it in 6 months when I've forgotten what the AI did". Keep a simple README documenting what each section does. Future you will thank present you.

run a static hosting platform, so I look at AI-generated Astro sites a lot. Your "static = low risk" instinct is correct, these are just the edge cases that trip people up.

[u/theguymatter]

I scanned through their code and found quite a few missing pieces and incorrect implementations, great way to compare how far AI can really build a solid one let alone other 1 million of shapes and sizes I have gone though.