>>> What percentage of the HN crowd has developed something that has had (or will have) a 10, 20 or 40 year life span? Did that a lot when I was working at a m

>>> What percentage of the HN crowd has developed something that has had (or will have) a 10, 20 or 40 year life span? Did that a lot when I was working at a major US bank (JP Morgan). All the critical software I worked on was planned for 10-20 years in my mind. Some of the work was upgrading/rewriting ancient things that have been there for 15 years, sometimes mostly untouched. Wrote some blog posts about it. The most remarkable legacy system I have seen : That one was 13 years old, upgraded and half rewritten with bug to bug compatibility, 99% sure it will still be there in 13 years. https://thehftguy.com/2020/07/09/the-most-remarkable-legacy-system-i-have-seen/ https://thehftguy.com/2020/07/09/the-most-remarkable-legacy-... Retired the last Perl software in the bank, rewrote in python and made sure it works on 2.6 and 2.7 and 3.7 to cover the upcoming decade. That software was handling in the order of a trillion dollars per day, wouldn't be surprised if it's still there in 30 years. https://thehftguy.com/2020/06/26/are-banks-still-using-perl-in-2020-the-answer-is-no/ https://thehftguy.com/2020/06/26/are-banks-still-using-perl-...