←back to thread

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

61 points NotAnOtter | 3 comments | 04 Jul 25 22:20 UTC | HN request time: 0.508s | source

My company is increasingly pushing prompt engineering as the single way we "should" be coding. The CEO & CTO are both obsessed with it and promote things like "delete entire unit test file & have claude generate a new one" rather than manually address test failures.

I'm a 'senior engineer' with ~5 years of industry experience and am considering moving on from this company because I don't want

1. Be pushed into a workflow that will cause my technical growth to stall or degrade 2. Be overseeing a bunch of AI-generated spaghetti 2-3 years from now

Feel free to address my specific situation but I'm interested in more general opinions.

1. Ancapistani ◴[04 Jul 25 23:43 UTC] No.44468924[source]▶
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 that environment will help your career.

replies(2): >>44469389 #>>44469771 #
2. GianFabien ◴[05 Jul 25 01:23 UTC] No.44469389[source]▶
All of the above +

Start looking for a new role that is better aligned with your expectations. You may find it harder than you expect. In which case, you might be glad you didn't burn your bridges in a pique over AI mandates by the CEO & CTO.

3. andrei_says_ ◴[05 Jul 25 02:49 UTC] No.44469771[source]▶
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.