Story: Problem? What problem?

by admin on November 17, 2009

Andy has a consulting horror story …

We were doing a 2 day ‘architectural overview’ for a potential client – they were suffering performance issues as their production site started scaling, and they wanted a hand investigating it. Whilst digging around, my colleague noticed that one of their ASPs didn’t compile. He suggested a potential fix, and asked how they would test and promote the change. “Ah”, said client dev that he was working with – who promptly logged on to the production box, found the non-compiling production code, edited the file in place, and bounced the server …

Share with the group:
  • Digg
  • del.icio.us
  • Facebook
  • DZone
  • LinkedIn
  • Slashdot
  • StumbleUpon

Related posts:

  1. Story: Wolf++ fixes the Deployment Process The last of the top three stories for the...
  2. Story: Rolling your own Thanks to Daniel Spiewak for this great story from...
  3. Story: Daniel’s Continuous Integration System Daniel Spiewak gave us this great story for the...
  4. Story: Fan or Die David Goh contributed this beauty: Back in 1994 or...
  5. Build Pattern: Green-lit build Continuous Integration should be a highway, not a parking...

Related posts brought to you by Yet Another Related Posts Plugin.

blog comments powered by Disqus

Previous post: Drunken Build Monkeys, and Agile Systems Administration

Next post: Selenium and The Dialog of Doom