<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Be a MacGyver &#8212; not a MacGruber</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/networkhub/be-a-macgyver-not-a-macgruber/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/networkhub/be-a-macgyver-not-a-macgruber/</link>
	<description>A SearchNetworking.com blog</description>
	<pubDate>Mon, 09 Nov 2009 21:49:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Okcaver54</title>
		<link>http://itknowledgeexchange.techtarget.com/networkhub/be-a-macgyver-not-a-macgruber/#comment-97</link>
		<dc:creator>Okcaver54</dc:creator>
		<pubDate>Mon, 12 May 2008 21:33:35 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/networkhub/be-a-macgyver-not-a-macgruber/#comment-97</guid>
		<description>First - I am not at all sure being a techie nerd is such a bad thing, however being able to explain things to people in different fields and levels of interest is a good trait in any level or work,

The best application in the world won't work if the network has a problem, and the best network in the world isn't worth much without applications and data to run on it.

The network engineer  or technician no longer is dealing with just the transfer of bits and bytes between data jacks - the network itself has changed. The network is now part of the devices on each end and part of the applications that are running on them,  

Network people need  the developers, and project managers to work the problem to resolution  without finger pointing. The developers, system administrators, DBA's, project managers, etc. need  to  be willing to join in, not just hand the issue off to the network people. 

I'd like to think a network person is one of the smartest people and most technically savvy, but I sure have been proved wrong once or twice by some of the programmers and security people.</description>
		<content:encoded><![CDATA[<p>First - I am not at all sure being a techie nerd is such a bad thing, however being able to explain things to people in different fields and levels of interest is a good trait in any level or work,</p>
<p>The best application in the world won&#8217;t work if the network has a problem, and the best network in the world isn&#8217;t worth much without applications and data to run on it.</p>
<p>The network engineer  or technician no longer is dealing with just the transfer of bits and bytes between data jacks - the network itself has changed. The network is now part of the devices on each end and part of the applications that are running on them,  </p>
<p>Network people need  the developers, and project managers to work the problem to resolution  without finger pointing. The developers, system administrators, DBA&#8217;s, project managers, etc. need  to  be willing to join in, not just hand the issue off to the network people. </p>
<p>I&#8217;d like to think a network person is one of the smartest people and most technically savvy, but I sure have been proved wrong once or twice by some of the programmers and security people.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->