I would prefer to title it “Gravity’s Rainbow Of Vibe Coding” as this is hardly a cycle, more like a denial committed with force that will eventually give out and cause regression into a shattering of identity.
And to think all those times I cursed CORS under my breath. Doing God’s work.
I remember there being a CORS problem in a team project.
Perhaps I should ask the webdev at the time whether they had made that thing with AI or they really just made the whole thing themselves and somehow overlooked CORS.CORS has always been a problem. I keep having to remind the backend team to send proper headers. They say it works in curl so why not in the browser. It’s not very intuitive.
Have you noticed how every LinkedIn bro is talking about their vibe coding workflows, but no one is showing what they’ve made with vibe coding?
Sometimes a post on LinkedIn will have a link to a “finished” product. But 99% of the time there is a comment that says, “Hey, your API endpoints aren’t protected.”
Like all the other content grifters and their tutorials or get rich quick scams.
Just a little more compute bro, we just need a little more context window. trust me bro Claude 5 will be AGI
They said it can write code. They never said it can fix code or debug issues.
That’s like saying you can drive, bit can’t navigate or park.
