问 HN:因为要推行 Vibe 编码而离职,值得吗?

6作者: NotAnOtter大约 1 年前
我的公司越来越推崇提示工程,将其作为我们“应该”使用的唯一编码方式。首席执行官和首席技术官都对此着迷,并提倡诸如“删除整个单元测试文件,然后让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.