Live data from Hacker News

Vibe engineering

simonwillison.net

21–30 of 759 posts

Re: Vibe engineering

#21
post #2

Just added this note to the end, as part of my justification for picking such an obviously stupid term for this: > I’ve tried in the past to get terms like AI-assisted programming to stick, with approximately zero success. May as well try rubbing some vibes on it and see what happens.

We can resurrect CASE: https://en.wikipedia.org/wiki/Computer-aided_software_engine...

“casing”?

Re: Vibe engineering

#22
post #15

I’d just call it “coding” – it’ll be the default soon enough. For the old way: “hand-coding”

I've definitely heard people semi-seriously refer to the old way as "artisanal coding".

Someone called it "brain coding" the other day which I quite enjoyed: https://domm.plix.at/perl/2025_10_braincoded_static_image_ga...

Re: Vibe engineering

#23
Vibe is just a bad word to describe anything that requires skill beyond "taste". A word play off of "AI assisted programming" is probably going to be the term that sticks. AIssisted? pAIr programming...

Re: Vibe engineering

#24
post #4

Earlier quoted context omitted.

The AI adds a ton. It really is like having a whole team of extra coders available, all of which can type faster than you. Getting good results out of that team is hard , because the bottleneck is how quickly you can review their workflow and point them in new directions. Understanding techniques like TDD, CI, linting, specification writing, research spikes etc turns out to be key to unlocking that potential. That's…

I've yet to get any quality code out of one, though I don't try particularly hard either. I'd rather spend my time actually coding, especially since all the positive stories about enhanced productivity are anecdotes, and the hard data remains far less supportive of the claim.

While I don’t agree with you, I keep a healthily skeptical outlook and am trying to understand this too - what is the hard data? I saw a study a while ago about drops in productivity when devs of OSS repos were AI assisted, but sample size was far too low and repos were quite large. Are you referring to other studies or data supporting this? Thanks!

Re: Vibe engineering

#25
post #14

I feel using the word 'vibe' is inherently giving it a negative connotation which goes against the idea presented here. The reality is the tools are really useful when used as tools, like a power drill vs. a screw driver. Vibing implies backseat driving which isn't what using the tools proficiently is like. The better term would be 'assisted' or 'offloaded'. Same thing with the term 'engineering'. That's a fairly new…

> That's a fairly new term that implies being engineers which we are not. We haven't studied to be engineers, nor have real engineering degrees. We've called ourselves that because we were doing much more than the original job of programmer and felt like we deserved a raise.

Uh, speak for yourself. There are countries where being a software engineer does indeed imply that you studied engineering and hold a "real" engineering degree.

Also, Hillel Wayne's "Are We Really Engineers" is worth reading:

https://www.hillelwayne.com/post/are-we-really-engineers/

Re: Vibe engineering

#27
post #15

I’d just call it “coding” – it’ll be the default soon enough. For the old way: “hand-coding”

I feel a certain way when I hear about older programmers who used to program using punch cards, I guess everyone in the future will think about us in the same way?

Re: Vibe engineering

#28
"Vibe coding" implies it's newbies throwing prompts and hoping some of them stick.

For the experienced lot of us, I've heard many call it "hyper engineering"

Re: Vibe engineering

#29
post #15

I’d just call it “coding” – it’ll be the default soon enough. For the old way: “hand-coding”

I've definitely heard people semi-seriously refer to the old way as "artisanal coding".

That's actually a pretty reasonable description I think. I mean, in the semi-serious way. But I was just talking to some colleagues of mine about how one can get attached to or invested in code that they hand wrote, even though that code wasn't really solving a problem that was "worth" that level of attachment. And AI assisted code generation changes the dynamic for code that fits in that category for me, and it just so happens to be a lot of the code people write for work fit into that. You only really need to be "artisinal" about the code that "really matters".

Re: Vibe engineering

#30
post #14

I feel using the word 'vibe' is inherently giving it a negative connotation which goes against the idea presented here. The reality is the tools are really useful when used as tools, like a power drill vs. a screw driver. Vibing implies backseat driving which isn't what using the tools proficiently is like. The better term would be 'assisted' or 'offloaded'. Same thing with the term 'engineering'. That's a fairly new…

Same, I feel like the word vibe paints a picture of some dude ripping a bong while pressing enter.

If you can’t do it while you’re also singing a karaoke song, then you’re not vibing.

I have fairly decent engineering credentials, but when the task fits, I prefer to vibe code.

Post reply on HN