http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Finally, it seems that I'm not the only one having this 'problem'. Building the database and core functionality to get this working becomes unfortunately a common practice. Mostly, because managers start thinking what they want when development is ready... So I'm using pre-production environments. Don't call them a test or beta environment, because managers don't want to test. They only want to see it work.. The main problem is that managers stop think after the specified the GUI. The visible part of the application. They often forget that the application requires a backend application dealing to make it work. http://ayende.com/3134/what-ready-for-production-means#comment3http://ayende.com/3134/what-ready-for-production-means#comment3Tue, 12 Feb 2008 17:07:25 GMTYes. Proper error handling and logging ALL functions will account for the remaining 80% of the time. One these are done, when things blow up you spend 0% of your time wondering what went wrong. Thinking that your boss/client/yourself is going to go back and do a proper retrofit is well, wishful thinking. Your boss already thinks the app is done since - well it's in PRODUCTION! http://ayende.com/3134/what-ready-for-production-means#comment2http://ayende.com/3134/what-ready-for-production-means#comment2Sun, 10 Feb 2008 17:56:21 GMTIn my experience the problem with this approach is trying to convince people who see and use it that it really isn't ready for prime-time. Personally I help address that by intentionally keeping the UI unpolished until it's almost ready but the temptation is always there to make it look good. [)amien http://ayende.com/3134/what-ready-for-production-means#comment1http://ayende.com/3134/what-ready-for-production-means#comment1Sat, 09 Feb 2008 17:02:25 GMT