David Hayden [MVP C#] - All Comments

re: Tampa ASP.NET MVC Developer Group Meeting Recap

dzejms — Sun, 19 Apr 2009 16:12:23 GMT

Thanks for the screencast David. It really helps solidify what was shown on Thursday.

re: Excited About Unfuddle Subversion / Git Hosting and their Mac Widget ;)

David Carrillo — Mon, 30 Mar 2009 16:46:14 GMT

Yes unfuddle is fine but a friend found another great place with Subversion 1 GB with SSL, including bug tracking and wiki

http://xp-dev.com/

Enjoy it

re: Excited About Unfuddle Subversion / Git Hosting and their Mac Widget ;)

David Hayden — Mon, 23 Mar 2009 14:31:06 GMT

Liam,

I can't wait to try those features. The idea of having all those features consolidated in one place is much more attractive than I first thought.

re: Excited About Unfuddle Subversion / Git Hosting and their Mac Widget ;)

Liam McLennan — Mon, 23 Mar 2009 03:58:28 GMT

I love unfuddle. The web application side of their service, with bug tracking and wiki, is one of my favourite web apps.

re: ASP.NET MVC 1.0 Released

Paul — Wed, 18 Mar 2009 17:53:56 GMT

How about some ALT.Net examples?

An ASP.Net MVC app built using NHibernate, Spring.Net, nUnit and log4Net...oh and why not PostSharp while we're at it?

:-)

re: ASP.NET MVC 1.0 Released

Budigelli — Wed, 18 Mar 2009 15:05:22 GMT

have been waiting for this :)

re: Patterns & Principles Help Me Sleep!

David Hayden — Tue, 17 Feb 2009 15:15:12 GMT

Jim,

Thanks for the spelling tip. I made the change.

re: Patterns & Principles Help Me Sleep!

Jim Cooper — Tue, 17 Feb 2009 10:10:08 GMT

That should be "pique your interest"

re: Patterns & Principles Help Me Sleep!

David Hayden — Mon, 16 Feb 2009 22:05:00 GMT

Daniel,

Yep. If you are building disposable applications ( prototypes, pilots, etc. ) then certainly having higher quality, maintainable code won't be as big of a deal as you don't have to worry about maintaining and evolving it.

Of course, how many times does a pilot or prototype become an application that needs to be maintained and evolved over a longer term than expected and then you have to deal with less quality code? And then the total cost of ownership of the application becomes much more than what would have been the price of an application with far better code quality? Happens all the time ;)

Your point is well-taken, however. There is a market for disposable applications, but the client should be made aware of the fact that they are getting a disposable application.

As you say, there is also more to developing and maintaining production systems than just having high code quality. Of course, if your code is hard to maintain, those systems won't necessarily be as effective as they could be in the long run.

re: Patterns & Principles Help Me Sleep!

David Hayden — Mon, 16 Feb 2009 21:43:40 GMT

Hey Craig,

Thanks for your comment! Your experience sounds similar to mine many years back and I think a lot of developers have experienced this situation. Sounds like you are on the right path so keep up the great work!

re: Patterns & Principles Help Me Sleep!

Stephen Rylander — Mon, 16 Feb 2009 19:46:00 GMT

Well said David. This looks like it was written in response to a certain podcast over the last month. Thanks for making a solid case for understanding principles and patterns and clarifying that real world experience with them is when they come alive.

And I too sleep much better now.

re: Patterns & Principles Help Me Sleep!

Daniel — Mon, 16 Feb 2009 19:44:46 GMT

Design patterns and principles are only the tip of the iceberg. Software architecture and processes in general can produce even more suitable and better fitting the problem. There are some cases where maintainability isnt the most important requirement or is a requirement at all ( for a pilot?).

re: Patterns & Principles Help Me Sleep!

Craig — Fri, 13 Feb 2009 22:58:16 GMT

Many thanks for this posting as I myself am having trouble sleeping at night (well sort of!) due to the same issues you have spoken about.

I have been developing web based applications since 2000 first using classic asp, then moving up to .net with vb.net then C# around 4 years ago. I have only ever worked for small software companies that have been more interested in shipping systems out of the door rather than shipping good maintainable software. I have just started my quest in trying to gain the skills that will make me become a more productive developer that is capable of producing high quality maintainable code. I have read a few books such as The Pragmatic Programmer, a new book by Neil Ford titled the Productive Programmer, C# Design patterns and downloaded the GoF patterns . I am now also looking at Bob Martins blogs articles regarding SOLID principles.

I am not saying that I am a poor developer by any means, as all my clients have been very happy with the solutions I have provided, and the code is a great deal better than a lot of the code out there. It’s just that niggling feeling that it could be so much better by applying some of the principles mentioned above. It’s not that I am looking for some kind of developer utopia , but just a better knowledge and understanding of what it takes to write good, clean maintainable code.

Unfortunately a lot of this was to taught at Uni back in 1997 and I seem to have had the misfortune to work at companies who’s developers did not care much for the afore mentioned. So its up to myself to get out there and learn those skills by reading blogs like yours and other likeminded professionals. Any maybe some time in the not too distant future I too, will be able to sleep as sound as you.

Keep up the good work.

Craig

re: An Aha Moment on MVC Validation Extensibility in DefaultModelBinder - Bye to IDataErrorInfo

Peter — Wed, 11 Feb 2009 22:35:22 GMT

This is great.

Is there a way to apply this to ADO.net Data Services so that I can combine MVVM and ADO.net Data Services?

re: ASP.NET MVC and Validation Using IDataErrorInfo and Validation Application Block

David Hayden — Wed, 11 Feb 2009 17:13:21 GMT

Thanks for the tip, bezieur. I will have to play with that this week.