其他驱动的发展
Which
Why More Models?
为什么有更多的模型？
Mental models within an industry, company, or even a person, change constantly. As methodologies mature, we see the long term effects our choices have wrought and can adjust accordingly. As a team or company grows, methodologies that worked well for five people may not work as well for 40 people. If all employees could keep an entire app in their head, we’d need fewer rules and checks and balances on our development, but that is not the case. As a result, we summarize things we notice have been implicit in our work.
一个行业、公司、甚至一个人的心智模式都在不断变化。随着方法论的成熟，我们可以看到我们的选择所带来的长期影响，并可以进行相应的调整。随着一个团队或公司的成长，对5个人有效的方法论可能对40个人就不那么有效了。如果所有的员工都能把整个应用程序记在脑子里，那么我们的开发就需要更少的规则和制衡，但事实并非如此。因此，我们总结了我们注意到的已经隐含在工作中的东西。
When I began as an engineer, TDD taught me to consider my outcomes first and work backwards from the results. As a result, I spent less time writing unnecessary code. I worked towards the results instead of the imagined problems. As my career progressed and I worked on harder problems, Sandi Metz’s Rules forced me to consider the specific code I was writing, instead of writing code with reckless abandon as long as the tests passed. When I became a tech lead, problems became human in nature. I did my best to codify what led to success, and examine what led to failure.
当我开始成为一名工程师时，TDD教会了我首先考虑我的结果，然后从结果往后工作。因此，我花了较少的时间来编写不必要的代码。我努力追求结果，而不是想象中的问题。随着我的职业生涯的发展，我在更难的问题上工作，Sandi Metz的规则迫使我考虑我正在编写的具体代码，而不是不顾一切地写代码，只要测试通过。当我成为一名技术负责人时，问题就变得人性化了。我尽力将导致成功的因素编成法典，并检查导致失败的因素。
So why do we add more models? We add more to transform lessons we’ve learned from unconscio...