←back to thread

61 points NotAnOtter | 1 comments | | HN request time: 0.205s | 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. gary17the ◴[] No.44470659[source]
Vibe coding/prompt engineering automatically accumulate "technical debt" of spaghetti code and thus with time cause every larger project to fail. Sooner or later you will be asked to fix all that AI mess in your company codebase and when you respond that you are unable to do so without a major, manual rewrite, you will probably get fired. Stay at your job for as long as possible, but start searching for a new position ASAP in an organization that declares up front that they do not intend to use AI for their codebase as a matter of company policy. There are actually companies out there already that make that kind of choice, but it might take a year or two for you to find such a job in the current job market. If all else fails, switch to the Linux kernel/driver development specialty with C/Rust for companies like Canonical.