Ask HN: Is vibe coding a new mandatory job requirement?

So many companies and products were built on a pivot. Why try to imagine the exact problem, user, success, etc. when you can build in seconds (or more reasonably days) and then find the right users' problems to rebuild around from actual users?

It might feel like kicking the can down the road. But it's a much more informed decision when users churn or they don't. And you can reach that decision point just about as quickly as a long thinking/planning phase.

Thinking while building is bad when paying multiple high-dollar humans for months per rebuild. It's arguably better when a full redesign costs you $10.57.

Vibe coding seems like a religion more than anything to me: engineers go and use techniques for prompting but rarely actually test those techniques relative to other ones. There is especially no evidence that vibe coding is a skill: the people most effective with these tools are people who would've been most effective without them (i.e. it relies on experience and domain knowledge).

If I were currently actively hiring and I wanted to capture skills that likely will translate well to an AI-augmented work strategy, I would focus on "code review" in the interview. I've only seen a handful of truly great, rigorous code reviewers in my career, but AI makes code review supremely important. Unfortunately, most of the real world "agentic coding" I've seen is light in review (lots of LGTMs!).

I think that firms are going to eventually collapse under their own weight unless models continue improving at the velocity slop is merged into main.

I will also note that I do use these tools, mainly as a search engine, and I do so in hiccups (I will use the tools for a month and then completely abstain for 1-2 months). I am worried about undermining my own cognitive fitness by overreliance on these tools.