[flagged]
Ask HN: Is vibe coding a new mandatory job requirement?
71–80 of 92 posts
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#72[dead]
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#73There is a big difference between vibe coding and using an LLM to assist with coding. Vide coding is just accepting what ever slop it outputs and saying LGTM. You are not going to get quality code that way. You need to review what it does. I often find that it uses outdated libraries and deprecated functions.
Some ways an LLM can assist with coding: I recently needed to refactor a bunch of code. Claude was very helpful this and it completed in about 5 minutes what would have taken me a couple of hours by hand.
Also they are very handy when using new frameworks and libraries. As we all know documentation for open source projects is often lacking. Just yesterday I ran into this. I pointed Claude at the projects GitHub repo and had the answers to my questions in just a couple of minutes. Manually I would have been spending a hour or two reading the code to figure out what I needed.
They are very handy when debugging. Get a weird hours that makes no sense. Instead of banging your head against the wall for a few hours, an LLM can help you find the problem much quicker.
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#74I couldn't imagine wanting to hire someone who doesn't use LLMs for coding unless they are bringing something very special to the table. It accelerates many coding tasks significantly. But you have to know the limitations to use them efficiently and that only comes with experience.
I don't understand why anyone would want to work for a firm that will not allow their employees to do their entire job properly, but will instead insist that they delegate a large portion of it via natural language of all things to some stochastic parrot from hell and hope after enough iterations of this that it will all somehow turn out okay. This sounds like a complete nightmare! To be frank, this entire situation…
Even just using them for prototyping is a big gain. While they do have monetary cost to run, they massively reduce the time cost of experimenting.
They can also waste a lot of time if you end up over-reliant on them, but that's where experience with LLMs comes in. The nature of them means it's not an exact science, but you get a feel for how to best apply them.
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#75We do not interview for this nor care about it, despite using agentic and code complete tooling heavily. It's not a deep technical skill like C++ that requires years of hands-on experience. Spend a few weeks getting comfortable with Claude Code and you're probably at about parity with most devs. That seems like sort of a red flag to me to have that as a job requirement.
This has been my thought all along, not sure why I don't see it more. I'm not scared about being left behind, none of the tooling looks crazy enough that a few weeks of dedicated learning wouldn't catch me up.
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#76[dead]
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#77Jesus Christ. Imagine reading these comments even just a year ago. Don’t know/care about coding with AI? You’re unhireable now. Grim.
It's not a skill. Seriously. It's pretty simple to get started, just open codex/claude, and give it a shot.
Everything is a skill, depending on what the company values. Early on I used to do work for temp agencies, and they'd care about the ability to use (even on a rudimentary level) Microsoft Word, Excel, and how fast you could type. I'm sure you wouldn't care about anything like that, but it's about the same level of complexity as interacting with codex/claude today.
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#78[flagged]
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#79The distinction between coding-by-prompting and knowing what to build is the right one, but I'd push it further.
The problem with vibe coding isn't the coding part — it's that people are trying to think through their product while they're building it. That's always been a bad idea. AI just makes the consequences arrive faster.
Good product thinking happens before you touch any tool. What problem are you actually solving? For whom? What does success look like? What are you not building? These questions don't get easier with LLMs — if anything, because you can generate plausible-looking output so quickly, it's easier than ever to convince yourself you've answered them when you haven't.
The vibe coding mess isn't an AI problem. It's a 'skipped the thinking' problem that AI has made cheap enough to do at scale.
Re: Ask HN: Is vibe coding a new mandatory job requirement?
#80Earlier quoted context omitted.
If you aren't taking advantage of it, you are not a competent software engineer in 2026.
Many companies cannot take advantage of it. Not everyone is making toy CRUD web applications to help consumers purchase things they don't want. Some people are making safety critical applications, and many more are making highly sensitive applications. At my job, we just got agents. Because we had to self-host them in our new data center. Our product isn't the kind that can be used with Claude or Gemini, like, legall…
So you just said that you couldn’t use coding agents because you are doing “very important things”, while you clutch your pearls about what other people are doing but your company is in fact using coding agents…