I read a post a few weeks ago about feeling the pain of some software development practises including such things as untestable code and tight coupling. I'd really like to post a link to it however Google Reader search isn't at all helping in helping me re find it. But first some history.
First thing you should when setting up a new machine, install source control.
So there's been a lot of commenting back and forth at the moment concerning the new Microsoft Entity Framework and especially the "vote of no confidence" by members of the Alt.Net and DDD communities. This I can understand, the current EF certainly doesn't meet any of their requirements for a toolset or framework.
Originally when I wrote the previous post I was all fired up to start an MVC CMS as way to get myself update to data with some new things, namely the new MVC framework, JQuery and Silverlight. However the more I thought about it the more I realised the standard view factory doesn't lend itself well completely customisable pages, one of the great things about MVC is that we could switch out the view engine for something that could work. However I feel this defeats a lot of the purpose of the exercise.
Wow, that took a lot longer than expected. Vodafone took every single day of their "up to three weeks for your broadband to be connected". In the last few weeks I've taken up my new job and am settling in fairly well. Part of the new job entails evaluating new technologies (more so than I usual do) for use within the company. After reading over the Entity Framework I have mixed feelings.Visual designers are always pretty much as many have people have pointed out they scale terribly, the strongly typed querying via LINQ, but hopefully that can come to libraries such as NHibernate soon. The lack of implicit lazy load is also really annoying.