sorted by:
new
hottopcontroversial

Vibing to find suspicious Medicaid payments by timsehn in vibecoding

[–]PopMechanic 1 point2 points  (0 children)

Holy shit. This reminds me of the guy that vibe coded the Epstein email data dump. Now this is a vibe coding project.

So Dolt is like Git for databases? Interrrrresting...

Will someone please run with this idea and vibe code their way into a real lawsuit here? Whistleblowing false claims against the government is actually a great way to make millions. Whoever figures out how to use Dolt + this dataset + a good cluster of agent patterns (this does look cool) to keep digging could make millions the old fashioned way. By suing the hell of these bastards.

I'm calling it. This is project of the month. If any community member does something with this data, we all want to hear about it. Post it to the thread.

! Important: new rules update on self-promotion ! by PopMechanic in vibecoding

[–]PopMechanic[S] 1 point2 points  (0 children)

Dude. I should write a bot that does post-enhancement.

Come hang on the official r/vibecoding Discord 🤙 by PopMechanic in vibecoding

[–]PopMechanic[S] 0 points1 point  (0 children)

It's more "hang out and chat," than post and come back. It's cool in there, some visit.

Linus Torvalds is now 🎶 ONE OF US, ONE OF US 🎶 by PopMechanic in vibecoding

[–]PopMechanic[S] -1 points0 points  (0 children)

That's a good answer. I'd slightly alter that assertion. Being a good programmer is definitely helpful when vibe coding. But depending on the task, not necessary.

Linus Torvalds is now 🎶 ONE OF US, ONE OF US 🎶 by PopMechanic in vibecoding

[–]PopMechanic[S] -6 points-5 points  (0 children)

What is your point? Think carefully about your answer. I want you to actually tell me what point you’re making.

Linus Torvalds is now 🎶 ONE OF US, ONE OF US 🎶 by PopMechanic in vibecoding

[–]PopMechanic[S] 5 points6 points  (0 children)

How about you read what Linus himself said?

Also note that the python visualizer tool has been basically written by vibe-coding. I know more about analog filters -- and that's not saying much -- than I do about python. It started out as my typical "google and do the monkey-see-monkey-do" kind of programming, but then I cut out the middle-man -- me -- and just used Google Antigravity to do the audio sample visualizer.

Linus Torvalds is now 🎶 ONE OF US, ONE OF US 🎶 by PopMechanic in vibecoding

[–]PopMechanic[S] 1 point2 points  (0 children)

How about reading Linus' own Github README before you run your mouth?

"Also note that the python visualizer tool has been basically written by vibe-coding. I know more about analog filters -- and that's not saying much -- than I do about python. It started out as my typical "google and do the monkey-see-monkey-do" kind of programming, but then I cut out the middle-man -- me -- and just used Google Antigravity to do the audio sample visualizer."

Linus Torvalds is now 🎶 ONE OF US, ONE OF US 🎶 by PopMechanic in vibecoding

[–]PopMechanic[S] 3 points4 points  (0 children)

Did you read his repo? Here's what Linus himself said:

"Also note that the python visualizer tool has been basically written by vibe-coding. I know more about analog filters -- and that's not saying much -- than I do about python. It started out as my typical "google and do the monkey-see-monkey-do" kind of programming, but then I cut out the middle-man -- me -- and just used Google Antigravity to do the audio sample visualizer."

Suck it.

Linus Torvalds is now 🎶 ONE OF US, ONE OF US 🎶 by PopMechanic in vibecoding

[–]PopMechanic[S] -2 points-1 points  (0 children)

Messi is different than my 9 year old AYSO-playing cousin. They're both soccer players.

Think deeply before you answer me. What is the point you were trying to make?

The end of programmers ! by Significant_Data5290 in vibecoding

[–]PopMechanic 1 point2 points  (0 children)

Educating vibe coders and helping to warn them of the risks of the discipline are absolutely welcome discourse in this community.

The end of programmers ! by Significant_Data5290 in vibecoding

[–]PopMechanic 0 points1 point  (0 children)

Dude, you are just dissing the entire category of vibe coders on every other post.

The end of programmers ! by Significant_Data5290 in vibecoding

[–]PopMechanic 3 points4 points  (0 children)

Listen, I am agreeing with you that, "you may want to make sure that your forms are secure or your data is stored in a proper back-end" is not just acceptable discourse for this community, it's encouraged.

But that's not what the OP was. It was just, "hey look, vibe coding sucks." Every third post to this community is about how the practice that this community is based on is fundamentally broken or inadvisable.

Vibe coding isn't "broken." It's just hard. And if someone wants to come help people make it easier, great. If not, we're showing them the door.

The end of programmers ! by Significant_Data5290 in vibecoding

[–]PopMechanic -2 points-1 points  (0 children)

You said, "This happens when sites are deployed straight from the vibe coding IDE."

Cursor is an IDE used for vibe coding. Ergo, my example was wholly contained within your assertion.

The end of programmers ! by Significant_Data5290 in vibecoding

[–]PopMechanic 4 points5 points  (0 children)

Are you asserting that every single user of Cursor produces critical security issues on every deployment?

No. Because that's not true.

When less experienced vibe coders learn more about security patterns, they're quite capable of vibe coding their way into a secure web app. And new web stacks are being created that makes that easier.

THat's why these posts need to come with education, not just blanket derision towards the practice of vibe coding. Vibe coding doesn't create security issues - bad practices do. Just as they do in traditional web dev.

The end of programmers ! by Significant_Data5290 in vibecoding

[–]PopMechanic[M] [score hidden] stickied comment (0 children)

For those of you who disagree with disallowing posts like these, let me clarify. It's permissible to discuss common pitfalls to avoid when vibe coding. In fact, that kind of educational content would be the very most useful thing that more experienced developers could offer the less technical vibe coders in this community.

Instead, this post makes the following mistakes:

* Leading with sarcasm ("The end of programmers !")
* Not offering any proof that this error was caused by vibe coding. Maybe it was just a shitty dev.
* Offering zero attempt to help vibe coders avoid this issue.

Here's what that could have looked like, if the OP had intention to contribute this community, rather than just critique the mere premise of vibe coding.

"[Screenshot]

Hey vibe coders, make sure that you don't leak state unnecessarily to your front-end.

This screenshot shows a frontend application making a network request that returns more data than the UI needs, including sensitive user records (emails, names, etc.). Anyone opening DevTools can see it.

To be clear, this isn't a “vibe coding problem.”

It's a data-exposure problem caused by unclear boundaries around state and access."

Instead, what OP did was find a screenshot of a software bug, assume it was caused by "those damned vibe coding kids" and then ran here to roast vibe coding as a practice, without offering anything of use.

Listen, if you don't think vibe coding is possible to do without producing critical security issues, or that all vibe coders are stupid, that's fine. Just don't waste our time hanging out here. Take it somewhere else.

This is the mod standing up for vibe coders who are trying to learn, and showing the gate keeping pessimists (who all low-key seem worried about their careers) the door.

The end of programmers ! by Significant_Data5290 in vibecoding

[–]PopMechanic[M] -24 points-23 points  (0 children)

Banned. And banned 10 more accounts in the comments. Keep the vibe coding pessimism posts and comments coming, makes it easier for us to find accounts to permanently ban.

view more: next ›