Ask HN：我如何才能找到一份工作，专注于编写高质量代码，而不是疲于应付紧急情况？
5 分•作者: speeder•3 个月前
今天我看到了关于人工智能摧毁西方软件业未来的帖子。我回想起自己也面临着类似的工作困境。
目前我的生活是这样的：一些公司失去了资深员工，他们雇我去顶替。他们希望我在两个月内以相同的速度和质量产出代码。
然后他们意识到他们实际上已经落后了（例如，有一家公司晚了 6 个月才向客户交付），并希望我使用人工智能更快地生成代码。
与此同时，我发现他们失去了所有了解实际运作方式的人，没有文档，或者更糟的是，文档完全是错误的（我参与的一个项目有数千个 Jira 票据是从需求文档生成的。经过几个月的政治斗争，我获得了查看需求文档的许可，结果发现它完全来自另一个项目，他们浪费了数年时间用错误的需求进行编码！）。
然后，当我快要结束试用期时，公司会尝试某种“孤注一掷”的策略，一家公司认为，如果他们解雇他们的 DevOps 工程师，并让我去做离职的资深工程师、被解雇的 DevOps 工程师的工作，并在两周内学习 Go 语言（我被聘为 C 语言开发人员，甚至不是 C++），我可能会更有用。然后，当这种荒谬的“孤注一掷”失败时，我就被解雇了。
一段时间以来，我一直在反复尝试，但结果总是相同，试图找出我做错了什么，现在我得出结论，我在错误的地方找工作。
每次被解雇时，都会出现同样的批评：我花了太多时间钻研“兔子洞”，研究遗留代码的细节，或者调试、修复问题或重构，而没有花足够的时间快速交付代码以安抚客户。我一直在努力改变这种行为，但都失败了，也许我应该去找一份能把这种行为视为优点而不是缺点的工作，但我不知道该去哪里找。
查看原文
Today I saw that post about AI destroying the future of West software. I remembered I am having a similar struggle with my jobs.<p>Right now my life is like this: some company lost their senior, they hire me to replace. They expect me to produce code with same speed and same quality in 2 months.<p>Then they realize they are late actually (one company for example was 6 months late to deliver to clients) and want me to use AI to churn out code even faster.<p>Meanwhile I find out they lost all people that knew how things actually worked, there is no documentation, or worse, the documentation is outright wrong ( one project I worked had thousands of Jira tickets generated from a requisites document. After some months of politicking I got permission to see the requisites document and learned it was from another project entirely, they wasted years coding with the wrong requisites outright! )<p>Then as I get close to the end of probation period, the company tried some kind of hail Mary, one company thought maybe I would be more useful if they fired their DevOps and asked me to do the job of the senior engineer that had quit, the fired DevOps, and learn Go (I was hired as C dev, not even CPP) in 2 weeks. Then when the absurd hail mary fails I get fired.<p>For a while I have been trying again and again with always same results, tried to see what I was doing wrong, and now I concluded I am looking for a job in the wrong places.<p>Every time I got fired the same criticism happened: I spent too much time going into "rabbit holes" and figuring out details of legacy code or debugging or fixing things or refactoring, and not enough time just shipping code fast enough to appease clients. I keep trying to change this behavior and fail, maybe I should instead find a job where this behavior is something good instead of something bad, but I have no idea where to look.