I've been watching the /r/cli and /r/tui subreddits for some time. The amount of vibe coded apps posted there just continues to climb. Some people in the comments for these apps can be quite rude when they read the description and find out its vibe coded. Nevermind how vile some can be when it's not in the announcement but the author lets them know down the line in the comments.

▲

nebula8804 2 hours ago | parent | next [-]

Ha! I got raked over the coals when I asked for some help in a vintage Apple subreddit. I described the problem, what I tried to do to solve it and at the very end I also mentioned that I asked AI and that it gave me an absurd answer. So many people just read the one line and gave me an earful.

▲

insin 4 hours ago | parent | prev | next [-]

/r/chrome_extensions feels like it's getting close to being 100% LLM generated, extension code, submission descriptions which read like you accidentally went to LinkedIn, and generic LLM replies

	▲	datadrivenangel 2 hours ago \| parent [-]
		I didn't trust any of the chrome history extensions so Claude Code made me one in five minutes...

▲

slopinthebag 4 hours ago | parent | prev | next [-]

To me this is fair. If you vibe code something and try to pass it off as your own work people will be angry about the deception.

▲

steve_adams_86 3 hours ago | parent | next [-]

I don't love seeing slop everywhere and I don't feel good about models being trained on people's hard work, but... I also have a hard time believing my work was ever much different. I've always regurgitated and synthesized existing solutions. I took them from open source examples. I read people's blogs. I'm basically a really slow LLM most of the time. Is that a form of deception too? I really wonder how much of a difference it is sometimes. Maybe LLMs are just a shortcut of sorts to get where we've previously gotten using very similar means. Just absorbing and recycling ideas, learning by reinforcement, so on.

▲

slopinthebag 3 hours ago | parent [-]

No, building on top of other peoples work is fine. Taking credit for work you didn't do is not the same.

	▲	steve_adams_86 3 hours ago \| parent \| next [-]
		That's a valid take. I think there's substance to that claim. Maybe what I've been struggling with lately is how blurry the lines seem to be. When am I building on top of something, and when am I claiming credit I don't deserve? Along these lines, an interesting category of work is when I have an LLM do something I could do myself. I totally understand the code, I instruct it all the way, I have it redo things, revise, rejig, etc... But I don't actually write any code. How responsible am I for any of that? At work there are a ton of small scripts I use for piping data around ad-hoc, and this is often how I do it. Claude can make dumb pipes really well and remarkably quickly with reasonably clear specs given to it. I compose all kinds of specs, reports, plans, etc. using this workflow. And I find myself wondering... How much of this is me? How much credit do I deserve? The code is gone, the outputs remain, and I can't quite tell how responsible I am for the end product. It's a strange experience.
	▲	an hour ago \| parent \| prev [-]
		[deleted]

▲

podnami 3 hours ago | parent | prev | next [-]

Do you have to know Assembler to be able to write code in Java? With the point being that you rarely know the underlying mechanics - and the same if true for vibe coding.

	▲	cbg0 3 hours ago \| parent \| next [-]
		This is not a good analogy.
	▲	slopinthebag 3 hours ago \| parent \| prev [-]
		Nah, but you have to actually put the work in to get the credit. Lazily vibe coding slop and then passing it off as your work is like claiming you cooked a microwave meal.

▲

woah 3 hours ago | parent | prev [-]

Who cares?

	▲	slopinthebag 3 hours ago \| parent [-]
		I do, and plenty of other people. It's fine if you don't, but people will justifiably let you know how they feel about that :)

▲

DeepYogurt 4 hours ago | parent | prev [-]

Are any of them good?

▲

steve_adams_86 3 hours ago | parent [-]

In my experience no, but I don't think that's a problem.

It's fascinating to see so many ideas and so much enthusiasm. I sometimes wonder if the fervor will die down as people realize it's still really hard to make truly fantastic software, but it's hard to say. There's a ton of inertia behind the vibe coding rush.

I also wonder if vibe coding is actually somewhat incompatible with the states of mind and contemplation that's often required to figure out how to solve problems properly. It isn't clear if you can brute force great solutions without putting in the initial domain distillation and idea incubation and so on. I'm sure there are exceptions but I have a feeling it'll never be trivial to come up with truly good and novel ideas for software, and vibing to get there might not make it any easier.

	▲	pacificpendant 2 hours ago \| parent [-]
		Without giving away exactly how old I am… I am old enough to remember old programmers complaining about the wave of new shareware/freeware apps that people made with Visual Basic when that came out. Many of the apps were visually awful because it opened up desktop app development to people with no aesthetic experience. I don’t see that awful style any more despite those tools for rapid UI creation still existing, did those people get better or did they get bored and move on to other things? I guess the same will happen with vibe-coders, they’ll get the experience to make better software or their poor quality apps won’t give them what they want and they’ll move on.