软件使用寿命：您从多久开始从零开始？ [英] Lifespan of Software: How often do you expect to do start from scratch?
问题描述
毕竟，我的一些客户有笨重的大型机已经有二十年了，他们是如此根深蒂固，他们可能会生活永远。
当平台变得老旧以至于我们的技能不好（我们是承包商）时，我个人倾向于开始谈论严重的重构，并且保持这个项目的效率不高。我正在考虑ASP Classic。这可能是5到8年的窗口，甚至不需要重写。
当然，我也看到项目引发了大量的技术性债务，因为有些人经常陷入利益相关者，或者开发人员不知道如何计划变更。或者这个项目是在一个没有扩展的弱平台上开始的。 可以减少生命周期。
也许这些项目是那些倾向于生活3年的项目。或更少。
最后一个想法：有些研究证明，维护旧代码比编写新代码便宜得多，我相信。重写大型系统总是比看起来更困难和更昂贵。
这些都是阴谋的，表明开发人员倾向于重写太早，而且可能天真？我想是的，我可以看到这是一个容易的错误。
你在这里有什么经历？ / strong>
我正在开发的团队已经开发了同样的Web应用程序6年，没有结束了。在那段时间里，它从经典ASP到ASP.NET 1.1到ASP.NET 2.0，所以各种模块都经历了渐进的重写，但是从来没有像是从零开始重写。有时候有人会说，如果我们可以重新开始，会有多好，但是我们有6万多个用户：没有办法等待12到18个月的时间，而他们更新的功能或功能坐在
我只有两次完成重写的机会。在这两种情况下，我们有时间和买入的原因是因为我们有一小部分客户使用已经稳定的版本。当我们和新产品一起去的时候，他们都认为它比旧系统好，但是很少有人买了它，因为他们已经对自己的产品感到满意了。对于程序员来说，这是一件很有趣的事情，但最终这是一笔损失。
所以，从个人经验来看，你从头开始的事情每3年可能不会被许多人使用。当您有广泛使用的应用程序或服务，特别是在企业环境中时，很难进行逐步升级，更不用说重写。
I've heard people say that the average lifespan of software is about 3 years, but that seems shockingly low to me. I don't buy it.
After all, some of my clients have lumbering mainframes that have been around for 20 years, and they're so entrenched that they might live forever.
I personally tend to start talking about severe refactoring when the platform gets so old that it's bad for our skills (we are contractors) and otherwise inefficient to keep maintaining the project. I'm thinking about ASP Classic here. That can be a 5 to 8 year window, and it doesn't even need to be a rewrite.
Of course, I have also seen projects that incurred a lot of technical debt because someone caved to stakeholders too often or a dev didn't know how to plan for change. Or the project was started on a weak platform that didn't scale well. That radically reduces the lifespan.
Maybe those projects are the ones that tend to live 3 years. Or less.
One last thought: Some studies have proven that it's cheaper to maintain old code than to write new, and I believe it. Rewriting large systems is always way harder and more expensive than it looks.
Does all of this conspire to indicate that developers tend to re-write too early, and perhaps naively? I'm thinking yes, and I can see how that's an easy mistake to make.
What are your experiences here?
The team that I'm working on has been developing the same web application for 6 years, and there's no end in sight. In that time, it's gone from Classic ASP to ASP.NET 1.1 to ASP.NET 2.0, so various modules have undergone incremental rewrites, but never anything like a from-scratch rewrite. Every so often somebody will say how nice it would be if we could start over, but we have 60,000+ users: there's no way they're going to wait the 12 to 18 months it would take while their updated functionality or features sit on a shelf.
I've only had the chance to do a ground-up rewrite twice. In both cases, the reason we had time and buy-in to do so was because we had a rather small group of customers using an already stable version. When we went to them with the new product, they all agreed that it was better than the old system, but very few of them bought it because they were already happy with what they had. It was a lot of fun for the programmers, but ultimately it was a loss for the business.
So, from personal experience, the things that you get to start from scratch every 3 years are likely not used by many people. When you've got a widely used application or service, especially in a corporate environment, it's hard enough to get buy-in to do gradual upgrades, let alone rewrites.
这篇关于软件使用寿命：您从多久开始从零开始？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
