Sunday, 8 July 2007

Model View Controller ?? Model View Presenter

Jean Paul Boodhoo explains what the Model View Presenter design pattern is and what's the difference between it and Model View Controller. I've never been a big fun of MVC because it tightly couples View and Model.

Great book: C# via CLR

As I mentioned earlier I always wanted to read C# via CLR by Jeffrey Richter. Finally I got it a few months ago and while I was sick I read it. I think it's just brilliant because:
  • I like the way Jeffery explains problems.He is strict and precise whenever it's needed but no more.
  • As far as I know he is not a Microsoft employee which lets him express criticism of everything that deserves it.
  • It reveals lots of things that you will never be aware of unless you start thinking in an illogical way. Unfortunately CLR and/or C# not always behave in a predictable way.
  • The books touches nearly all the .NET internals that you can come across during your everyday job as long as you don't work on compilers and runtimes :).

Thursday, 5 July 2007

You always struggle with formatting strings?

Check this out. It's a great crib sheet and I've even downloaded it to my machine. Just in case it disappears from the Internet :).

Monday, 2 July 2007

Rough but enough explanation of WS-* standards

Michele Leroux Bustamante presents a rather short article about WS-* standards. It's great because it allows you to see the big picture and how all of these standards fit together. There are so many of them that it's easy to get lost if you don't deal with them directly on daily basis.

Tuesday, 26 June 2007

What kind of software development have you experienced?

Scott Berkun published his list of unofficial software methodologies :). Regarding these mentioned by him I've experienced: ADD, CDD, CYAE . Don't forget to check comments, especially: NMP, CPM and NIH.

Silverlight is getting smaller and smaller...

The BCL team has announced that they've removed quite a few collections from the Silverlight version of the framework. It makes prefect sense to remove all non-generic classes but I can get why they've removed Stack<T> and Queue<T> as well. These 2 are very useful and people should not write them from scratch. That defeats the whole purpose of the .NET framework - leverage it. I don't know all the numbers but I can imagine it wouldn't harm Silverlight if they left them.

Wednesday, 20 June 2007