Cezar Lamann wrote: and that they do everything inside application code, I code to the business and not to odd-ball extremes that some person with no objective data came up with. Using stored procedures can be much more effective that at some tasks then attempting to do it in code. I have seen systems that attempted to do the work only in the application and their performance was orders of magnitude larger than it could have been. I have also seen cases where because there was no clean separation of data access (because after all it should be right were it is needed right?) that a conversion to a different database took years (actual years) to do. And that conversion was driven by real business needs and not just because the newest CTO decided they wanted something different.

My group keeps comprehensive backups due to our products' extraordinary life span, 10 years or more. We limit support to more recent versions. Archived source code is generally available to the team, although some older items take a minor bit of effort to retrieve. We have one application, an in-house debugging tool, that has been in active development since 2000. Software Zen: delete this;