Technical growth in 2025 means understanding how to use LLMs effectively more than your peers.
There's no going back to pre-LLM days. Just like we're not going to stop using machines to weave textiles.
Ask HN: Worth leaving position over push to adopt vibe coding?
31–40 of 99 posts
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#32I suspect that if you don't change the /sector/ of computing you are working in, you may run into the same thing elsewhere.
AI is being adopted mainly where it works, and where it works is where regurgitated code cobbed-together from what has been seen before is sufficient to get the job done.
Assume that your CEO and CTO are not complete idiots; that they have some rational argument for believing that the approach will work. It's also possible they are gambling on an experiment; if it fails, they will back off on it.
If you want to avoid being told to use AI, you have to work on legacy tech stacks that AI doesn't understand; algorithmically complex code; critical infrastructure code where one bad bit stops multiple machines and applications; safety-critical embedded where AI slop could maim and kill and so is out of the question, etc.
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#33I 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. In other words, be an engineer.
If that can’t be done where you are, or isn’t valued, you’re in the wrong place.
I’ve been through this with (including but not limited to) PCs, OOP, client-server, SOA, XML, NoSQL, blockchain, “big data”, and indeed, multiple definitions of “AI”. Turns out all but one of those were actually somewhat useful in the end, when applied properly, but they didn’t eliminate the industry. Just roll with it.
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#34I 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.
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#35[dead]
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#36Is it worth leaving? Hard to say for your specific situation, there's thousands of variables that no one here will ever know. Unless you are a superstar or independently wealthy, it's typically a bad idea to leave a job before you have something else lined up. Is it worth looking? Absolutely! It will be much easier to make a decision when you're comparing your current position to a job offer, rather than comparing yo…
Assume OP is talking about grabbing a new rope before letting go of another one; otherwise we are mixing generalities about career moves not specific to the issue in the topic.
>generalities about career moves not specific to the issue in the topic.
They explicitly asked for general opinions, and provided almost no context which would let me be more specific.
"Is it worth leaving position over push to adopt X" is not exclusive to AI, nor is it a new question, so I addressed the general case.
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#37I can't stop thinking what happened when CASE tools, WYSIWIG, UML, Model Driven Architecture/Development, etc was pushed into devs. I know, it's a different phenomenon (that was a graphical visual push, this keeps the text).
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#38Play along, but keep relatively detailed yet abstracted notes on how the AI code is failing. Keep these notes private ... type them into a notes program on your personal device so that you can draw upon them in the future if needed.
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#39Software engineering is not about typing. The LLM would write the unit tests based on the implementation you provide. Regardless of the LLM's output, you'd be expected to read and understand it before committing, or at the very least, review, refactor, tweak, etc. Reading is crucial for both personal and cognitive development. That is not vibe coding! There are top devs in the industry using them in top applications, such as Ghostty or Bun. The biggest names in the scene! The reality is that you would not know if your favourite app was partially or fully built with LLM help, sorry to disappoint!
Re: Ask HN: Worth leaving position over push to adopt vibe coding?
#40If 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