←back to thread

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

63 points NotAnOtter | 1 comments | 04 Jul 25 22:20 UTC | HN request time: 0.345s | 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. KronisLV ◴[05 Jul 25 08:24 UTC] No.44471050[source]▶
> delete entire unit test file & have claude generate a new one

Why not just add new tests or refactor the existing ones? Seems kind of silly.

Aside from that:

  - if you don't like AI tools and can afford to do so, then look for a place that matches how you want to work
  - if you do like AI tools, or are open to learning them, then there isn't an issue (aside from maybe how they're used)
There isn't much more to it: https://blog.kronis.dev/blog/ai-artisans-and-brainrot (bit of a rant of mine on the topic, the tl;dr would be that the cat is out of the bag in regards to these tools and there are both positives and negatives, but they lead to brainrot and degradation of skills the same way how IDEs and StackOverflow did, just a large leap further)