YHK - yet another hacker news clone

This is certainly the case in the field of bioinformatics right now, so I do feel it's a little apt.

(HN is a bit of a bubble - it's about the only place on the internet where you can be cautiously positive about agenting coding and not be abused.)

And I think that's one important difference: with vibe coding you can't cast aside the AI after you've taken the initial step.

before someone cries false analogy they should realise that widget is literally a technical term in SWE for a GUI component.

https://en.wikipedia.org/wiki/Graphical_widget

Pivoting from programming-brained to business-brained has proven so successful for the likes of Bill Gates, that quite a few other programmers have done likewise (including arguably the esteemed founder of this place, Paul Graham). In addition, the filed has attracted so many people who are indeed business-brained and mainly in it for the money, especially over the past 20 years or so.

I used to gently make fun of colleagues of mine at college, who switched majors from computer science to MIS (Management Information Systems) as they discovered that programming is hard and math is hard. I thought of MIS as "computer science on easy mode", and called the textbooks they used "Richard Scarry books"[0] because they were full of busy-looking illustrations but lacking in depth.

Serves me right for my arrogance, I guess, because the Richard-Scarry-book kids are winning bigly, going from zero to go-to-market in no time flat with LLM agents to do the work they were afraid of in college.

Having a business brain is the new moat.

[0] Richard Scarry was an American children's book author, known for his books whose pages were filled with large colorful illustrations of the animal citizens of Busytown. https://en.wikipedia.org/wiki/Richard_Scarry

So lots of personal one-off tools/dashbooards that I never would have made before will probably live forever on my personal git server instead of github or somewhere.

1. People who let agents drive designs/plans and just let them rip (what I would /actually/ call vibe coding) -- who place value in the final product, and aren't shameful about the tools used to get there as long as the product is "good"

2. People who provide (or collaborate with AI on) designs/plans and use AI to write the code (which I wouldn't call vibe coding, but often gets conflated) -- who place value in the planning, and aren't shameful about the tools used to implement them as long as the architecture is "good"

Either way: I'd say most people who "vibe code" (in either category) are a little annoyed at the term inherently belittling what they make, but generally dismiss the term rather than feel any shame about it.

I'd be surprised to learn anyone in my programming network doesn't use any AI anywhere. It's a very powerful tool that's integrated pretty much everywhere into the 2026 Developer's toolkit, and the question is generally /where/ you use it (or not), not whether you use it at all.