[翻译]架构师应该知道的97件事_03关键问题可能不是出在技术上

03 Chances Are, Your Biggest Problem Isn't Technical
关键问题可能不是出在技术上

Mark Ramm
马克•兰姆

RIGHT NOW SOMEONE'S RUNNING a failing project to build a payroll system. Probably more than one someone.

简单的项目（比如工资管理系统）也会翻船，这恐怕不是个别情况吧。

Why? Was it because they chose Ruby over Java, or Python over Smalltalk? Or because they decided to use Postgres rather than Oracle? Or did they choose Windows when they should have chosen Linux? We've all seen technology take the fall for failed projects. But what are the chances that the problem was really so difficult to solve that Java wasn't up the the task?

为什么？难道是因为选错了技术吗？是因为我们选择了Ruby而非Java，选择了Python而非Smalltalk？或者选择了Postgres而非Oracle？还是因为本该用Linux时，错选了Windows？一旦项目失败，技术往往沦为替罪羊。但是有多少问题真的是Java无法胜任的呢，这种可能性有多大？

Most projects are built by people, and those people are the foundation for success and failure. So, it pays to think about what it takes to help make those people successful.

多数项目是由人完成的，人才是项目成败与否的基本因素。因此很有必要花时间来思考，如何帮助团队成员获得成功。

Equally, there's a good chance that there's someone who you think is "just not doing it right" and is undermining the project. In these cases, the technology you need to solve your problem is very old and well established indeed; in fact, it's possibly the most important technical innovation in the history of humanity. What you need is a conversation.

如果团队里有人工作方式不正确，拖项目的后腿怎么办？有一项非常古老完善的技术可以帮助你解决问题。它称得上是人类有史以来最重要的技术创新，那就是沟通。

Mere familiarity with the conversation as a technology isn't enough. Learning to treat people with respect, and learning give them the benefit of the doubt, is one of the core skills that turn a smart architect into an effective one.

但仅仅了解沟通的用途还不够。学会尊重他人，给予团队成员充分的信任，是聪明的架构师获得成功必须掌握的核心技能。

There's lots more to it than this, but a couple of small tips can significantly increase your conversational effectiveness:

沟通技巧一言难尽，但是有几条经验可以显著改善效果：

•    Approach these events as conversations—not as confrontations.
If you assume the best about people and treat this situation as an opportunity to ask questions, you definitely learn more, and are less likely to put people on the defensive.

•    不要把对话当成对抗
如果你能看到他人的优点，并把沟通视为请教问题的机会，就必然有所收获，同时也避免引起对方的戒备之心。

•    Approach these conversations only after you've got your attitude right.
If you're angry, frustrated, annoyed, or otherwise flustered, it's very likely that the other person will interpret your nonverbals as an indication that you're on the attack.

•    不要带情绪与人沟通
当你处于愤怒、沮丧、烦恼，或者慌张的情绪中时，对方很可能会误认为你的举动不怀好意。

•    Use these as opportunities to set mutually agreed-upon goals.
Instead of telling a developer that they need to be quiet in meetings because they never let anybody speak, ask if they can help you increase other people's participation. Explain that some people are more introverted and need longer silences before they enter into a conversation, and ask the developer to help you out by waiting five seconds before jumping in.

•    尝试通过沟通设定共同的目标
有些人在会议中喋喋不休，影响其他人发言。与其命令他闭嘴，不如请他协助你提高其他人的参与度。告诉他有些同事比较内向，发言前需要安静地理清思路。请他在每次发言之前稍做等待，让同事有机会表达意见。

If you start with a shared purpose, treat people "problems" as an opportunity to learn, and manage your own emotions, you'll not only become more effective, you'll also discover that you learn something every time.

如果你能首先与同事达成一致的目标，把处理冲突和矛盾的过程视为学习的机会，控制住自己的情绪，那么每次沟通都会让你有所收获，并且做得更好。

About The Author

Mark Ramm is BDFL for TurboGears 2, a python enthusiast, and a generally crazy dude. He's done nearly every job imaginable from software architect to network administrator to lobster-trap thrower and biker-bar cleaner. He is passionate about making tools that help professional and amateur programmers more productive.

马克•兰姆是TurboGears 2开源项目领头人。这位老兄热爱Python，喜欢挑战，他干过各种奇怪的工作，除了做过软件架构师和网络管理员，他还捕过龙虾，在摩托党酒吧当过清洁工。他目前致力于开发软件工具，用来帮助专业程序员和业余程序员的更好地开展工作。

转载于:https://www.cnblogs.com/seanxu/archive/2009/07/26/1531420.html