如何激励团队致力于遗留产品
我们是一个致力于遗留代码的团队，这些代码相当古老，并且是用最初编程时代的语言编写的。由于团队成员接受了最新技术的培训，现在又开始处理遗留代码，他们并不高兴。如何激励他们也使用遗留代码？
We are a team working on legacy code which is pretty old and written in languages of initial programming days. As the team members are trained in latest technology and are now put to work on legacy code, they are not happy. How to motivate them to work in legacy code also?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（11）
派您的团队去见用户并观看他们使用软件。他们应该找出用户使用该软件时遇到的最严重的问题是什么。
了解用户使工作更加真实 - 您的团队会知道添加新功能或消除一些错误将对某些真实的人有所帮助。这应该会激励程序员完成无聊的工作。
Send your team to meet users and watch them use software. They should find out what are most critical problems users have with that software.
Getting to know users makes work more real - your team will know that adding new functionality or eliminating some bugs will help some real person. That should motivate programmers to get boring job done.
仅靠现金并不能让开发商高兴。你应该为他们提供良好的环境，以便他们能够专注于他们的工作。
另一件事是，没有任何技术是不好的、遗留的或较旧的。问题是，如果你的公司需要维护它，那么你就必须让它继续下去。但保留设计、编码、测试、代码审查、交互式会话等的所有标准。
此外，您还可以激励他们将遗留代码转换到某些新平台，以获得更好的性能和可维护性。我认为每家公司都会这样做，因为他们想与其他市场产品竞争。
还为他们提供一些很酷的课程，介绍您公司中使用但他们不知道或不使用的其他技术。让他们深入了解事情，给予他们适当的时间和支持来解决问题。主要目标是按时交付，减少返工和错误。
为他们的工作提供一些奖励，让他们对工作感到满意。
谢谢。
Only cash can not make the developers happy. You should provide them good environment so that they can pay attention to their work.
Another thing is no technology is bad OR legacy OR older. Thing is if your company needs to maintain it, then you must keep it going. But keep all standards for designing, coding, testing, code review, interactive sessions etc..
Also you can motivate them to convert your legacy code to some new platform for better performance and maintainability. Every company does that even once i think, because they want to compete with other market products.
Also provide them some cool sessions for other technologies which are used in your company but they don't know or use. Let them be deeply in the things, give them proper time and support for problem solving. Main goal is to deliver on time with less rework and bugs.
Provide some rewards towards their work and keep them happy about their work.
thanks.
我真的很喜欢“派你的团队去见用户并观察他们使用软件”
如果我必须激励我的团队，我真的会要求我的开发人员访问使用情况并了解用户对产品的满意度。
我真的很想接受挑战，研究如何让它比现有的更好。
i really like "Send your team to meet users and watch them using software"
If i have to motivate my team, I will really ask my developer to visit the use and find out how much user is happy with the product.
I will really like to take challenge on how we can make it more better then what exist.
您是否有在可预见的将来淘汰遗留代码的空间？如果是这样，“我们只需要继续这样做，直到……”可能会让药丸变得更甜。
团队成员是否对编写遗留代码的语言/环境有经验？如果不是，可能只是不愿意做一些他们不知道如何操作的事情。可能需要安排一些时间让他们至少获得短暂的熟悉感。只要它与最新技术没有太大的范式转变，它应该不会那么难吧？
Do you have some scope for retiring the legacy code in the foreseeable future? If so, "we only need to keep this going until..." might sweeten the pill.
Are the team members experienced in the languages/environments which the legacy code is written in? If not, it might be simple reluctance to do something that they don't know how to operate. Possibly scheduling in some time for them to gain at least a passing familiarity might be in order; provided it's not too much of a paradigm shift from latest technology, it shouldn't be all that hard?
团队成员是否只允许在遗留代码团队中工作，或者他们的时间可以分配在不同的项目之间吗？我认为没有人会愿意每周花 40 个小时进行 FORTRAN 调试。但是，如果您必须花几个小时处理遗留代码，并且知道白天可以休息一下来处理您真正喜欢的事情，那么痛苦就会减轻一些。
我将重申之前所说的，确保团队成员在投入旧技术之前有时间学习并获得旧技术的经验。努力让训练也变得有趣。我们的遗留代码培训被设置为一场竞赛，看看谁能针对有趣的问题提出最快/最短/最完整等的解决方案，而不必只关注我们要处理的代码。实际上，即使您没有时间进行培训，这也可以应用于团队的计划。在手头的任务中添加一点竞争，或者留出一点时间来进行具有挑战性和竞争性的副项目。
Are the team members only allowed to work on the legacy code team or can their time be split between different projects? I don't think anyone is going to be happy about spending a 40 hour week on FORTRAN debugging. But if you have to spend a few hours on the legacy code knowing that you can take breaks during the day to work on something you actually enjoy it's a little less painful.
And I'll reiterate what was said before about making sure the team members have time to learn and gain experience with the old technologies before throwing them in there. Try to make the training enjoyable too. Our legacy code training was set up as a competition to see who could come up with the fastest/shortest/most complete/etc solution to interesting problems rather than having to look exclusively at the code we were to be working on. Really, that could be applied to the team's plan even if you don't have time set aside for training. Add a little competition to the task at hand or allow a little bit of time for challenging and competitive side projects.
他们如何因开发这些遗留产品而获得奖励？你知道他们的动机是什么吗？有些人可能更喜欢及时的认可和赞扬，而另一些人可能希望得到现金或理解这不一定是他们最初接受这份工作时所希望的。我很想建议举行一对一的会议，看看他们希望什么能让他们更快乐。是不是钱多了？休息时间更灵活？传统技术培训？肯定他们在这些古老的系统上做得很好，因为最初的编程日子让我想起大型机和其他非常古老的工具，人们可能会想，“这真的能运行多久？”
How are they getting rewarded for working on these legacy products? Do you know what motivates them? Some people may prefer timely recognition and praise while others may expect cash or understanding that this isn't necessarily what they signed up for when they initially took the job. I'd be tempted to suggest having 1:1 meetings to see what would they like that would make them happier. Is it more money? More flexibility in time off? Training in the legacy technologies? Affirmation that they are doing good work on these ancient systems, as the initial programming days makes me think of mainframes and other really old tools that one may wonder, "How much longer will this run really?"
现金不是答案。免费食物、软饮料等等，这只能缓解遗留代码工作的苦差事。尝试改变他们的观点怎么样？
“任何人都可以使用现代代码来完成出色的工作，这些代码有一个内置重构功能的优秀 IDE，只需 Google 搜索一下即可获得大量资源，但我们很少有人感到自豪，我们这群兄弟，我们足以用古老的过程语言做到这一点我们将驯服这些可怕的乱七八糟的代码，并在背后用一只手完成它，并创建流程和工具，以确保下一个可怜的混蛋不会遇到这么糟糕的事情。”
Cash isn't the answer. Free food, soft drinks, whatever, that only goes so far at alleviating the drudgery of legacy code work. What about trying to change their perspective?
"Anyone can do good work with modern code that has a nice IDE with refactoring built in, a ton of resources just one Google search away, but we proud few, we band of brothers, we are good enough to do this with ancient procedural languages. We'll tame this awful mess of code and do it with one hand behind our backs and create processes and tools to make sure the next poor bastards won't have it so bad."
我想说，吸引开发人员对遗留编码最积极的情感的最简单方法是以某种方式将旧的编码变成新的。
举行一两次会议来确定遗留代码的作用，然后了解在新架构上重新执行它需要做什么。 “新架构”部分是关键，因为 9/10 的情况下，令人害怕的是架构（意大利面条代码、预标准约定等）。
如果您的重写估算无法获得批准，那么至少制定一个计划，将遗留代码的重构纳入日常维护中。至少，你的开发人员会觉得他们正在努力做一些事情，而且是一些新的事情，而不是只是破坏没有人愿意记住的旧腐朽的东西。
只是我的2美分。
I would say the simplest way to attract the most positive emotion from developers to legacy coding would be to make the old new in some way.
Have a session or two to identify what it is that the legacy code does, and then get an idea of what it would take to do it anew on a new architecture. The "new architecture" part is key, because 9/10 times, it's the architecture that is dreaded (spaghetti code, pre-standard conventions, etc...).
If you can't get your re-write estimates approved, then at least work out a plan to get your refactoring of legacy code into the daily maintenance. At the very least your developers will feel as though they are working towards something, and something new at that, instead of just monkey-wrenching the old decay that no one wants to even remember.
Just my 2¢.
例如，您可以尝试在测试方面做一些奇特的事情。尝试模拟框架等。
还要尝试强调，如果您想成为一名可靠的程序员，那么处理遗留代码是一种很好的体验，因为每种技术最终都会成为遗产。
You can for example try to do fancy things on the testing side. Try out mocking frameworks etc.
Try also emphasize that handling legacy code is a good experience if you want to become a solid programmer, since every technology becomes eventually legacy.
额外现金？ :) 不知道其他任何事情...
即使它是新技术遗留代码，处理此类代码并不总是令人愉快，所以关于“初始技术”...我想唯一的激励因素是发现编程是如何进行的这些日子...
Extra cash? :) Don't know anything else...
Even if it's new technologies legacy code it's not always a pleasure to work on such code, so on "initial technologies"... i guess the only motivating thing is to discover how programming was these days...
考虑到免费提供的资源、IDE、专业知识、框架等的数量，花在激励团队、学习遗留代码并半心半意地修复它所需的时间可以很容易地用于在新平台上构建相同的东西，好消息是，您已经拥有了系统，您只需要在新平台中满足相同的行为，而不是我们必须为某些我们不知道其行为和用户体验的产品构建新的东西。
The amount of Time required in spending motivating the team and learning the legacy code and fixing it half heartedly can easily be used to build the same stuff in new platform , given the amount of resources , IDEs , expertise , frameworks etc available for free, the Good news you have the system in place you just need to meet the same behavior in new platform unlike we have to build something new for some product whose behavior and user experience we dont know .