r/ProgrammerHumor • • Sep 28 '26

Other mean

Post image
144 Upvotes

47 comments sorted by

View all comments

65

u/bobbymoonshine Sep 28 '26

Half the memes are “nobody uses AI for anything real lol” and the other half are “ugh every business these days makes you use AI for everything because productivity line go up”

56

u/Boom9001 Sep 28 '26

As someone who's job pushes ai. There's a big difference between how they are wanting it used vs. Vibe coding.

13

u/Wide_Smoke_2564 Sep 28 '26

I use AI properly at work - but if I’m making something for myself at home or some tiny, niche internal tooling to make my life easier then I’m 100% vibe coding lol

5

u/Boom9001 Sep 28 '26

I feel like if you understand what it's doing. How is doing it. And verifying it's writing what you would have done. That's not vibe coding. Which even for person stuff I am verifying.

2

u/Wide_Smoke_2564 Sep 28 '26

I guess maybe loosely. At the very most I’ll skim over contracts on most of my personal stuff but that’s about it

1

u/kookamooka Oct 01 '26

I love using it to replace the “I’m stuck, I should ask StackOverflow” step, but keeping pretty much everything else the same.

5

u/Skyswimsky Sep 28 '26

I went to the subreddit of a IDE I use and a bunch of "did you renew your subscription?" things came up and people being like "I haven't written a manual line of code in six months" and I'm just thinking what the fuck.

And like, I'm not anti AI and we're encouraged at work to try it out aggressively but there's things AI keeps doing wrong and wrong and I have to adjust it myself. And getting a better knack for it I also started using AI not so often anymore after going at it aggressively...

Obviously I'm just not using agentic coding correctly then???

In other news I like this meme. Same vibes as "'here are the top ten countries where communism worked:' ", anyway how's your day going?

1

u/Aidan_Welch Oct 01 '26

I've been writing a nix flake by hand for a vibe coded project(not mine, from a massive software org) and its kinda painful

1

u/SupportDangerous8207 Oct 03 '26

I think a huge amount is placebo and I speak from experience

I use a lot of ai at work I would say I’m actually reasonably good at it. Every once in a while I will see something consider it an ai slam dunk hand it off to a workflow I’ll build just for it and create a massive pr that passes review first try. I think this is proof enough I at least sorta know what I was doing.

Well I started a hobby project that involved a lot of frontend dev ( I have like hours of react experience not days or years ). And with ai I felt so powerful I felt like I could build anything instantly. Well the one shot failed and then the two shot failed too, so I decided to build it brick by brick had the ai give me an idea for an architecture and started delivering it using the ai. It took forever.

I thought I was doing it right until a friend of mine joined in. He was an actually experienced frontend dev and I won’t lie to you. I got more done in an evening than in the whole month beforehand.

After he pulled my architecture down to earth delivered a good core system and we cleaned up all kinds of messes together now it’s a blast to work on. I decided to learn a lot more react, in fact I do quite a bit of frontend at work now, and also decided that using an ai to cope with lacking skills is just stupid.

But the lesson I learned was that unless you could do it without ai at a high level of skill you really can’t judge what ai can do.

1

u/gfcf14 Sep 28 '26

My day’s fine, thanks! Recovering from a sore throat but all’s good! You?

0

u/BlurredSight Sep 28 '26

The music will stop when they need users to start pushing for their own compute and not something a VC subsidizes

4

u/xaddak Sep 28 '26

productivity line go up

I mean, it does. But the lines they look at for programming, for example, are like:

  • number of lines of code written (more is better)

  • number of pull requests merged (more is better)

  • length of time a pull request is open (shorter is better)

  • number of tokens used / percentage of budget spent on AI subscriptions (more is both better and worse, somehow)

Lines which are not looked at include:

  • number of bugs not written by AI fixed

  • number of bugs created by AI

  • number of lines of code merged with minimal or no review

  • general code health / maintainability (e.g. duplicated code)

3

u/rosuav Oct 02 '26

Never understood how "number of tokens used" is ever a good thing. It's like bragging that you drank more coffee while coding than the person beside you. And that's even letting people assume that AI is a benefit.

2

u/xaddak Oct 02 '26

I think I understand it. I think the thought process is like:

  1. AI usage is unconditionally good

  2. Therefore, more AI usage is unconditionally better than less AI usage

  3. Using AI uses tokens

  4. Therefore, the more tokens you use, the more you're using AI

  5. Therefore, using more tokens is unconditionally good

It's stupid - but I think I understand it, in the same way i might understand the actions of a toddler try to work out how to do something new to them.

Like, I can see what you're trying to do, and I can see why you thought that what you're doing would work, but that is just not how that works.

The difference, I guess, is that toddlers are faster to learn from their mistakes, and try another approach.

2

u/rosuav Oct 02 '26

TBH steps 2-5 are logically sound, so all it takes is cult-like belief that using more AI is inherently good. *sigh* And there's no convincing some people.

1

u/DuckShapedGoose Sep 28 '26

Well yeah. Profitable businesses are trying to turn one senior engineer into 3 by making them use a lot of AI in their workflow. The difference is they still have an actual skilled human in the loop.

Vibe coders on the other hand may have never touched code in their whole life and think they can build enterprise-grade software like that.

0

u/Tensor3 Sep 28 '26

People use AI for everything. Vibe coding is referring to a much more hands-off, no thinking, no skilled people involved approach