<?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: A Challenge to NI: Use your Application Builder</title>
	<atom:link href="http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/feed/" rel="self" type="application/rss+xml" />
	<link>http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/</link>
	<description>an unfiltered stream of data flow consciousness</description>
	<pubDate>Thu,  4 Dec 2008 16:49:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Jim Kring</title>
		<link>http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11524</link>
		<dc:creator>Jim Kring</dc:creator>
		<pubDate>Fri, 06 Jun 2008 17:05:36 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11524</guid>
		<description>Matt: Another interesting thought is that an engineer who is highly skilled in using NI products might be more valuable to NI when they are working for a large company vs. an NI alliance partner.  The reason being that they can more effectively evangelize NI products within that large organization and they probably have a big stack of purchase orders ;)</description>
		<content:encoded><![CDATA[<p>Matt: Another interesting thought is that an engineer who is highly skilled in using NI products might be more valuable to NI when they are working for a large company vs. an NI alliance partner.  The reason being that they can more effectively evangelize NI products within that large organization and they probably have a big stack of purchase orders <img src='http://thinkinging.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11519</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Fri, 06 Jun 2008 15:21:04 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11519</guid>
		<description>Interesting point Jim. I wouldn't have thought about how hiring an engineer from the industry might remove a customer. Valid and certainly an eye opening perspective. Thanks!</description>
		<content:encoded><![CDATA[<p>Interesting point Jim. I wouldn&#8217;t have thought about how hiring an engineer from the industry might remove a customer. Valid and certainly an eye opening perspective. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Kring</title>
		<link>http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11403</link>
		<dc:creator>Jim Kring</dc:creator>
		<pubDate>Tue, 03 Jun 2008 16:04:13 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11403</guid>
		<description>Matt: Yes, you’re probably right. NI typically doesn’t pay for experience engineers — they prefer to hire right out of college and have them develop their experience within NI. This is what makes &lt;a href="http://en.wikipedia.org/wiki/Eat_one%27s_own_dog_food" rel="nofollow"&gt;eating their own dog food&lt;/a&gt; so important. It would probably benefit NI greatly to hire outside people who are very skilled users of NI’s tools, however, these individuals are, at the same time, both (1) expensive to hire and (2) have an enormous value to NI, when left “out in the wild”, where they directly purchase NI’s products or facilitate the purchase of NI’s products through integration services.</description>
		<content:encoded><![CDATA[<p>Matt: Yes, you’re probably right. NI typically doesn’t pay for experience engineers — they prefer to hire right out of college and have them develop their experience within NI. This is what makes <a href="http://en.wikipedia.org/wiki/Eat_one%27s_own_dog_food" rel="nofollow">eating their own dog food</a> so important. It would probably benefit NI greatly to hire outside people who are very skilled users of NI’s tools, however, these individuals are, at the same time, both (1) expensive to hire and (2) have an enormous value to NI, when left “out in the wild”, where they directly purchase NI’s products or facilitate the purchase of NI’s products through integration services.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11399</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Tue, 03 Jun 2008 15:31:39 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11399</guid>
		<description>Jim:

Interesting point, for years I have maintained the belief that NI doesn't hire enough from industry, since they typically hire right out of college. People that haven't practiced, seldom preach an accurate message.

Do you think this hiring practice could be one of the root causes? Just curious about your opinion.</description>
		<content:encoded><![CDATA[<p>Jim:</p>
<p>Interesting point, for years I have maintained the belief that NI doesn&#8217;t hire enough from industry, since they typically hire right out of college. People that haven&#8217;t practiced, seldom preach an accurate message.</p>
<p>Do you think this hiring practice could be one of the root causes? Just curious about your opinion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mikael</title>
		<link>http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11209</link>
		<dc:creator>Mikael</dc:creator>
		<pubDate>Wed, 28 May 2008 22:25:53 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11209</guid>
		<description>Jim, 
15 Hours, it would be good if you could use a cluster server like this one:
http://helmer.sfe.se/
Cheers,
Mikael</description>
		<content:encoded><![CDATA[<p>Jim,<br />
15 Hours, it would be good if you could use a cluster server like this one:<br />
<a href="http://helmer.sfe.se/" rel="nofollow">http://helmer.sfe.se/</a><br />
Cheers,<br />
Mikael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ton Plomp</title>
		<link>http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11193</link>
		<dc:creator>Ton Plomp</dc:creator>
		<pubDate>Wed, 28 May 2008 11:16:31 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11193</guid>
		<description>And that's why we love OpenG, Tom see &lt;a href="http://wiki.openg.org/Current_VIs_Parent_Directory" rel="nofollow"&gt;here&lt;/a&gt;.

On the builder issue, what happens during those 15 hours? That are a lot of computations.

Ton</description>
		<content:encoded><![CDATA[<p>And that&#8217;s why we love OpenG, Tom see <a href="http://wiki.openg.org/Current_VIs_Parent_Directory" rel="nofollow">here</a>.</p>
<p>On the builder issue, what happens during those 15 hours? That are a lot of computations.</p>
<p>Ton</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Eilers</title>
		<link>http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11184</link>
		<dc:creator>Tom Eilers</dc:creator>
		<pubDate>Wed, 28 May 2008 07:04:27 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11184</guid>
		<description>It is not only that LVOOP things won't work if you build an application. Also a lot of Properties won't work any more after you build an application and that changes with every Labview version. And the superstar of all the vi's that won't work is the Current Path VI that never was good.</description>
		<content:encoded><![CDATA[<p>It is not only that LVOOP things won&#8217;t work if you build an application. Also a lot of Properties won&#8217;t work any more after you build an application and that changes with every Labview version. And the superstar of all the vi&#8217;s that won&#8217;t work is the Current Path VI that never was good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Kring</title>
		<link>http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11171</link>
		<dc:creator>Jim Kring</dc:creator>
		<pubDate>Tue, 27 May 2008 22:48:14 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11171</guid>
		<description>Justin: Regarding, “foreheads simultaneously hitting their desks”, that sounds a lot like what happened when I found out :)

Ben: Yes, these concepts are timeless.  Thanks for sharing that story.  I'm looking forward to sharing some stories about about how we're eating our own dog food at JKI, soon.

Mikael: It's too bad you can't use that 30 minutes to catch up on LAVA.  Actually, I've worked on an application that takes 15 hours to build!  And, it took much longer than that before we did some build optimization (removing some type definitions that were inside the class data cluster).  Our solution to the long build time was to have a dedicated build machine with quad (4) core 2 duo processors.  But still, this is very impractical -- we can't wait 15 hours to know if a build was successful.</description>
		<content:encoded><![CDATA[<p>Justin: Regarding, “foreheads simultaneously hitting their desks”, that sounds a lot like what happened when I found out <img src='http://thinkinging.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Ben: Yes, these concepts are timeless.  Thanks for sharing that story.  I&#8217;m looking forward to sharing some stories about about how we&#8217;re eating our own dog food at JKI, soon.</p>
<p>Mikael: It&#8217;s too bad you can&#8217;t use that 30 minutes to catch up on LAVA.  Actually, I&#8217;ve worked on an application that takes 15 hours to build!  And, it took much longer than that before we did some build optimization (removing some type definitions that were inside the class data cluster).  Our solution to the long build time was to have a dedicated build machine with quad (4) core 2 duo processors.  But still, this is very impractical &#8212; we can&#8217;t wait 15 hours to know if a build was successful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mikael</title>
		<link>http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11169</link>
		<dc:creator>Mikael</dc:creator>
		<pubDate>Tue, 27 May 2008 22:17:27 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11169</guid>
		<description>Hi
I hope NI will abandon the LLB structure they are using in the exe-file or at least add folder support in the a LLB, this will make it possible to store everything inside the exe-file.
One other painful thing I have is that a quite large application, with lot of classes and lvlibs, it takes me more then 30 minutes to build an executable and during that time I can’t use my computer for something else, since LabVIEW uses all my resources.
Cheers,
Mikael</description>
		<content:encoded><![CDATA[<p>Hi<br />
I hope NI will abandon the LLB structure they are using in the exe-file or at least add folder support in the a LLB, this will make it possible to store everything inside the exe-file.<br />
One other painful thing I have is that a quite large application, with lot of classes and lvlibs, it takes me more then 30 minutes to build an executable and during that time I can’t use my computer for something else, since LabVIEW uses all my resources.<br />
Cheers,<br />
Mikael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11166</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Tue, 27 May 2008 19:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://thinkinging.com/2008/05/27/a-dogfooding-challenge-to-ni-use-your-application-builder/#comment-11166</guid>
		<description>Good points Jim!

That reminds me a war story from back in the day...

Ken Olsen (owner and founder of Digital Equipment Corp.) gathered all of his top managers togther and demanded that they assemble a computer system using only the instructions available when they were shipped.

It was not very long until the hardware got much easier to work with.

Ben</description>
		<content:encoded><![CDATA[<p>Good points Jim!</p>
<p>That reminds me a war story from back in the day&#8230;</p>
<p>Ken Olsen (owner and founder of Digital Equipment Corp.) gathered all of his top managers togther and demanded that they assemble a computer system using only the instructions available when they were shipped.</p>
<p>It was not very long until the hardware got much easier to work with.</p>
<p>Ben</p>
]]></content:encoded>
	</item>
</channel>
</rss>
