Building Slow Development Systems (On Purpose)

Hey guys,
I did a post yesterday about a conversation I had regarding "encouraging" developers to write tighter code by intentionally hampering development system capabilities. Specifically, using a very small buffer cache which basically turns all the lio's into pio's, thus (theoretically) encouraging developers to minimize lio's. There have been some good comments already but I thought I would poll you guys.
My initial reaction to the idea was that it was just plain crazy. But for some reason, over the last several days, the idea keeps popping up to the top of the stack in my brain. I fully expect to get flamed a bit, but I'll try not to take it personal. I would request that you give it an hour or two to roll around in your brain before you respond. It is a bit counter intuitive and it is certainly counter to what I've always thought of as the "ideal", which is DEV being an exact duplicate of PROD in every respect (I'm still waiting to see my first one of those by the way).
Note that my conversation was about DEV environments, not QA environments. QA environments should, IMHO, always be as close to PROD as possible (same stats, etc...) But maybe there is an argument for "encouraging" developers to minimize lio's. 

  Feel free to flame away.

Kerry Osborne
Enkitec
blog: kerryosborne.oracle-guy.com






--
http://www.freelists.org/webpage/oracle-l

Other related posts: