﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Moutasem al-awa commented on When the design violates the principle of least surprise, you don’t close it as By Design</title><description>Man, cant they mimic RubyOnRails if they can not design their own API, as you said its misleading and you should have a separate Flowchart to know whether its satisfying the simple need for validation or not. Complex solution for a simple problem :) MSDN way
</description><link>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment7</link><guid>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment7</guid><pubDate>Sun, 24 Jan 2010 08:51:13 GMT</pubDate></item><item><title>Borek commented on When the design violates the principle of least surprise, you don’t close it as By Design</title><description>Brad explains in his post why it's not easy / possible to change the Required attribute now.
</description><link>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment6</link><guid>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment6</guid><pubDate>Fri, 22 Jan 2010 18:33:00 GMT</pubDate></item><item><title>Justice~! commented on When the design violates the principle of least surprise, you don’t close it as By Design</title><description>I agree entirely man.  That is crazy.
  
</description><link>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment5</link><guid>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment5</guid><pubDate>Thu, 21 Jan 2010 17:07:13 GMT</pubDate></item><item><title>Sean Gough commented on When the design violates the principle of least surprise, you don’t close it as By Design</title><description>Well said!  If people get this wrong more that 4,000 times a day then that's a pretty good indication that the attribute is named incorrectly! 
  
  
To quote Inigo Montoya:
  
  
"You keep using that word. I do not think it means what you think it means."
</description><link>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment4</link><guid>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment4</guid><pubDate>Thu, 21 Jan 2010 15:17:00 GMT</pubDate></item><item><title>Mark commented on When the design violates the principle of least surprise, you don’t close it as By Design</title><description>I agree completely. In my opinion, not fixing issues like this when there is still the chance to do so (i.e. before a final release) is somewhat of an oversight.
  
  
In this particular case, I understand some of the points being made and the decisions behind them. However the fact still remains - understanding this behaviour hinges on knowing the reasoning behind it and this seems wrong. As you have said, the design should not be misleading. I'm sure it would have been possible to gather ideas from all those concerned and come up with a solution which pleases more people.
</description><link>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment3</link><guid>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment3</guid><pubDate>Thu, 21 Jan 2010 09:35:46 GMT</pubDate></item><item><title>spmason commented on When the design violates the principle of least surprise, you don’t close it as By Design</title><description>I couldn't agree more
</description><link>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment2</link><guid>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment2</guid><pubDate>Thu, 21 Jan 2010 09:18:16 GMT</pubDate></item><item><title>Barry Dahlberg commented on When the design violates the principle of least surprise, you don’t close it as By Design</title><description>Possible alternate names for the attribute:
  
[Required_NotReally], [Maybe], [HahaFooledYou]
</description><link>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment1</link><guid>http://ayende.com/4369/when-the-design-violates-the-principle-of-least-surprise-you-don-t-close-it-as-by-design#comment1</guid><pubDate>Thu, 21 Jan 2010 09:16:46 GMT</pubDate></item></channel></rss>