Live data from Hacker News

Ask HN: Worth leaving position over push to adopt vibe coding?

news.ycombinator.com

51–60 of 99 posts

Re: Ask HN: Worth leaving position over push to adopt vibe coding?

#51

I'm a senior engineer with 20+ (oof) years of industry experience. I appreciate that this sucks and you don't want to do it. I wouldn't either. That said, it's a hirer's market out there right now. There will be plenty of people who will be happy to take your position while you're looking for something you prefer. My opinion is that we're going to have about 5 years of this. Managers and C-suite folks are going to do…

I feel I'm sort of stuck in the opposite situation of OP. I manage a few massive codebases that I simply cannot trust an AI to go mucking around with. The only type of serious AI coding experience I could get at this point would be to branch one of these and start experimenting on my own dime to see how good or bad the actual experience is. And that doesn't really seem worth it, because I know what I want to do with…

I do a lot of non-work AI stuff on my own, from pair programming with AI, asking it to generate whole things, to just asking it to clarify a general approach to a problem.

FWIW, in a work environment (and I have not been given the go-ahead to start this at my work) I would start by supplementing my codebase. Add a new feature via AI coding, or maybe reworking some existing function. Start small.

Re: Ask HN: Worth leaving position over push to adopt vibe coding?

#52
post #8

No. Good luck.

this comment is presented to you by "ShortsAI - never say nothing, never too much".

“Should I quit? My boss wants me to use”

  Assemblers
  Compilers
  Relational Databases 
  Garbage Collectors
  The Internet
  Source Control

Re: Ask HN: Worth leaving position over push to adopt vibe coding?

#53
post #20

It's the same elsewhere. Some places are actually using it as a way to get rid of people 'resistant to change'. It also remains to be seen what technical skills we need 5 years from now. I did memory management and pointers 15 years ago and I can still do them now. What I'd suggest is adapt to it, find ways to push back. Obviously things like "delete entire unit test file & have claude generate a new one" is a bad id…

> I've seen claude "monkey patching" a system so that it returns true to the tests.

I’ve watched Github Copilot do the same thing. I’ve also seen it doubling down on ridiculous things and just spewing crash-laden messes. There seems to be a low upper ceiling on how “competent” it is, which makes sense.

Re: Ask HN: Worth leaving position over push to adopt vibe coding?

#54

I’ve been doing this for 20 years. I see it as you having two primary options. You should stay there, learn the new tech, and see what happens. If it works better than you expected, then your mind will be changed and you’ll be well positioned for the new economy. If it turns out how you expect, now you have experience working with this tooling to inform your positions at your next company. Either way, a few months in…

I have the same recommendation.

Learn the strengths and weaknesses of the new technology and add it to your resume.

Become the AI advisor who can help an organization adopt the tech where appropriate and avoid the traps associated with top-down hype- and fomo-driven adoption.

Also who knows where the AI cycle will be in 2-3 years. My sense is by then we will see the cost of tech debt caused by LLM generated code, the cost of the ignorance and naïveté of vibe coding and the cost of VC money wanting its ROI on a subsidized tech.

Re: Ask HN: Worth leaving position over push to adopt vibe coding?

#55
Yep, your company is pretty much doomed.

CEO can afford being somewhat ignorant about the nature of engineering work or how llms work (still a red flag for a tech company).

But CTO being that stupid (if you don’t exaggerate) leaves little room for doubts.

Re: Ask HN: Worth leaving position over push to adopt vibe coding?

#56

If you are not at least using these tools, more so than vibecoding but understanding how to improve your craft, you are going to lose. I’m now 100% behind AI gen code as it has given me 10x powers. Ask the right prompts, get the best code. AI, if you reject it, yngmi

Why the anon account though?

Re: Ask HN: Worth leaving position over push to adopt vibe coding?

#57
post #34
post #33

I know with only 5 years experience this may not be obvious, but this is only the first of many “revolutionary” technologies making everyone around you lose their minds that you’ll have to deal with in your career. Like every other such technology, I recommend that you engage with it, understand it, relate that experience to what your employer does, and be the voice of knowledgeable pragmatism about where to use it.…

Reminds me when Rational Rose and UML were briefly famous in the late 90s. What an absolute piece of crap that the suits pushed to use.

I remember at the time that Rational Rose was going to allow non-programmers to make apps…

History doesn’t repeat, but it rhymes

Re: Ask HN: Worth leaving position over push to adopt vibe coding?

#59
post #34

Earlier quoted context omitted.

Reminds me when Rational Rose and UML were briefly famous in the late 90s. What an absolute piece of crap that the suits pushed to use.

I remember at the time that Rational Rose was going to allow non-programmers to make apps… History doesn’t repeat, but it rhymes

This time is different.

No, really. This time is different.

Re: Ask HN: Worth leaving position over push to adopt vibe coding?

#60

I'm a senior engineer with 20+ (oof) years of industry experience. I appreciate that this sucks and you don't want to do it. I wouldn't either. That said, it's a hirer's market out there right now. There will be plenty of people who will be happy to take your position while you're looking for something you prefer. My opinion is that we're going to have about 5 years of this. Managers and C-suite folks are going to do…

I feel I'm sort of stuck in the opposite situation of OP. I manage a few massive codebases that I simply cannot trust an AI to go mucking around with. The only type of serious AI coding experience I could get at this point would be to branch one of these and start experimenting on my own dime to see how good or bad the actual experience is. And that doesn't really seem worth it, because I know what I want to do with…

With all due respect, and I’m particularly anti-LLM, you sound exactly like someone who has never tried the tech.

You can use LLMs without letting them run wild on the entire codebase. You have git, so you can see every minute change it makes. You can limit what files it’s allowed to change and how much context you give it.

You don’t have to give it root on your machine to make it useful. You don’t have to “Jesus, Take the Wheel”. It is possible to try it out at a smaller scale, even on critical code.

Post reply on HN