@asdasdasdasd714
"but it's not very good at debugging" Yeah, that's 90% of the fucking job.
@matheussantiago6246
Bruh... 100x faster? What the heck are you building? To-do lists?
@aihype-2025
Real engineers: 2 hours coding, 6 hours debugging. Vibe engineers: 10 minutes coding, 3 days debugging 😂
@ThomasHorrobin
When people talk about vibe coding I feel like I'm in a cult. Yeah sure the vibes might be good but my database connection is still timing out.
@shoulderstack5527
When the 'sales team' introduce the product by saying 'It's not a fad', and 'If you don't use it you will be left behind', then you know they got nothing real to say.
@julianklumpers
I can tell you that people who say “vibe coding” is the future… they benefit from it!
@arpitdubey5938
Vibe coding is the future unless you need to do "Vibe debugging"
@securityinteractive
never ask a barber if you need a haircut
@Chad-i7b
I'd like to see a build in public vibe coding session where someone is building something worthwhile using this approach. Show me this works well for product development
@Aaron-vi1tj
Some of these quotes are fucking bonkers. "...as codegen tools make everyone a 10x engineer" - If you are being made a 10x engineer by the current state of LLMs, I daresay you were barely an engineer in the first place. Maybe in further iterations this will happen. "...Since I can write code 3x faster, it's easy for me to scrap and rewrite if I need to" - Why not, like, give a few minutes of decent thought "...100x" speed up - are you actually serious? You are doing some now in 1 day that 6 months ago would have taken you 100? I'm calling absolute bullshit on that one Jackson
@user-mx1oc4rr5f
The misconception is that people who don’t know anything are good at this . 10x on zero is still zero
@Dman-g3w
AI enables non-coders to try something, fail, return to AI with an error or description of what is wrong, and keep trying. This cycle is WAY faster than if they used a search engine and had to understand the programming concepts to even be able to search on the problem. Feels like a game changer as it lowers the bar and will enable more coders. Amusing because I always thought the "ultimate program" was one that replaces the programmer and we are certainly closer to that than ever before.
@marthinus.x
The iPad kids of the programming world.
@isurujn
Startups' codebases are notoriously messy due to the initial fast-paced growth stage. Now imagine you throw AI slop code into that mix! I wouldn’t wanna be anywhere near a project like that.
@hellofahmid
Vibe coding debugging trick: In Cursor, have your terminals selected that is running the app. Then turn on YOLO mode. Then grab a beer, light up that joint, get on the surfboard, and let the wind dictate your future. Turn on live reloading while you're at it.
@CloudGrazingZebra
Yikes, would love to see how they handle vibe architecture, code interviews and security😂
@fluttera
I am a developer. I work with both cursor and windsurf. I switched to cursor because it is better for large production apps. You want to control the context window to exactly decide which content to give the AI. Sonnet 3.7 is good for execution. More expensive models with reasoning are better to plan with me the feature like an architect. Execution in agentic mode especially for repetitive tasks sonnet is great. Also in real life the ai tools are not 3x or 10x the developer it rather improves my speed by approx 20%. Important is to learn prompting and in large projects you need to define rule files for cursor to follow to make sure it works with the packages and structures in line with project guidelines. Mvps are build fast with Cursor. Adding features to real production apps do not help much maximum 30% developer speed improvements and sometimes if you trust the ai tools much it causes more bad than good. Just my two cents as developer who uses cursor daily for work
@yuximchuk99
oh no guys, it is "Ping-pong coding" - the frustrating cycle of repeatedly sending AI-generated code back for fixes until you finally give up and write it yourself from scratch
@sbonth
Debugging left the chat
@chapterme