<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">

<channel>
<title>IT Troubleshooter | Harper Mann</title>
<link>http://weblog.infoworld.com/ittroubleshooter/?source=rss</link>
<description>No big IT problems, just lots of little ones</description>
<dc:language>en-us</dc:language>
<dc:creator>harper&#46;mann&#64;gmail&#46;com</dc:creator>
<dc:date>2008-04-27T16:32:45-08:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.17" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>

<item>
<title>Desperately Seeking Interop 2008 Las Vegas</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2008/04/desperately_see.html?source=rss</link>
<description>
Off to Interop. Energy camp looks pretty interestinghttp://www.energycamp.org/. I&apos;m looking forward to seeing what&apos;s new in green data centers and the rest of the show. I&apos;m also going to visit the Microsoft Management Summit (MMS) which will be interesting for me since I&apos;ve never been to a Microsoft only show before. https://www1.mms-2008.com/ Should be fun. More posting more often soon.... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2008/04/desperately_see.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2008/04/desperately_see.html</guid>
<dc:subject></dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2008-04-27T16:32:45-08:00</dc:date>
</item>
<item>
<title>Transforming ITIL to Agile</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2008/03/transforming_it.html?source=rss</link>
<description>
 It&apos;s just dawned on me that Agile development won&apos;t work if it&apos;s only something the dev group is doing. It has to be part of how the whole operation. As an example, you can&apos;t have product managers going through a long waterfall process to create a 90 page PRD to be handed to the Agile guys. The PRD won&apos;t match up with the Agile process. The PMs have to get with the Agile program if Agile is going to be successful. Even if everyone approves of dev doing Agile, and there is no resistance to it, Agile won&apos;t be... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2008/03/transforming_it.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2008/03/transforming_it.html</guid>
<dc:subject>IT Process</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2008-03-27T16:03:13-08:00</dc:date>
</item>
<item>
<title>Visualization Coolness</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2008/03/visualization_c.html?source=rss</link>
<description>
 I&apos;m a big fan of TED (www.ted.com), inspired talks by the world&apos;s greatest thinkers and doers. Many of the talks have amazing visualizations. This one by Hans Rosling has been around for a while, but I like it a lot. The TED talks are fascinating. While perhaps not strictly IT, they are so creative that after watching them I feel like I can solve any IT problem. At least they put IT perspective which is often helpful when solving problems. The talks have been great to share with my team and have made for great discussions and problem solving,... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2008/03/visualization_c.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2008/03/visualization_c.html</guid>
<dc:subject>IT Community</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2008-03-13T10:27:56-08:00</dc:date>
</item>
<item>
<title>Change Detection</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2008/02/change_detectio.html?source=rss</link>
<description>
Wouldn&apos;t it be great if you could map your server configuration changes to all the other events happening on your systems? It turns out you can and on one display. Splunk has added configuration management to it&apos;s feature set so you can now tell Splunk to log changes to particular files or directories. Check out Splunk File System Change Monitor This is a preview release, but it&apos;s cool since it adds CM to Splunk&apos;s ability to powerfully index whatever you can get it to eat, and it will eat most things. While CM systems detect and log change, and provide... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2008/02/change_detectio.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2008/02/change_detectio.html</guid>
<dc:subject>Camp Sys Admin</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2008-02-27T14:58:54-08:00</dc:date>
</item>
<item>
<title>Green IT Machine</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2008/02/green_it_machin.html?source=rss</link>
<description>
There is a lot of green going on. I&apos;ve just started looking into Green Data Centers. What are you doing that&apos;s green in your Data Center? Here are some links: The Green Grid Cut Server Room Power Intel Goes Greener IBM Becomes More Energy Efficient It seems to me one of the first things you want to do is figure out what your actual energy consumption is so you can tell if something you do to make green accomplishes anything. Large system vendors are starting to offer tools to figure out data center power consumption and cooling requirements. EMC has... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2008/02/green_it_machin.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2008/02/green_it_machin.html</guid>
<dc:subject>Green IT</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2008-02-19T20:17:36-08:00</dc:date>
</item>
<item>
<title>Continuous Training</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2008/02/continuously_tr.html?source=rss</link>
<description>
It interesting how often IT people are left to their own devices as far as training is concerned. Some shops seem to think IT training is a needless expense they want to avoid or worse they think training someone will make them want to leave the company for greener pastures. I&apos;ve never understood why there is fear about training. There is a lot of evidence training improves IT efficiency. Here&apos;s an article from The Register with the data: Are your staff adequately trained? Training is critical for a lot of reasons. Aside from simply enabling staff to do better with... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2008/02/continuously_tr.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2008/02/continuously_tr.html</guid>
<dc:subject>Camp Sys Admin</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2008-02-11T10:57:20-08:00</dc:date>
</item>
<item>
<title>Community and Cooperation are the Keys to Success!</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2008/02/community_and_c.html?source=rss</link>
<description>
 In the old days, IT industry players were all about proprietary systems. The plan was to get the customer locked in to a particular company and to make it trouble for them to work with any other vendor. Digital Equipment Corporation (DEC) had their line of stuff, HP had theirs and Big Blue stuff set the pace for not working with anyone else. About the time of the UNIX client / servers, TCP was invented and cleaned up enough to connect a few computers. This changed the social environment as well, as customer demanded the ability to move their... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2008/02/community_and_c.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2008/02/community_and_c.html</guid>
<dc:subject>Enterprise Applications</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2008-02-01T22:51:52-08:00</dc:date>
</item>
<item>
<title>Ignoring the source code is akin to an ostrich sticking its head in the sand</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2007/10/ignoring_the_so.html?source=rss</link>
<description>
eWeek&apos;s Jim Rapoza recently released a slide show called 10 Things You Should Know About Open Source. I admit, I love lists and I love the perspectives laid out here. You&apos;ll need to visit the slide show for more info, but here&apos;s the list ... 1. Check the label 2. Not just for coders 3. Forks feed open source 4. You can ignore the source 5. GPL is not a social(ist) disease 6. Open source is no secret society 7. Open Source in Windows-friendly 8. Releasing the code isn&apos;t enough 9. Watch out for orphans 10. Dog the bounty hunters... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2007/10/ignoring_the_so.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2007/10/ignoring_the_so.html</guid>
<dc:subject>Open Source</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2007-10-17T11:33:30-08:00</dc:date>
</item>
<item>
<title>Remember when men were men and wrote their own device drivers?</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2007/09/remember_when_m.html?source=rss</link>
<description>
If you have the chops, your open source software project should lead and inform your commercial product. Red Hat and Ubuntu have done this brilliantly. Fedora precedes RHEL. Feisty goes before supported Gutsy. Both companies have rabid communities who gobble new code and contribute back fixes and improvements. The developer communities are happy to get cool new stuff. The commercial guys get better fit and finish. The early users are often the production guys as well, so they value early experience and use it to influence the production code. It&apos;s a quality loop and better for everybody. Success with this... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2007/09/remember_when_m.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2007/09/remember_when_m.html</guid>
<dc:subject>Open Source</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2007-09-19T12:50:47-08:00</dc:date>
</item>
<item>
<title>My downloads is bigger than yours!</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2007/09/my_downloads_is.html?source=rss</link>
<description>
My downloads is bigger than yours! CNET&apos;s Matt Asay posted an interesting blog today titled The Open Source Volume Myth. I believe his post succinctly pulls the covers off the value of the download metric that many feel is the best barometer of success in open source. Maybe in certain instances, sure. But in commercial open source (which I loosely define as a company trying to monetize their particular open source business model), that dog won&apos;t hunt. Déja vu back to the late nineties when all the internet-related start-ups thought their future fortunes were linked to oodles and oodles of... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2007/09/my_downloads_is.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2007/09/my_downloads_is.html</guid>
<dc:subject>Open Source</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2007-09-13T17:03:42-08:00</dc:date>
</item>
<item>
<title>It&apos;s all about working together</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2007/09/its_all_about_w.html?source=rss</link>
<description>
Systems and network monitoring is often a second or third order concern in IT organizations. The team usually agrees it&apos;s a good idea, but never seems to quite get monitoring set up and, more importantly, embedded into the IT process so it&apos;s kept up-to-date. When monitoring is up-to-date, it completes an ideal quality circuit that provides not just accurate feedback about how IT and the team are functioning, but also advertises what the team has done for the company lately. Unfortunately, monitoring is complicated. Most IT shops have purchased &quot;big iron&quot; monitoring tools that turned out to be larger projects... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2007/09/its_all_about_w.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2007/09/its_all_about_w.html</guid>
<dc:subject>Open Source</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2007-09-13T09:54:49-08:00</dc:date>
</item>
<item>
<title>Is that a real poncho or a Sears poncho?</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2007/08/is_that_a_real.html?source=rss</link>
<description>
Companies that respond to Open Source communities have the advantage: the old proprietary ways are over. IBM got this and has done well with projects like XCat and Eclipse. But, companies vary in their ability to participate in open source. Some companies aren&apos;t able to go beyond posting a demo on SourceForge. It&apos;s a demo for a commercial product because there isn&apos;t a community producing patches and product direction behind it. It&apos;s just a company calling itself open source for marketing gain without contributing to the community. One sign of this is when the company moves the discussion forum for... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2007/08/is_that_a_real.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2007/08/is_that_a_real.html</guid>
<dc:subject>Open Source</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2007-08-27T18:25:40-08:00</dc:date>
</item>
<item>
<title>Open Source Outsourcing</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2007/08/open_source_out.html?source=rss</link>
<description>
Companies that are strong with the Open Source force gain code contributions and testing from their OS communities. This has become critical since feedback from users needs to be direct to the developers or feature requests get lost in the translation. When a bug has to travel from support -&gt; operations -&gt; marketing -&gt; product management -&gt; QA -&gt; Eng management -&gt; engineering -&gt; coder, you get the telephone game effect. Avoiding this commercial vendor daisy chain is one of the underpinnings of Open Source projects that make them robust. The smart software companies like Google and Red Hat know... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2007/08/open_source_out.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2007/08/open_source_out.html</guid>
<dc:subject>Open Source</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2007-08-16T16:16:18-08:00</dc:date>
</item>
<item>
<title>Outsource!</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2007/08/outsource.html?source=rss</link>
<description>
I often see very smart programmers who are working hard but perhaps not so smart. It’s hard in they need to grind out code to get something done; it’s not so smart because they often code stuff a junior &quot;code pig&quot; could and would like to write. Why not hire someone and outsource the coding? This would relieve core smart people to address other problems. Marketing guru Geoffrey Moore speaks of core vs. context, and recommends outsourcing anything that&apos;s not core. In an open source company, it’s important to define what the core activities are. I think there are several.... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2007/08/outsource.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2007/08/outsource.html</guid>
<dc:subject>Open Source</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2007-08-14T13:36:58-08:00</dc:date>
</item>
<item>
<title>Ask The Experts: It&apos;s What Project Leads Really Want</title>
<link>http://weblog.infoworld.com/ittroubleshooter/archives/2007/08/ask_the_experts.html?source=rss</link>
<description>
Project leads are good at a lot of things, like thoroughly understanding the ins and outs of their projects, keeping things on track, and getting problems solved. The downside of being so good at the job is that they become immersed in the details and demands of running their projects and spend less time face-to-face with the people who are using them (let&apos;s face it, email is not the same). The people at GroundWork know the value of getting people together in person. For the second year in a row, they&apos;re sponsoring an Open Source Council, bringing together &quot;lead developers... &lt;a href=&quot;http://weblog.infoworld.com/ittroubleshooter/archives/2007/08/ask_the_experts.html?source=rss&quot;&gt; READ MORE&lt;/a&gt; &lt;/p&gt; 
</description>
<guid>http://weblog.infoworld.com/ittroubleshooter/archives/2007/08/ask_the_experts.html</guid>
<dc:subject>Open Source</dc:subject>
<dc:creator>Harper Mann</dc:creator>
<dc:date>2007-08-01T15:45:12-08:00</dc:date>
</item>


</channel>
</rss>
