No. I did a full rewrite opf a complex system once. It was %100 a good idea and the new version was much better. You just need good tests and a clear specification.
as long as you have a sponsor... And then? How long will the 'new' system last? Does anybody tell their customers 'this is unmaintainable throw-away software - you need a new one after 5 years'
All depends if you can maintain it. If you have bought a car and bring it to a bicycle repair shop for maintenance, yes, you need to have something new after 5 years. But if you have the tools and experience to maintain it (bring it to the car service shop), software can last a long time.
![[Live] : ONE 169 วันนี้!! "อนาโตลี vs อูมาร์"](http://i.ytimg.com/vi/IK3YZVWuFJg/mqdefault.jpg)
![[Full] 4 ต่อ 4 Celebrity EP.922 | 10 พ.ย. 67 | one31](http://i.ytimg.com/vi/zmV5HRIxIBI/mqdefault.jpg)
![ไลฟ์สุ่ม iPhone 295 บาท... โกงมั้ย?[ โกงมั้ยครับ ep.97 ] | DOM](http://i.ytimg.com/vi/gdstHEE4UUE/mqdefault.jpg)
I was just about to rewrite an app instead of maintaining a legacy ! Let's watch this
A rewrite may end up looking exactly like the original because of familiarity tendency and organizational constraints/modes of communication.
No. I did a full rewrite opf a complex system once. It was %100 a good idea and the new version was much better. You just need good tests and a clear specification.
Well, whole modern IT ecosystem is a blocks of black boxes. All PaaS, Saas, IaaS solutions are black boxes. This is the Zeitgeist.
as long as you have a sponsor...
And then? How long will the 'new' system last?
Does anybody tell their customers 'this is unmaintainable throw-away software - you need a new one after 5 years'
All depends if you can maintain it. If you have bought a car and bring it to a bicycle repair shop for maintenance, yes, you need to have something new after 5 years. But if you have the tools and experience to maintain it (bring it to the car service shop), software can last a long time.