请问HN：我该如何找到一份需要扎实代码而不是应急处理的工作？
今天我看到了一篇关于人工智能摧毁西方软件未来的帖子。我想起我在工作中也面临着类似的困境。
现在我的生活是这样的：某家公司失去了他们的高级工程师，他们雇佣我来替代。我被期望在两个月内以相同的速度和质量产出代码。
然后他们意识到其实他们已经延迟了（例如，有一家公司交付给客户的时间晚了六个月），于是希望我利用人工智能更快地输出代码。
与此同时，我发现他们失去了所有了解实际工作流程的人，没有文档，或者更糟的是，文档完全错误（我参与的一个项目中，从需求文档生成了数千个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.