It’s useful for things I’d otherwise Google. It makes a great ORM, when you know exactly what you want to do with a lot of mundane code. And it’s so much better than adding a framework for an ORM.
You know, you can just look at it. It’s pretty simple, easy to look at, pretty repetitive code where it’s generally pretty easy to spot if something’s wrong.
Vibe coding is more hitting “accept all” and not looking at it at all (or not knowing how to look at it).
It’s useful for things I’d otherwise Google. It makes a great ORM, when you know exactly what you want to do with a lot of mundane code. And it’s so much better than adding a framework for an ORM.
I don’t like ORMs, but I’d rather use a battle tested ORM than some vibe coded data layer.
You know, you can just look at it. It’s pretty simple, easy to look at, pretty repetitive code where it’s generally pretty easy to spot if something’s wrong.
Vibe coding is more hitting “accept all” and not looking at it at all (or not knowing how to look at it).
Or, I could just write it myself, instead of ending up like these guys https://sketch.dev/blog/our-first-outage-from-llm-written-code