各类软件马斯洛需求层次分析_马斯洛的软件开发需求层次

各类软件马斯洛需求层次分析

I've been experimenting with my diet a little and considering a Paleo diet. What an amazing and selfish thing, though, for me to even consider or be able to change my diet in a fundamental way. Only someone who isn't worried about their next meal could explore that aspect of their lives without fear or concern.

我一直在试验饮食，并考虑古饮食。但是，对于我来说，甚至可以根本地考虑或能够改变自己的饮食，这真是一件了不起而自私的事情。只有不担心下一顿饭的人才可以探索生活中的这一方面而无所畏惧。

One doesn't get to have certain luxuries until other more basic needs are met. Here's an interpretation of Maslow's hierarchy of needs:

在满足其他更基本的需求之前，人们不会奢侈一些。这是对Maslow需求层次结构的解释：

I was talking to a customer a while back and one gentleman was deeply concerned about coding style, curly brace location, best practices in interface design and a bunch of important but arguably not urgent thing. Their unit testing wasn't well organized, their deployment was manual, their build was only marginally verifiable.

不久前，我正与客户交谈，一位先生深深地担心代码风格，花括号位置，界面设计最佳实践以及许多重要但可以说不是紧迫的事情。他们的单元测试没有很好的组织，他们的部署是手动的，他们的构建只能勉强验证。

Stated differently, he was asking questions like "Am I eating enough veggies rich with Vitamin A" without asking the more fundamental "Do I have food for tonight?"

换句话说，他在问诸如“我是否吃了足够的富含维生素A的蔬菜”之类的问题时，却没有问到更基本的“我今晚有食物吗？”之类的问题。

Now, apply the Hierarchy of Needs to Software and Technical Debt. Here's one, with my thanks to Phil Haack, Jon Galloway, Jonathan Wanagel, Paul Stovell for their help in brainstorming.

现在，将需求层次结构应用于软件和技术债务。在此，我要感谢Phil Haack ， Jon Galloway ， Jonathan Wanagel ， Paul Stovell的集思广益。

吹牛的权利-让您感到骄傲的改变 (Bragging Rights - Change you are proud of)

Paul put it well when he said to me: "The top of Maslow's pyramid is self-actualization...in some ways I think we like to achieve self-actualization through our code, [such that] in years to come, maintenance programmers will stumble upon this architecture and exclaim, 'Wow, Scott was here.'"

保罗对我说的很好：“马斯洛金字塔的顶端是自我实现……在某些方面，我认为我们喜欢通过我们的代码来实现自我实现，例如，在未来的几年中，维护程序员会偶然发现这种架构，并惊呼：“哇，斯科特在这里。”

Are you writing software or crafting software? When does your craft become art?

您是在编写软件还是在制作软件？ 您的手艺何时成为艺术品？

This is a noble and certainly attractive goal, but is one that should be attempted only after the basic needs are met.

这是一个崇高的目标，当然也是很有吸引力的目标，但是只有在满足基本需求之后才应该尝试这一目标。

可重构-改变无惧 (Refactorable - Change without fear)

Is your code/system easy able to be refactored? Can you rearrange it without fear? Does it follow all the conventions and use the appropriate idioms of your chosen language? Do you have automated unit tests?

您的代码/系统易于重构吗？您可以不用担心重新排列它吗？它是否遵循所有约定并使用您选择的语言的适当习语？您有自动化的单元测试吗？

可维护-通过验证进行更改 (Maintainable - Change with verification)

Is it able to change at all? Are bugs fixable? When you make a change is that change verifiably correct? Any tests at all?

它可以改变吗？错误可以修复吗？当您进行更改时，该更改是否可以证明是正确的？有测试吗？

可构建和部署-生产变更 (Buildable & Deployable - Change in production)

Can you deploy your system as easily as you can build it? Continuous Integration is effectively a must in today's software systems, but moving up in importance is Continuous Deployment - with rollback!

您能否像构建它一样轻松地部署系统？在当今的软件系统中，持续集成实际上是必须的，但重要的是持续部署-具有回滚功能！

可修改-更改 (Revisable - Change)

Is your system in source control with a clear workflow that governs contributions? Can you revert changes, stamp official changes, branch and merge? What? You're using zip files? Sorry, friend, you don't get to talk about class design or move around UML diagrams until you're using source control.

您的系统是否在源代码控制中具有清晰的工作流来管理贡献？您可以还原更改，加盖正式更改，分支并合并吗？什么？您使用的是zip文件吗？抱歉，朋友，除非您使用源代码控制，否则您不可以谈论类设计或在UML图周围移动。

领导的重要性 (The importance of leadership)

This underscores the importance of a strong and appropriately self-aware leader. Creating art is the fun stuff but it isn't always what needs to be done to move the project forward. The tech lead needs to recognize the right time to be an artist and the right time to invest in strong foundational processes.

这凸显了强大且具有适当自我意识的领导者的重要性。创造艺术是一件有趣的事情，但并非总是需要做些什么才能使项目向前发展。技术负责人需要认识到合适的时间成为艺术家，以及正确的时间投资于坚实的基础流程。

Are we eating enough leafy greens as a team? Let's start with "are we eating tonight?" and work from there.

我们作为一个团队吃足够多的绿叶蔬菜吗？让我们从“今晚吃饭吗？”开始从那里工作。

关于斯科特 (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员工。他是一位失败的单口相声漫画家，一个玉米种植者和一本书的作者。