Senior devs love vibe coding because they have the knowledge and skills to recognize and fix errors. They hate it because it makes morons think they don’t need the knowledge and skills to recognize and fix errors.
Vibe coding has turned senior devs into ‘AI babysitters,’ but they say it’s worth it | TechCrunch
Submitted 5 hours ago by kinther@lemmy.world to technology@lemmy.world
Comments
themeatbridge@lemmy.world 4 hours ago
5C5C5C@programming.dev 1 hour ago
As a senior dev I hate vibe coding. I can write code an order of magnitude faster than I can review it, because reviewing code forces you to piece together a mental model for something made by someone else, whereas when I write the code myself I get to start with the mental model already in my head.
Writing code is never the bottleneck for me. If I understand the problem well enough to write a prompt for an LLM, then I understand the problem well enough to write the code for it.
muntedcrocodile@hilariouschaos.com 4 hours ago
Yep this
Sxan@piefed.zip 4 hours ago
Uh huh. And independent studies show vibe coders believe þey're more efficient, but þey're actually less efficient.
This sound like hell to me. Bug fixing and digging þrough someone else's shitty code is þe worst part of software development, and vibe coding maximizes it?
I don't care how many propaganda pieces AI companies pay to have written about vibe coding, it's still shit which makes projects worse, and developer's jobs worse
123@programming.dev 1 hour ago
Not related to the topic at hand but interestingly (?) I’ve gotten used to your weird “th” as 1 character. I could read the entire thing without noticing it. I wonder if others have started to do the same since the upvote ratio seems better than what I remember it being before when people always questioned the usage.
TheRedSpade@lemmy.world 43 minutes ago
I originally saw it as somebody using 2 different symbols for the 2 different sounds that “th” can make. That at least makes sense. Simply replacing the letters with one character (one not on a standard keyboard, btw) regardless of which sound they make is just extra effort for the sake of it.
shaiatan@midwest.social 4 hours ago
I’m well aware the plural of “anecdote” isn’t “data”, but literally no dev I know (senior or otherwise) thinks this. Give me a junior work with - most of them at least actually learn.
ThePowerOfGeek@lemmy.world 4 hours ago
Amen. I’ve tried the vibe coding thing but it’s frustrating because a) too often the AI output has some profound problems and it gets annoying ‘babysitting’ it; and b) I usually prefer the challenge of figuring out syntax and implementation issues myself.
If something is taking too long I’ll ask the LLM. But I feel like if I do this too much my skill set will atrophy and I’ll lose my sharpness. So it’s a balancing act.
But this brings up another wider question: where is the line between “occasionally getting AI help” and “vibe coding”? Surely it’s subjective.
Buffalobuffalo@reddthat.com 2 hours ago
The definition may have changed but I feel like originally it was only vibe coding when the “dev” did not know what they are doing. When some one with little to no programming background is able to build and app on “vibes” alone.
MagicShel@lemmy.zip 2 hours ago
I don’t think the two cross, really. A vibe coder asks for a bunch of features and then starts refining the output, fixing bugs and adding features. A developer knows the specific architecture and from years of writing tasks knows how to break work into manageable chunks and uses AI to implement something they have already defined and know where it fits in. The skill to write a good story isn’t far off from sitting a good prompt.
I use AI all the time, and every time I hear someone describing vibe coding it makes my skin crawl.
pheonixdown@sh.itjust.works 4 hours ago
I’d say the use cases of: mundane but time consuming, pointed inquiries or interactive rubber ducking, are all getting AI help. Offloading a design where you don’t have a clear understanding of how it should be done is vibing.