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.
this post was submitted on 12 Jan 2026
257 points (99.2% liked)
Programmer Humor
28398 readers
1031 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
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.
When I was learning, CORS was a pain in my ass. It’s not taught well, and often glossed over.
So I guess AI and hence, vibe coders are having the same problems as normal programmers.
Cors was usually not part of any tutorials. To new people it was more of an afterthought, just set policy to get you page to work.
Hehe yeah, security in general has been an afterthought in the computing space.
And it makes sense. You first make something possible, then restrict it for whatever cases you don't want it happening. The latter is supposed to be easier.
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."
99% of the time it’s just a basic todo list
The 1 percent being AudioNoise?
It's literally a single small python file.
But not a ToDo list right?
Unless you consider computer instructions as ToDo items, in which case, all executables would be ToDo lists.
In a recent post on HackerNews, someone said that there is no burden of proof that it works. The purest form of "trust me bro."
I prefer the other posts of vibe coders complaining about data loss because their llm didn't tell them how to prevent xss or SQL injection.
Or because their agent wiped all the data on production
Yea, that was a good story.
Like all the other content grifters and their tutorials or get rich quick scams.
stealth startup bro, my crud app is gonna change the world
I'd be delighted to do some QA consulting for you! I'll throw in some pentesting as well. Hell, I'd give you a few hours' free trial so ~~I get to piss you off legally~~ you can get an outside confirmation fueled by a shared passion to see you reach the acclaim you deserve.
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.
I think the largest failure is bad architecture, or that is the inability to understand architecture at all. After your vibe coded project gets larger than a prototype and you "zoom out" to try and grasp what is going on, is when you see how bad it is.
Ironically cars can park and navigate, but not drive.
I have met people that dont know how to navigate with Google maps and its painful to be a passenger with them.
Driving with a nav system is a part of the driver license test here.
Where is "here"? Because it doesnt seen to be a thing in the US
Netherlands, Belgium and UK.
That guy picked me up as a rideshare driver once. He was late.
Did you vibegraph those lines?
Looks ethically sourced artisanal lines to me
they're "rustic".
no, not generated with Rust.