tbh, i don't want to keep up now. if it's that special, it will reach me, i'll know about it. the extreme hype around gen ai over the past 3-4 years kind of overdid it for me, it made me tired. i did want to once be at the top, follow twitter threas, newsletters. now i want what works. claude code for work, claude web for general tasks, chatgpt periodically when i want it to do some research. that's it. periodically i get to know a about a new advancement, i give it a try, if it sticks, cool, if it doesn't cool. i keep moving ahead.

so this is not n8n but conversational.

if the author knows what they're doing and understand the model of the code at least, i don't understand the reason mentioning that it was vibe coded. maybe declaring something is vibe coded removes part of the responsibility nowadays?

Someone once told me that their mistake wasn’t theirs, but rather it was ChatGPT being wrong.

I think you have a good point about why people say it was vibe coded.

It might also be because they want to join the trend -- without mentioning vibe coding, I don't think this tool would ever reach #1 on Hacker News.

HN guidelines say one shouldn't question whether another commenter has read TFA, so I won't do that. But TFA explains exactly why it was vibe coded, and exactly why they're mentioning that it was vibe coded, which is that that was the central point of TFA.

yes. not that expensive.

i don't understand why do competent people need to mention that they vibe coded something.

It's a disclaimer that they have no idea what they code does.

It's just because vibe coding is still "new" and various people have mixed results with it. This means that anecdotes today of either success or failure still carry some "signal".

It will take some time (maybe more than a decade) for vibe coding to be "old" and consistently correct enough where it's no longer mentioned.

Same thing happened 30 years ago with "The Information Superhighway" or "the internet". Back then, people really did say things like, "I got tomorrow's weather forecast of rain from the internet."

Why would they even need to mention the "internet" at all?!? Because it was the new thing back then and the speaker was making a point that they didn't get the weather info from the newspaper or tv news. It took some time for everybody to just say, "it's going to rain tomorrow" with no mentions of internet or smartphones.

It's like how in space, they just call the "space bar" the "bar".

I wouldn’t be surprised if it’s actually a plus in the eyes of possible new employers these days.

vibe coding in my understanding is losing/confusing the mental model of your codebase, you don't know what is what and what is where. i haven't found a term to define "competently coding with ai as the interface".

I agree. But management types bedazzled by AI probably see these kids as the future leaders of our profession.

For the same reason competent people need to mention that X utility was (re)written in Rust.

I would guess the reason there is opposite. Like code that even newcomer can safely edit.

But in general you are right. The article was for developers so mentioning the tool/language/etc. is relevant.

I mean, they seem to address that pretty directly in the post

> Two years ago, I wouldn’t have bothered with the rewrite, let alone creating the script in the first place. The friction was too high. Now, small utility scripts like this are almost free to build.

> That’s the real story. Not the script, but how AI changes the calculus of what’s worth our time.

"My static blog templating system is based on programming language X" is the stereotypical HN post. In theory the choice of programming language doesn't matter. But HNers like to mention it in the title anyway.