<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://devlicio.us/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Tim Barcz : Commentary</title><link>http://devlicio.us/blogs/tim_barcz/archive/tags/Commentary/default.aspx</link><description>Tags: Commentary</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP1 (Build: 31106.3070)</generator><item><title>Poor Design Is Not a Bug</title><link>http://devlicio.us/blogs/tim_barcz/archive/2010/11/25/poor-design-is-not-a-bug.aspx</link><pubDate>Fri, 26 Nov 2010 03:37:18 GMT</pubDate><guid isPermaLink="false">40756a8b-6212-4073-9d98-6c26781577de:63610</guid><dc:creator>Tim Barcz</dc:creator><slash:comments>190</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://devlicio.us/blogs/tim_barcz/rsscomments.aspx?PostID=63610</wfw:commentRss><comments>http://devlicio.us/blogs/tim_barcz/archive/2010/11/25/poor-design-is-not-a-bug.aspx#comments</comments><description>&lt;p&gt;&lt;a href="http://www.ayende.com/blog"&gt;Ayende&lt;/a&gt; recently posted a an article titled &lt;a title="Ayende&amp;#39;s post &amp;quot;Where is the Bug?" href="http://ayende.com/Blog/archive/2010/11/17/where-is-the-bug-yet-again.aspx"&gt;“Where is the bug”&lt;/a&gt;.&amp;#160; While reading the comments, I was disappointed by some of the answers to Ayende’s request to find the bug. Here are two of the comments that stood out to me:&lt;/p&gt;  &lt;ul&gt;   &lt;li&gt;“You could argue the biggest bug is the use of a switch statement as it violates OCP.“ &lt;/li&gt;    &lt;li&gt;“The use of a switch statement is a bug in itself.“ &lt;/li&gt; &lt;/ul&gt;  &lt;p&gt;What bothers me so greatly is people’s inability to separate design discussion with bugs. A bug is defined on Wikipedia as:&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;A &lt;b&gt;software bug&lt;/b&gt; is the common term used to describe an error, flaw, mistake, &lt;a href="http://en.wikipedia.org/wiki/Failure"&gt;failure&lt;/a&gt;, or &lt;a href="http://en.wikipedia.org/wiki/Fault_%28technology%29"&gt;fault&lt;/a&gt; in a computer program or &lt;a href="http://en.wikipedia.org/wiki/Software_system"&gt;system&lt;/a&gt; that produces an incorrect or unexpected result, or causes it to behave in unintended ways&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;The two comments above don’t attempt to solve the bug and instead take an “ivory tower approach” to the problem (more befuddling is that removing the switch in favor of something else would leave the bug in place). This bugs me because we (as an industry) continue to care very little about the output and meeting of customer/business needs and more about code structure and semantics than actually working code.&lt;/p&gt;  &lt;p&gt;Let me state for the record, it is &lt;em&gt;perfectly acceptable&lt;/em&gt; to talk about code structure and design but please let’s not confuse a bug – an actual error or flaw in code – with poor design.&lt;/p&gt;  &lt;p&gt;(I think it’d be humorous for Ayende to post some perfectly fine code and ask “Where’s the bug” and watch people trip over themselves trying to find something wrong)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://devlicio.us/aggbug.aspx?PostID=63610" width="1" height="1"&gt;</description><category domain="http://devlicio.us/blogs/tim_barcz/archive/tags/Principles/default.aspx">Principles</category><category domain="http://devlicio.us/blogs/tim_barcz/archive/tags/Common+Sense/default.aspx">Common Sense</category><category domain="http://devlicio.us/blogs/tim_barcz/archive/tags/Musings/default.aspx">Musings</category><category domain="http://devlicio.us/blogs/tim_barcz/archive/tags/Commentary/default.aspx">Commentary</category></item><item><title>What to Make of Intel Buying McAfee</title><link>http://devlicio.us/blogs/tim_barcz/archive/2010/08/19/what-to-make-of-intel-buying-mcafee.aspx</link><pubDate>Thu, 19 Aug 2010 20:39:00 GMT</pubDate><guid isPermaLink="false">40756a8b-6212-4073-9d98-6c26781577de:61561</guid><dc:creator>Tim Barcz</dc:creator><slash:comments>46</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://devlicio.us/blogs/tim_barcz/rsscomments.aspx?PostID=61561</wfw:commentRss><comments>http://devlicio.us/blogs/tim_barcz/archive/2010/08/19/what-to-make-of-intel-buying-mcafee.aspx#comments</comments><description>&lt;p&gt;&lt;a href="http://www.jamessenior.com/"&gt;James Senior&lt;/a&gt; posted on &lt;a href="http://twitter.com/jsenior"&gt;his Twitter account&lt;/a&gt;:&lt;/p&gt;  &lt;blockquote&gt;   &lt;p&gt;“oh dear lord no. why intel, why? &lt;a href="http://ow.ly/2s2dm"&gt;http://ow.ly/2s2dm&lt;/a&gt; reminds me of when Intel got into the hosting business. &lt;a href="http://ow.ly/2s2fT"&gt;http://ow.ly/2s2fT&lt;/a&gt;”&lt;/p&gt; &lt;/blockquote&gt;  &lt;p&gt;James is referencing an article posted by the BBC on the recent news of Intel’s takeover of McAfee for 7.68 Billion. While I agree with James on Intel’s foray into hosting – of course hindsight is 20/20 – I disagree with his position on this particular deal and here’s why.&lt;/p&gt;  &lt;p&gt;Despite the rapid growth over the last 15 years of PC’s, viruses are still problematic. Despite continual efforts at training the masses, viruses still are far too prevalent. Additionally the methods for exploitation continue to spread and evolve faster than the education can keep up with.&amp;#160; For example, by now, the vast majority – save your grandmother – knows not to open executables sent via email (largely this practice is blocked at the email level anyway).&amp;#160; A smaller, but still growing population have learned to not open attachments from people you don’t know. And yet viruses at times runs rampant.&lt;/p&gt;  &lt;p&gt;The virus landscape has largely changed with a more sophisticated modern day virus writer.&amp;#160; He/she is no longer malicious in their intent to infect your computer but instead often plant malware to consume and distribute private information on your computer. Certainly dangerous viruses still exist, but there’s less money in that.&lt;/p&gt;  &lt;p&gt;Given that education can’t keep up (or thus far hasn’t proven to be able to keep up) with the changing exploits and security software saturation is still less than 100%, I see the move by Intel as a positive one. Imagine virus protection at the chip level. The virus uses the chip and it’s processing to do it’s damage. If the chip can refuse access to the virus, the virus is rendered ineffective.&lt;/p&gt;  &lt;p&gt;In an environment with increasing questions/concerns about security threats, a chip maker who can offer it’s customers virus protection has a significant advantage over it’s competitors.&amp;#160; Additionally, every computer has a CPU and saturation into the market would be swift as computers with this technology would be introduced into the market as people replaced their old PC’s.&lt;/p&gt;  &lt;p&gt;In an interesting twist to this story, I could see Microsoft having interest in this particular marriage. Largely portrayed by many as insecure, a chip with protection renders the discussion about OS security potentially moot. Whether Microsoft would admit to it or not, it has skin in this game.&lt;/p&gt;  &lt;p&gt;Overall, I think Intel’s choice is a strategic one and might prove be a great one. After over two decades of security software, software hasn’t been the answer. That doesn’t mean software couldn’t be the answer, however history has thus far shown software as a weak solution.&amp;#160; It’s time for a game-changer. This could be the road to that much needed change.&lt;/p&gt;  &lt;p&gt;Time will tell…&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://devlicio.us/aggbug.aspx?PostID=61561" width="1" height="1"&gt;</description><category domain="http://devlicio.us/blogs/tim_barcz/archive/tags/Opinion/default.aspx">Opinion</category><category domain="http://devlicio.us/blogs/tim_barcz/archive/tags/Commentary/default.aspx">Commentary</category></item></channel></rss>