Comments on: Myth of the isolated production fix http://lostechies.com/jimmybogard/2007/10/18/myth-of-the-isolated-production-fix/ Strong opinions, weakly held Sat, 25 May 2013 16:53:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Jimmy Bogard http://lostechies.com/jimmybogard/2007/10/18/myth-of-the-isolated-production-fix/#comment-10 Jimmy Bogard Fri, 19 Oct 2007 13:28:43 +0000 /blogs/jimmy_bogard/archive/2007/10/18/myth-of-the-isolated-production-fix.aspx#comment-10 That's exactly why I'd rather push config into code, and if not that, have tests for my config files. FDD, I like that. That’s exactly why I’d rather push config into code, and if not that, have tests for my config files. FDD, I like that.

]]> By: Joe Ocampo http://lostechies.com/jimmybogard/2007/10/18/myth-of-the-isolated-production-fix/#comment-9 Joe Ocampo Thu, 18 Oct 2007 15:00:44 +0000 /blogs/jimmy_bogard/archive/2007/10/18/myth-of-the-isolated-production-fix.aspx#comment-9 Think about it. What do you do if you don't practice TDD, you have know idea how the changes made to code impact the production architecture. In essence you are practicing FDD (Faith Driven Development). You are praying that nothing goes wrong when you change code. But wait a smart developer on your team has minimized risk by decoupling configuration out of code and into an XML file. What genius! Now my risk has been mitigated by the fact that this configuration file is certainly isolated to this one component and can't possibly have any side effects. Lets just make this simple change in production. 16 hours later. Dev: "Yeah we should have tested that before we deployed to production." Build Guy: "But I thought you said it didn't affect anything else." Dev: "I didn't know they changed the code to aslo interact with this system as well. When I code it, it worked, it's not my fault the didn't update the documentation." Ahhh the memories of lessons learned...How I don't miss them. Think about it. What do you do if you don’t practice TDD, you have know idea how the changes made to code impact the production architecture.

In essence you are practicing FDD (Faith Driven Development). You are praying that nothing goes wrong when you change code. But wait a smart developer on your team has minimized risk by decoupling configuration out of code and into an XML file. What genius! Now my risk has been mitigated by the fact that this configuration file is certainly isolated to this one component and can’t possibly have any side effects. Lets just make this simple change in production. 16 hours later.

Dev: “Yeah we should have tested that before we
deployed to production.”

Build Guy: “But I thought you said it didn’t affect anything else.”

Dev: “I didn’t know they changed the code to aslo interact with this system as well. When I code it, it worked, it’s not my fault the didn’t update the documentation.”

Ahhh the memories of lessons learned…How I don’t miss them.

]]>