Comments on: IT Management Podcast #30 – That code don’t write itself, chuckle-heads http://www.redmonk.com/cote/2008/12/22/itmanagement030/ One foot in the muck, the other in utopia Thu, 24 May 2012 14:45:32 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Ashish http://www.redmonk.com/cote/2008/12/22/itmanagement030/comment-page-1/#comment-275323 Ashish Wed, 24 Dec 2008 14:32:49 +0000 http://www.redmonk.com/cote/2008/12/22/itmanagement030/#comment-275323 Thanks for the mention, Cote. It was a pleasure meeting you too. Merry Christmas! Thanks for the mention, Cote. It was a pleasure meeting you too. Merry Christmas!

]]> By: The Madstop » Puppet on the IT Management Podcast http://www.redmonk.com/cote/2008/12/22/itmanagement030/comment-page-1/#comment-274622 The Madstop » Puppet on the IT Management Podcast Mon, 22 Dec 2008 15:50:06 +0000 http://www.redmonk.com/cote/2008/12/22/itmanagement030/#comment-274622 [...] was a guest on last week’s IT Management Podcast again last week, and we ended up talking a lot about Puppet and the difficulties in running an open [...] [...] was a guest on last week’s IT Management Podcast again last week, and we ended up talking a lot about Puppet and the difficulties in running an open [...]

]]> By: cote http://www.redmonk.com/cote/2008/12/22/itmanagement030/comment-page-1/#comment-274676 cote Mon, 22 Dec 2008 13:55:04 +0000 http://www.redmonk.com/cote/2008/12/22/itmanagement030/#comment-274676 jeffg: thanks for the correction! jeffg: thanks for the correction!

]]> By: jeffg http://www.redmonk.com/cote/2008/12/22/itmanagement030/comment-page-1/#comment-274650 jeffg Mon, 22 Dec 2008 12:32:03 +0000 http://www.redmonk.com/cote/2008/12/22/itmanagement030/#comment-274650 A factual correction: the <a href="http://blogs.opennms.org/?p=472" rel="nofollow">situation</a> with the company in Sweden that John talks about around 10:30 is inaccurately described. Far from telling the user to "shit in their hat", we agreed to sell them a half-day of remote consulting. Our estimate would have been pretty spot-on if not for the coincidental firewall change in the customer's environment that led to thousands of SNMP traps per second hitting their openNMS installation, which was not sized to process events at that rate. As so often happens, the customer didn't make the connection ("I haven't changed anything else, really!"), but we worked the incident through to a resolution that left the customer very happy with the experience. Should we have insisted that the customer buy annual support? In hindsight, probably so. We hope that they'll buy a contract anyway, and take advantage of the <a href="http://blogs.opennms.org/?p=467" rel="nofollow">COVER</a> promotion to get a free seat of training bundled with it. Even if this client doesn't turn into a renewable revenue source, we're still happy to know that openNMS is allowing their sysadmins to get some sleep during the holiday shopping season. A factual correction: the situation with the company in Sweden that John talks about around 10:30 is inaccurately described. Far from telling the user to "shit in their hat", we agreed to sell them a half-day of remote consulting. Our estimate would have been pretty spot-on if not for the coincidental firewall change in the customer's environment that led to thousands of SNMP traps per second hitting their openNMS installation, which was not sized to process events at that rate. As so often happens, the customer didn't make the connection ("I haven't changed anything else, really!"), but we worked the incident through to a resolution that left the customer very happy with the experience.

Should we have insisted that the customer buy annual support? In hindsight, probably so. We hope that they'll buy a contract anyway, and take advantage of the COVER promotion to get a free seat of training bundled with it. Even if this client doesn't turn into a renewable revenue source, we're still happy to know that openNMS is allowing their sysadmins to get some sleep during the holiday shopping season.

]]>