I am once again convinced that "vibe coding" is fucked and haunted.

I'm cognizant of the fact that I've written this exact note before...

How many times will I be drawn by the AI siren song only to remember that it is, indeed, fucked and haunted and that reading, thinking, and writing code just works way better (obviously)?

Or at least its something like: know when to get off the ride. Get your basic scaffold up and then kick that shit to the curb and take the reigns again. It will eventually make your life worse 100% of the time if you don't recognize when the time has come to evict the demon!

Reply to this note

Please Login to reply.

Discussion

I thought I was missing something….

I might be also.

But if the experience I am having is identical to the one everyone else if having, we're about to have a widespread catastrophe of piles-of-shit software dumped on prod in the world.

You can't resist the Bitcoin siren either so thoroughly fucked top to bottom.

I like to prompt it like: here's a function, make it more idiomatic.

sometimes I learn something new.

most of the time, well, not much useful code

The problem with vibe coding is that there is a lack of introspection and modularity to the pieces of code that are being generated. Hope you understand where I'm going with this. 😏

The spice gives with one hand and takes away with the other

So what's interesting here is that programming languages have been tuned for "developer ergonomics" over correctness. What if your AI is writing F*?

"Regular vibe coding errors" / "Incomprehensible vibe coding errors"

Vibe coding is literally gambling

precisely. I've never had a gambling problem but I can imagine exactly what one is like now.

If you can’t reverse engineer and understand the code it spits out, yes

or if there is just way too much of it