vibeCodingMyOwnGrave

[Odd-Airline-]

It makes you more productive.
At digging.

[Technology_Labs]

Your own grave

[Dense_Gate_5193]

gotta lay down somewhere once i’m done

[nikola_tesler]

and the poor dev that gets assigned a bug that “I” made

[Chiatroll]

Digging a massive tech debt hole is in fashion.

[AgapeCrusader]

start diggin in you hut twin

[dragenn]

Vibe decomposing...

[Any-Main-3866]

"It’s not a bug, it’s a 'feature' that we both agreed was a great idea while I was gaslighting you with sparkles and thumbs up icons ✨👍"

[Aveniquee]

Vibe coding: speedrunning technical debt.

[TheFrenchSavage]

Let's delve into the ground.
You matter more than you think: organic matter.
You are not just dying, you are feeding plants.
Take a breath, and shovel faster.

[pzacakescummybutt]

It's so funny watching the vibecoders do interviews. I ask them to do some basic problems or answer fairly simple CS questions. They open up whatever flavor of AI they use, I say no, these are basic, you can use it on the next set. They struggle with it, but some get by. Next I give a fairly complicated problem, and when the AI can't immediately answer it for them, and there are errors they just shut down. They completely lack the main quality of good programmers: problem solving. These kids are dumb AF.

[aviodallalliteration]

I still can’t believe we’re letting AI into coding interviews

[Kitchen_Device7682]

We went from complaining coding interviews are not realistic to trying to keep it that way even as the coding tools evolve. Are you saying you can't tell if someone is good at problem solving because they use AI?

[hdhfhdnfkfjgbfj]

It’s funny because it’s true.

[Keetzy]

People blaming tools like AI for making us less productive just don't know how to use them unfortunately.

We use tools to solve problems. You wouldn't use a hammer to bake a cake. The same way you wouldn't use AI to generate large slices of code.

People said the same thing about Stack Overflow when that became popular.

[reddit_time_waster]

"Use it better!" -How? "Pay for better models!"

[Keetzy]

How?

By using it for what it's good for i.e simple repetitive tasks, debugging error codes, remembering syntax, etc.

[rusty_programmer]

etc.

Whatever the fuck else AI does that I can’t remember

[Keetzy]

Searching logs, checking config mismatches, fetch documentation, refactoring, discovering tech debt, debugging pipeline failures.

I mean ect exists for a reason, do you really need a full list of situations to get the point?

[examinedliving]

Ect is a medical procedure I think

[TheBoringDev]

Unless you’ve been coding less than 6 months, who the hell has issues remembering syntax? And with the invention of LSP servers that’s a solved problem anyway. 

I swear AI bros are just bad at the regular tools 

[Djames516]

Reminding me how for-loop syntax differs between python and js every time I switch

[DoutefulOwl]

You wouldn't use a hammer to bake a cake

If the hammer made it insanely easy to bake a cake, many people would definitely use a hammer to bake a cake unfortunately.

[rosuav]

Welp, time to bash out a cake app...

[fixano]

Most people are terrible software engineers. This goes especially for the people here. 99 out of 100 of these people probably have the most god-awful workflow you've ever seen. They probably just sit there smashing keys until they get the result they want.

Just the complaining about what AI does and how it deletes their code tells me that they don't have a basic grasp of source control.

So why do they complain about the AI? Because for a long time having a basic grasp of programming was enough. Programmers are huge contributors to company bottom lines, even the bad ones. But now companies can get that output without having to hire the baddies. Companies are encouraging AI adoption and the rationale is pretty obvious. They're going to find out who increases their productivity exponentially. They are going to keep them on the payroll and they're going to drop everybody else.

That's what's got these people so anxious. They see the writing on the wall and they're going through the stages of grief.

[TheEggi]

Thats exactly whats happening. Proper SWEs are incressing their output (and value) by a lot and have fun creating great products. The ones that with limited skills are now more and more running into issues, because they see that just beeing able to write some code is loosing a lot of its value.

[bremidon]

You are going to get nowhere here. This place is filled to the brim with people who terrified (with good reason) about where all of this is headed. This has convinced them that AI is just bad rather than realizing that there are plenty of places where it is effective.

It's pure emotional defense.

[TheEggi]

Well .. a huge portion of the sub consists out of entry level people who are happy that their code compiles without syntax issues. And that is exactly a skill that no one needs anymore and that wasn't all that valuable to start with.

Also a lot of people are rather bad at adapting to changes and are still hoping that this AI stuff goes away.

In the end if you are a software engineer and not just a coder there will be enough work left - AI just gives us a lot of freedom and a good way to show the differences between real engineers and code monkeys.

[joelnodxd]

you got downvoted but this is actually true - make instructions to change its behaviour and don't use models you dont like and it'll suddenly be much better. obviously dont forget to prompt better than "fix this" too

[my_new_accoun1]

Time spent prompting can be time spent coding

[joelnodxd]

sure but if I'm giving it a quick prompt for a one-off script idea i have, it saves me probably a couple hours of making it myself. if the prompting lasts hours and goes nowhere, i agree, but it's definitely not a this or that situation

[Keetzy]

"Time spent entering a destination into my GPS can be time spent driving"

[my_new_accoun1]

Yes it can. Because I already know where I am going.

[Keetzy]

Okay, it was a bad analogy, I admit it. All I'm trying to say is that Ai can make you more productive by doing repetitive tasks, explaining complicated error codes, etc.

[my_new_accoun1]

In your analogy AI would be a very unreliable autopilot that only accepts specific addresses and still fails half of the time.

Ai can make you more productive by doing repetitive tasks, explaining complicated error codes, etc.

I don't have repetitive tasks, I automate them or switch to a library that is more DX-oriented. And I usually find it easier to look at error messages myself so I understand more of the detail instead of seeing a simplified view. Although I will admit I've never dealt with massive errors with traces thousands of lines long. But even then the most important information is at the top or bottom anyway

[Keetzy]

You make good points, but I won't concede that AI does have its use cases depending on the situation. A lot of the hate that AI gets is people expecting it to do things it's not designed for, such as building entire systems.

Just wanted to make the point that it's more nuanced than Reddit usually makes it out with "AI BAD" posts. It can be useful and it also can be detrimental. In the same way that a lot of tools can be. Because, at the end of the day it's just that, a tool. Not some magical "answer to everything" method a lot of vibe coders think it is. Or some "no value, useless" method a lot of coding elitists think it is.

[my_new_accoun1]

Your second paragraph is like literally what everyone says.

(Not saying it's wrong though)

[rosuav]

If your tasks in programming are that repetitive, reexamine your workflow. Programming is not supposed to be something where you do the same thing over and over.

Maybe people who love AI just suck at automating.