请问HN:我该如何帮助一位经常出现拼写错误的同事?

5作者: tornadofart大约 1 个月前原帖
新年快乐!<p>这是个奇怪的问题,但我还是想问一下。<p>我的同事工作态度非常认真,努力工作,学习速度快,主动增加测试覆盖率等。我认为他的贡献是积极的,但他的一些工作确实会引发问题,尤其是在配置文件、Shell 脚本等方面,也就是那些不容易被代码检查工具或拼写检查器直接发现的错误。<p>他的拼写错误率相当高。我怀疑他可能有未被诊断的阅读障碍。<p>错误通常是在很晚的时候才被发现,主要是在预发布环境中,这使得问题变得繁琐。这导致了几次生产环境的故障。<p>我们有代码审查和完善的测试套件等,但拼写错误还是会漏掉——一旦你犯了错误,其他人就更难发现。<p>我为他感到难过,因为这已经在团队内部引发了指责游戏,有人问怎么会这么马虎。我并不怀疑他的马虎,因为他在其他方面都很细致。另一方面,这个问题在他身上变得非常敏感。<p>我怀疑他对这个问题有奇怪的意识,同时又处于否认状态,因此非常防御。<p>他的看法是我们应该增加测试覆盖率。这是解决方案的一部分。然而,一旦他参与编写测试,问题就转移到了编写正确的测试上。<p>我在考虑的方案有:<p>- 从根本上解决问题:调整我们的工具和配置机制,减少配置中的字符串,减少动态类型脚本等。<p>- 请他让人工智能专门检查他的代码以发现潜在的拼写错误。<p>- 增加测试覆盖率,由其他人而不是他来编写测试。<p>我没有考虑的方案有:<p>- 告诉他我怀疑他有阅读障碍。我不是医生。<p>我试图拓宽自己在这个问题上的视野,也许我漏掉了什么。你会怎么做?
查看原文
Happy new year!<p>Weird question but here goes.<p>My colleague has a strong work ethic, works hard, learns fast, goes out of his way to increase test coverage etc. I would say his contribution is net-positive but some of his work causes problems, especially when it comes to config files, shell scripting etc., so everything that is not directly caught by a linter or spell-checker.<p>His typo rate is quite high. I suspect an undiagnosed dyslexia.<p>Mistakes are often caught very late, mostly in staging, making it cumbersome. It led to a few production outages.<p>We have code reviews, a solid test suite etc. but typos are slipping through - once you make them, it&#x27;s just harder for others to catch them.<p>I feel bad for him because it already led to a blame game within the team, with some asking how one can be so sloppy. I don&#x27;t suspect sloppiness because he is otherwise thorough. On the other hand, it escalated because the subject is very touchy with him.<p>I suspect he is weirdly aware of the problem and in denial at the same time, and therefore extremely defensive.<p>His take is that we should increase test coverage. It is part of the answer. However, once he&#x27;s involved in writing the tests, the problem is shifted to writing correct tests.<p>What I&#x27;m thinking about:<p>- engineer the problem away: adjust our tooling and config mechanisms, less strings in our configs, less dynamically-typed scripting etc.<p>- asking him to let AI review his code specifically for potential typos<p>- increasing test coverage, with other people than him writing the tests<p>What I am not considering:<p>- Telling him I suspect he has dyslexia. I&#x27;m not a doctor.<p>I&#x27;m trying to broaden my horizon on this issue, maybe I am missing something. What would you do?