<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/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>What does "Robust" mean?</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx</link><description>Back in the days of NT OS/2, one of the things that was absolutely drilled into the development team was robustness. I even went so far as to write "Robustness" on my whiteboard in 1 foot high letters as a daily reminder. The team distributed mugs with</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: What does "Robust" mean?</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#362764</link><pubDate>Fri, 28 Jan 2005 22:10:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:362764</guid><dc:creator>Mike Dimmick</dc:creator><description>&amp;quot;So the robustness criteria for Exchange (or any other email system) includes the users data, while the robustness criteria for NTFS doesn't.&amp;quot;&lt;br&gt;&lt;br&gt;At least, not at the moment. I recall that Longhorn (at least, as announced at the 2003 PDC) will feature Transactional NTFS. Is this still slated for Longhorn, and will it protect simple file writes automatically? Obviously atomic updates to multiple files will need additional coding, but what can we expect, if anything, for existing applications?</description></item><item><title>re: What does "Robust" mean?</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#362766</link><pubDate>Fri, 28 Jan 2005 22:17:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:362766</guid><dc:creator>Larry Osterman</dc:creator><description>Mike, that may be true, I don't know.  I do know that if it's enabled, it won't be enabled by default - the performance cost of transacting application data writes is prohibitive (network file copies would be twice as slow, for example).&lt;br&gt;&lt;br&gt;</description></item><item><title>re: What does "Robust" mean?</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#363149</link><pubDate>Sat, 29 Jan 2005 18:55:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:363149</guid><dc:creator>kip</dc:creator><description>This is just the best blog.  I'm always happy when there's new Larry Osterman to read.&lt;br&gt;&lt;br&gt;Here's my meager attempt at a &amp;quot;robust&amp;quot; definition:&lt;br&gt;&lt;br&gt;A program is robust if, by design, it protects critical data and critical access, provides fail-safe operation, and allows for system recovery when the unexpected does occur.&lt;br&gt;&lt;br&gt;Feel free to pick it apart.  I'd be honored.&lt;br&gt;</description></item><item><title>re: What does "Robust" mean?</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#363291</link><pubDate>Sun, 30 Jan 2005 06:31:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:363291</guid><dc:creator>Jim Lyon</dc:creator><description>How about this: A program (or machine) is robust if it does not exhibit failure modes that are costly.&lt;br&gt;&lt;br&gt;For the ATM, screwing up the customer's account is high cost; failure to do anything isn't. For the telephone network, failure to connect is high cost.&lt;br&gt;&lt;br&gt;Also a quibble: In the early 80's I was in the electronic security industry. At that time, it was common for ATM's to fail to account for 1 to 2% of the cash they dispensed. Even then, it was cheaper for banks to eat this 1-2% than to pay human tellers. However, every bank understood that it was very expensive to charge a customer's account without dispensing the money -- reconciliation typically cost tens of dollars, and frequently resulted in the loss of a customer, whose acquisition cost was often about $50.&lt;br&gt;</description></item><item><title>Larry on robustness</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#363305</link><pubDate>Sun, 30 Jan 2005 11:19:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:363305</guid><dc:creator>Ben Reichelt's Blog</dc:creator><description /></item><item><title>re: What does "Robust" mean?</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#363667</link><pubDate>Mon, 31 Jan 2005 10:07:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:363667</guid><dc:creator>Rob</dc:creator><description>This all sounds right and standard for a sensible definition of robustness.&lt;br&gt;&lt;br&gt;A quibble of my own: where on Earth do you come from that thinks this is a grammatically meaningful sentence:&lt;br&gt;&lt;br&gt;&amp;lt;blockquote&amp;gt;The team distributed mugs with &amp;quot;INDUSTRIAL STRENGTH&amp;quot; on them (to indicate that NT, unlike previous MS operating systems) needed to be robust enough to work in mission critical environments.&amp;lt;/blockquote&amp;gt;&lt;br&gt;&lt;br&gt;Some mad parenthesis there :)</description></item><item><title>re: What does "Robust" mean?</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#363741</link><pubDate>Mon, 31 Jan 2005 12:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:363741</guid><dc:creator>Petr Kadlec</dc:creator><description>Interesting article. My understanding of &amp;quot;Robust&amp;quot; has always been substantially different than your definition. It seems to me that a program that does not cause problems &amp;quot;when operating in its expected use scenarios&amp;quot; is merely _correct_. I mean, if a program fails  in its expected use scenario, it cannot be considered as a valid solution at all.&lt;br&gt;&lt;br&gt;To me, robustness is a virtue proved by &amp;quot;failing gracefully&amp;quot; (not killing anyone around etc.) even when the conditions have not been expected. The response to the problems that were unexpected is the key definition to me. (Well, obviously, you cannot create a system that would be able to handle anything, so the conditions have to be &amp;quot;expected&amp;quot; at least in some generic way, but nonetheless I feel they shouldn't be named &amp;quot;expected scenarios&amp;quot;.)</description></item><item><title>re: What does "Robust" mean?</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#363787</link><pubDate>Mon, 31 Jan 2005 14:56:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:363787</guid><dc:creator>G. Man</dc:creator><description>I think the real problem with your definition is that you seem to use &amp;quot;unexpected behavior&amp;quot; and &amp;quot;failure&amp;quot; interchangeably... I think they are 2 different things.&lt;br&gt;</description></item><item><title>re: What does "Robust" mean?</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#363850</link><pubDate>Mon, 31 Jan 2005 16:43:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:363850</guid><dc:creator>Larry Osterman</dc:creator><description>Rob: That's because I don't have an editor to catch my stupid mistakes.&lt;br&gt;&lt;br&gt;Petr: That's why I have the second sentence (about recovering without lost data).  You're right that it's &amp;quot;merely _correct_&amp;quot;, and a correct program _should_ be robust.&lt;br&gt;&lt;br&gt;As I said in the beginning, everyone likes to use the word &amp;quot;Robust&amp;quot; (or &amp;quot;Reliable&amp;quot;) but the basic problem here is that the word is meaningless.  Is a phone network more robust (or reliable) than an ATM because it's always available?&lt;br&gt;&lt;br&gt;Robustness is clearly a desirable feature in a system, but how do you know if your system _is_ robust?&lt;br&gt;&lt;br&gt;</description></item><item><title>re: What does "Robust" mean?</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#367996</link><pubDate>Sun, 06 Feb 2005 13:38:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:367996</guid><dc:creator>Frank Hamersley</dc:creator><description>Your definition is most illuminating given your (and your employers) position within the IT industry.&lt;br&gt;&lt;br&gt;The distinction of &amp;quot;operating in its expected use scenarios&amp;quot; is far too weak IMO and experiance oft reinforces this belief.&lt;br&gt;&lt;br&gt;Truly robust programmes manage unexpected use cases as well as the (apparently) impossible ones.&lt;br&gt;&lt;br&gt;Had this ethic permeated the industry some time ago I suspect the times would not be quite as exciting or depressing depending (respectively ) whether you are observing or afflicted with the manic exploit riddled jungle we find ourselves in.&lt;br&gt;&lt;br&gt;Personally I don't think too many &amp;quot;real&amp;quot; programmers are willingly complict in this but the expediencies driven by Marketers to ship now, fix later and the ultra-rationalist vesting mentat make it difficult for ppl to deliver on such principles.&lt;br&gt;&lt;br&gt;Frank.</description></item><item><title>Words I dislike - Policy</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#443853</link><pubDate>Wed, 27 Jul 2005 18:40:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:443853</guid><dc:creator>Larry Osterman's WebLog</dc:creator><description>A while back, I wrote about how I disliked the word &amp;amp;quot;Robustness&amp;amp;quot; because it's meaning was so vague. ...</description></item><item><title> Larry Osterman s WebLog What does Robust mean | Paid Surveys</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#9664443</link><pubDate>Sat, 30 May 2009 13:15:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9664443</guid><dc:creator> Larry Osterman s WebLog What does Robust mean | Paid Surveys</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://paidsurveyshub.info/story.php?title=larry-osterman-s-weblog-what-does-robust-mean"&gt;http://paidsurveyshub.info/story.php?title=larry-osterman-s-weblog-what-does-robust-mean&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Larry Osterman s WebLog What does Robust mean | work from home</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#9762126</link><pubDate>Tue, 16 Jun 2009 16:17:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9762126</guid><dc:creator> Larry Osterman s WebLog What does Robust mean | work from home</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://workfromhomecareer.info/story.php?id=22107"&gt;http://workfromhomecareer.info/story.php?id=22107&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Larry Osterman s WebLog What does Robust mean | debt solutions</title><link>http://blogs.msdn.com/larryosterman/archive/2005/01/28/362651.aspx#9791671</link><pubDate>Fri, 19 Jun 2009 21:22:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9791671</guid><dc:creator> Larry Osterman s WebLog What does Robust mean | debt solutions</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://debtsolutionsnow.info/story.php?id=929"&gt;http://debtsolutionsnow.info/story.php?id=929&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>