Nick Parker
My Ramblings on Software Development...
Twitter
Follow me on
Twitter
Site Sections
Home
Contact
Syndication
Login
Recent Posts
Generic Factory over Object Initializers
Vimperator Tip - awesome bar
Vim + Firefox = Vimperator
Vim Tip of the Day - File Explorer Navigation
Microsoft Mocking Framework and TypeMock
Recent Comments
thanks for the information about Microsoft vs. Sun...
by Busby SEO Test
thanks for the "Linguistic Profile&am...
by Busby SEO Test
I use the following to configuration to persistent...
by Jon
Try MbUnit. Its also a great tool to work with, an...
by soundararajan
I use Ctrl-z when using Google maps or Gmail. Thi...
by seren
Archives
October, 2008 (1)
September, 2008 (1)
June, 2008 (1)
May, 2008 (1)
April, 2008 (1)
March, 2008 (1)
February, 2008 (2)
January, 2008 (1)
December, 2007 (1)
October, 2007 (1)
September, 2007 (1)
August, 2007 (3)
July, 2007 (2)
June, 2007 (1)
May, 2007 (4)
April, 2007 (6)
March, 2007 (3)
February, 2007 (3)
January, 2007 (4)
December, 2006 (1)
October, 2006 (4)
September, 2006 (3)
August, 2006 (2)
July, 2006 (3)
June, 2006 (4)
May, 2006 (4)
April, 2006 (5)
March, 2006 (2)
February, 2006 (2)
January, 2006 (5)
December, 2005 (5)
November, 2005 (5)
October, 2005 (4)
September, 2005 (10)
August, 2005 (3)
July, 2005 (5)
June, 2005 (3)
May, 2005 (2)
April, 2005 (5)
March, 2005 (5)
February, 2005 (5)
January, 2005 (18)
December, 2004 (5)
November, 2004 (4)
October, 2004 (12)
September, 2004 (4)
Post Categories
.NET
Agile
AOP
CI
Design Patterns
DLR
General
IronPython
MSBuild
NAnt
Open Source
Productivity
Ruby
Software
TDD
Vim
Visual Studio
December 2007 Entries
The Pitfalls of Concession
posted @
Sunday, December 09, 2007 5:45 PM
|
Feedback (0)
Ayende recently
posted
about a design aspect of the new MVC framework coming down from Microsoft. Ayende raised concern about the design requirement of attributing your public actions on a controller. He points out that Rob Conery has a 6 page
post
covering the usage of a tool to mask the pain involved in typing the excess noise. A
follow-up
by Phil Haack presents a solution through subclassing that allows one to avoid the attribute. What about composition instead?
The real reason behind this post is not to discuss the merit of a design decision directly, but the more off-handed results that come from it. If Microsoft is protecting the developer from making mistakes by requiring an attribute here and there within a controller, well, why wouldn't they protect the developer all over the place? Where does one draw a line in the sand from a design perspective? If we made a concession before, can we use that as justification for yet another design decision that might change the direction of the software even further? While the CTP is baked, the API can still change and Microsoft is listening, pipe up if you care to share your opinion.
tags:
.NET