问HN:为了推动采用氛围编码,值得辞职吗?

6作者: NotAnOtter7 个月前原帖
我的公司越来越强调提示工程,认为这是我们“应该”采用的唯一编码方式。首席执行官和首席技术官对此非常痴迷,提倡诸如“删除整个单元测试文件,让Claude生成一个新的”这样的做法,而不是手动解决测试失败的问题。 我是一名拥有约5年行业经验的“高级工程师”,正在考虑离开这家公司,因为我不想: 1. 被迫进入一种会导致我技术成长停滞或退步的工作流程 2. 在2-3年后管理一堆AI生成的混乱代码 欢迎您针对我的具体情况提出建议,但我也对更一般的看法感兴趣。
查看原文
My company is increasingly pushing prompt engineering as the single way we &quot;should&quot; be coding. The CEO &amp; CTO are both obsessed with it and promote things like &quot;delete entire unit test file &amp; have claude generate a new one&quot; rather than manually address test failures.<p>I&#x27;m a &#x27;senior engineer&#x27; with ~5 years of industry experience and am considering moving on from this company because I don&#x27;t want<p>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<p>Feel free to address my specific situation but I&#x27;m interested in more general opinions.