fdd 驱动开发_恐惧驱动的发展-FDD
fdd 驱动开发
I had an interesting chat recently at a conference in the "hallway track." The hallway track is all the great conversations that happen in the hallway between sessions.
我最近在“走廊”的一次会议上进行了有趣的聊天。 走廊是所有会话之间在走廊中进行的所有精彩对话。
What drives your development processes? Are you a TDD house, where your tests drive development? Or, perhaps there's a chief architect who isn't a very nice person. We call this ADD - Asshole Driven Development. However, this chat was about FDD - Fear Driven Development.
是什么驱动您的开发流程？ 您是TDD的房子，您的测试在哪里推动开发？ 或者，也许有一个首席建筑师不是一个很好的人。 我们称此为“ ADD-混蛋驱动开发”。 但是，此聊天是关于FDD-恐惧驱动开发的。
组织恐惧 (Organizational Fear )
Organization fear can have developers worried about making mistakes, breaking the build, or causing bugs that the organization increases focus on making paper, creating excessive process, and effectively standing in the way of writing code.
对组织的恐惧会使开发人员担心犯错，破坏构建或导致错误，从而使组织更加专注于造纸，创建过多的过程并有效地阻碍编写代码的方式。
This "analysis paralysis" slows the entire project down. Every one is so afraid of the process that forward motion stops. There's a great post called "10 ways to lose a team" that covers many negative behaviors that can affect a team. Things like
这种“分析瘫痪”会使整个项目变慢。 每个人都害怕前进的过程，以至于停止前进。 有一篇很棒的文章叫做“失去团队的十种方法”，其中涵盖了许多可能影响团队的负面行为。 像
- Forbidding one-on-one meetings禁止一对一会议
- Don't share information不分享信息
- Implying that everyone can be replaced暗示每个人都可以被替换
- Micromanaging微管理
All of these behaviors increase ambient fear and can cause a cloud of anxiety to loom over the organization.
所有这些行为都会增加周围的恐惧感，并可能导致组织中弥漫着焦虑。
失去工作恐惧 (Losing Your Job Fear)
Other kind of Fear Driven Development is when an organization tries to get developers to stay far too late, work unreasonably hard, by implying that they'll lose their job at the sign of any problems with the project. Threatening jobs will never create a more productive team. It only perpetuates negative feelings and will always lead to people quitting. This also can cause management to believe that heroic effort is a common and acceptable part of the software development. An occasional "work push" is one thing, but if EVERY RELEASE cycle means a heroic effort at the cost of your personal relationships, you've got problems.
恐惧驱动开发的另一种形式是，当组织试图暗示开发人员在项目出现任何问题时将失去工作时，试图使开发人员呆得太久，不合理地工作。 威胁性的工作永远不会创造出更高效率的团队。 它只会使负面情绪永久存在，并总是导致人们戒烟。 这也可能使管理层相信英雄般的努力是软件开发中常见且可以接受的部分。 偶尔的“工作推动”是一回事，但是如果每个发布周期都意味着付出了个人关系的代价就做出了英勇的努力，那么您就会遇到麻烦。
担心更改代码 (Fear of Changing Code)
Another kind of Fear Driven Development is when your development organization (or your entire organization) is afraid of the code. Perhaps the code is older (legacy code) but more likely it's just not fully understood. It mostly works, but folks are afraid that a small change to the code could cost unpredictable side-effects. Fear of bug regressions - a closed/fixed bug coming back to life also stresses developers out.
恐惧驱动开发的另一种形式是，您的开发组织(或您的整个组织)害怕代码。 该代码可能更旧(旧版代码)，但更有可能只是未被完全理解。 它通常可以工作，但是人们担心对代码进行小的更改可能会带来无法预料的副作用。 担心错误回归-封闭/修复的错误复活也使开发人员感到压力。
Can you think of other flavors of Fear Driven Development?
您能想到恐惧驱动开发的其他形式吗？
* Photo by Stacy Brunner, used under Creative Commons
Sponsor: Many thanks to Aspose for sponsoring the blog feed this week! Aspose.Total for .NET has all the APIs you need to create, manipulate and convert Microsoft Office documents and a host of other file formats in your applications. Curious? Start a free trial today.
赞助商：非常感谢Aspose本周赞助了博客提要！ .NET的Aspose.Total具有您在应用程序中创建，处理和转换Microsoft Office文档所需的所有API以及许多其他文件格式。 好奇？ 立即开始免费试用。
关于斯科特 (About Scott)
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
斯科特·汉塞尔曼(Scott Hanselman)是前教授，前金融首席架构师，现在是演讲者，顾问，父亲，糖尿病患者和Microsoft员工。 他是一位失败的单口相声漫画家，一个玉米种植者和一本书的作者。
翻译自: https://www.hanselman.com/blog/fear-driven-development-fdd
fdd 驱动开发