What are some options for future proofing your application? -
I am still trying to reduce the effect of the future on written application. I am trying to avoid any 3rd party products, and even avoid operating system specific calls. Can someone recommend other methods of proof of future? This idea will not have to re-write the key parts in 10 or 20 years, and only maintenance (bug fix) will have to be done anytime.
If you want your program to be running for the period of time (on the modern OS) If so, you probably have to write it only in pure ANSI C (or C ++). There is a possibility of some type of tweaking for some in some more years - and no one knows what will happen in the next 10-20 years.
He said, here is a few tips for reducing these types of problems:
- Avoid odd dependencies if you are going to depend on some libraries , Then make sure that it very is well established (and thus there is a possibility of surviving at least 5 in 10-20 years), or at least open-source if you If needed, you can cut it yourself.
- Avoid OS-specific calls. It will be a balance work with 1. You can use a cover library or what-you can do - but there will be an opportunity for compatibility problems on that front.
- All documents are fact, no matter how hard you try, this program will require compatibility fixes and bug fixes, and will probably also include additional features. That's why 15 years later poor maintenance programmers make life easier. :)
Comments
Post a Comment