To use these tools properly, you need to know how to build the same thing precisely.
The code isn't the most readable because I don't need it to be however if you make me write it from scratch in an interview style setting I'd have trouble doing it. If I read the code I can follow it and it makes sense + it's an easy component to manually test. So.. no, I don't need to know how to precisely build the same thing.
And before you worry that I'm committing code I can't build from scratch.. This is a simple component for a 5 page landing page build with astro where I'm the "main" dev ( wrote like 80% of the code). The web-page won't even need maintainance once it's deployed
The copilots get you going quick at the expense of your learning, which is great for one-offs, but not lasting work quality.
> This is a simple component for a 5 page landing page build with astro
You're already in the over-engineered section there.
https://gist.github.com/lazarcf/c80ae6f9362aaf3aa92e21e3a0dd...
you can see the component (the "image gallery") here : https://pixico.roware.ro/apa-distilata/
I used claude + gemini to whip out a rewrite of a show HN project in less than half an hour to deployment yesterday.
https://news.ycombinator.com/item?id=43071381
But this sort of work is fairly low value and boilerplate-y.
I agree the tools are overhyped for allowing non-developers to write code. It’s not (today) a replacement for a dev agency that takes a set of requirements and runs with it, it’s a replacement for a junior developer who you need to micromanage a bit. But that’s still a boon to productivity!