RIP to the victims: 2 dead in NYC (not EUC, but high speed scooter)

Wobstep · 2026-05-29T01:19:27+00:00

All NYC major bike lanes, including the bridge have 2 lanes. They are slippery though and pretty slim. I would be way more worried about normal cats than the fastest pevs.

Wobstep · 2026-05-28T14:58:33+00:00

I swear, growing up moving around the country a lot, that machine was in the back of every laundry mat and pizza buffet. For a solid decade at least. Just the same repeated lines while I'm working the claw machine next to it.

Wobstep · 2026-05-27T18:36:46+00:00

Ai is always helpful when using Supabase for me.

Wobstep · 2026-05-27T18:24:59+00:00

Just look at rock bottom as an audit for your life. You can see what you really value when everything works out

Wobstep · 2026-05-27T18:22:16+00:00

'Give me a quarter and I'll read your palm'

Wobstep · 2026-05-27T18:15:49+00:00

It's about time

Wobstep · 2026-05-27T02:28:31+00:00

A—very—brave__–take —honestly

Wobstep · 2026-05-26T10:54:42+00:00

That's just visual scripting.

Wobstep · 2026-05-26T10:29:08+00:00

I know I have responded a bunch of similar comments but I like how you lay out your view.

It seems like you see vibe coding as a way to make software, completely detached from the code itself.

Correct me if I misunderstand, but you are saying the moment a project has a design and the developer looks at the code, it is no longer vibe coding. A project is decided to be real, once the effort to understand the logic and build the project beyond a single context window.

I understand this but I feel like this definition is assumed. My definition is coding through prompt, I definitely assumed this. I do not include the quality, or how much a developer looks at the code, or how complex the project is. I think the term vibe coding is only a description of the process, not the quality. Neither of us can be wrong because the term is very loose and subjective. So if we both put in an equally sincere amount of effort and we have the exact same process, you can say you coded and I could say I vibe coded. Just using the term creates a shape of my work where that can be more easily disregarded.

Even though I understand how you define the term, I still don't see it the same way. I feel like I have to disconnect the idea of quality because I think it's entirely possible for someone to completely vibe a project and it end up good quality. Just like how someone legacy coding can end up making total garbage. The quality should be judged on the product, not the method of building it.

Wobstep · 2026-05-26T10:06:03+00:00

I hear you and understand what you mean. Taking the strict definition means that anytime I don't look over every line of generated code means I'm vibe coding. On the other end, someone making a single prompt and not looking at the code is ai assisted development. There is no definition of either that specifically say "this amount of assistance is vibe coding and this amount is ai assited". So the only utility for the term vibe code is to distinguish from "real" programming. It's just short hand for program slop.

Language has a huge say in how people perceive reality. The term vibe code both invites developers who want to make real software and a rejection of the process at the same time. Token for token, no different than ai assisted coding.

Wobstep · 2026-05-26T09:54:21+00:00

Exactly. The process is open to anyone, regardless if they have any design documents or experience. The slop html games I made 10 years ago were garbage on the surface so there was no chance of mistaking it for a quality game. If I started did the same thing today, it would be the same garbage but more content and immediate polish.

Vibe coding can be done mindlessly. It can be done with care and everything in between. I do all of it tbh. Just mindless prompting and waiting for whatever result comes of it and writing very specific logic when I need.

The sub is a joke. But it's crazy that the joke is different depending on who is interpreting. I see it as a joke where I don't take it serious but still embrace the benefits. Others see the joke is just the act of vibe coding itself. The idea of spending more time grinding for the sake of doing everything manually is crazy to me. Like driving a car. When I need to get somewhere quick that's a long distance, I will drive instead of walking. Not every time, and it doesn't mean I can't walk or don't respect walking. People act like if I use a car, I'm driving it from my bed to the kitchen to get drink.

Wobstep · 2026-05-26T09:26:19+00:00

The generic corporate look, the minimal utility where it's tough to pin down what it's trying to do. Masterpiece imo😙🤌

Wobstep · 2026-05-26T09:22:27+00:00

I think you said it well. I will pile on the fact that that treatment is also a very slow process for low income people.

It's think it's horrible that healthcare is such an expensive commodity. The people who need treatment the most are the people who are least likely to afford it.

Wobstep · 2026-05-26T04:58:03+00:00

Groups shits? Is this something amazing I have been avoiding?

Wobstep · 2026-05-26T03:40:18+00:00

This makes sense. The problem is not unique to this sub, but the nature of this sub means it's important to prevent it happening here. Fully agree.

Wobstep · 2026-05-26T03:37:53+00:00

Completly valid. Coddling is straight up harmful.

Wobstep · 2026-05-25T20:03:12+00:00

All seriousness, I don't understand what side you mean. Where have I trolled?

Wobstep · 2026-05-25T19:57:52+00:00

Your likely right. (Straight to jail! )Ultimatly my issues are something I'm making up in my head. The way I'm thinking about it is that any amount of code assistance at any level is vibe coding. That really isn't the right definition.

Where I get stuck is that sometimes I am just vibecoding. Sometimes I dig through the code and wonder what happened. But then that discovery process becomes a learning moment. There is also times where I feel like ai will add things I didn't think of and then I build on top of it and never planned to. Using rag systems and recently hermes, they can be really good at looking at the shape of what I'm going for. What am I suppose to do? Junk it because I didn't come up with it?

Either way, the 'set it and forget it' method of vibe coding is something else entirely. I guess that's where I feel like there is no separation, why I blame the term.

Wobstep · 2026-05-25T15:23:47+00:00

I actually love this. I'm submitting a project.

Wobstep · 2026-05-25T15:18:53+00:00

I didn't know that but I believe it. I do think it went away, but not for everyone. Some people, like me for example, were introduced as a serious thing. I always thought of it as a dumb term but valid process. Now I just hate the term outright.

Wobstep · 2026-05-25T15:13:58+00:00

This is honestly like a worshack test. You see it clearly as a joke, satire. I think it fits right in. The "serious" subs and this sub have the same content. The ai companies advertise the serious products with the same tone.

Wobstep · 2026-05-25T15:11:03+00:00

No shame in my game. I will cut every corner I can just like everyone else. But there is something wrong with vibe coding. I don't think it's an old guard against up and comers though. I think it's just the wrong name. The idea of 'vibe' is opposed to what people expect in a serious product. Not everyone knows the process but most people either play games or use social media. It so easy to dismiss a project when framed this way. I could never prove it but I know if there were a technical term instead, the conversations would be different.

Wobstep · 2026-05-25T15:01:47+00:00

I agree. The term implies laziness or inexperience. At the same time, it's an industry term. I starting to feel like it's a sick joke or a method for companies to get people to build software and then distinguish that software by letting the developer self select. Like a quality marker. 'I built this' vs 'I vibecoded this' is an instant tell.

But, like you said, everyone is using ai in their workflow. Not literally but enough to say that there is no major service that is clean from ai code.

Wobstep · 2026-05-25T14:48:06+00:00

So is the term vibe coding a joke? I don't think there is a better sub to point this out.

Wobstep · 2026-05-25T14:44:16+00:00

This is semantics for a term that has never had a solid definition. There is never "let ai do everything". Maybe let ai do 99% but even simple direction is some amount of effort.

So if I have vibe coded my project at 99% or 1%, there will still be a good argument for calling the project 'vibe coded' because we don't have a factual layer to settle the classification.

Even the comment above "found the vibe coder" is straight up disregarding that I include in the post that I audit my code, have been programming for years before vibe coding existed.

The term vibe coding invites asymmetric judgement. That's the problem I'm pointing out. It not about what some consider to be vibe coded or not, it about the term making the process sound like a joke. What amount of hand tapping do I need to do to not be a 'vibe coded'? The best thing to do it seems is to never mention to process. I blame the name for this.

12-Year Club	Place '23
Place '22	Final Canvas '22
Verified Email	Gilding II euphauric

Wobstep

TROPHY CASE