61 points NotAnOtter | 1 comments | 04 Jul 25 22:20 UTC | HN request time: 0.225s | 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. rogerthis ◴[05 Jul 25 00:17 UTC] No.44469094[source]▶

>>44468375 (OP) #

I 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).

↑

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