.NET at 9.400 ft above sea level

Everytime I have to convert a string to an integer I use int.Parse() instead of Convert.Int32(). Until today, I basically recommended it because it looked more O-O to me (besides, I get the chance to pick my Java pals because int behaves more like a real class in C# ;-). But today Clemens Vasters, a fellow RD, gave me a really sound reason for doing so: int is a higher level abstraction than Int32 and, by default, higher level abstractions are friends of the (business) developer. Nice one, Clemens.

In countries like mine, it is very important to have entry level tools for developers to adopt any new technology. That's why Web Matrix plays such an important role down here. And that's why I get so excited when Scott Guthrie comments that they are about to deploy a new version of the thing. I look forward to it.

I have no problem admitting that I learnt object oriented programming with Bruce Eckel's Thinking in Java. Even more, I am absolutely convinced that if from time to time I manage to look "solidly backgrounded" in O-O it is due to what I learnt in Thinking in Java. Third edition just received a Jolt award (I learnt while moving from 1st to 2nd Ed, time do fly, sigh). Thinking in C# is in the works and I am looking forward to it. In the mean time, Bruce has started his web log and it's got some mind opening content, go browse around, you won't repent.

I've forgotten to mention what I use to synchronize my (so far very light) work on NHibernate: TortoiseCVS. Once installed, it becomes part of Windows Explorer right-click menu, so you can check out, update, commit, etc. from the comfort of your explorer. Cool.

Make it +2, as I already made a posting on this very subject. I guess I cannot get to be as emphatic as David Stone in NUnit Rocks! But I can be redundant all right: use NUnit, your family will thank you.

A title taken from Jill Nicola et al.'s Streamlined Object Modeling.

It's been a few days since my last post. Let me explain why: from time to time Objeq actually demands me to do some billable work ;-). It's funny but, as passionate as I am for VM architectures, low level design patterns, and down-to-earth coding, nowadays I usually get paid for determining the business value of a software project, doing high level project design, assessing risk and generally helping teams start a project on the right foot. What they call the envisioning phase in MSF.