Friday, January 01 2010 tips
Plain Old CLR Objects (POCOs), along with their close cousins POJOs (Plain Old JVM Objects) are often held up as the ideal for use when modelling our problem domains.
Friday, January 08 2010 tips
In my previous blog entry, Improving on POCO Properties, we looked at the benefits we can reap for our domain objects if we represent properties with dedicated helper objects instead of restricting ourselves to the usual C# syntax.
Thursday, January 14 2010 smart-code
A common need in domain modelling is to specify a range - of dates, of prices, or some other numeric measure. Typically, we model this with a pair of properties, as in this example:
Friday, January 15 2010 tips
The ISerializable blog post “The difference between continuous Integration tools and automated build tools” has a good breakdown of the difference - one does the build, the other triggers the build.
Wednesday, January 20 2010 smart-code
Sometimes I look at a piece of code and find it hard not to sigh, especially when the developer has done something the hard way.
Thursday, January 21 2010 smart-code
Monday, January 25 2010 good-samaritan
Saw something interesting at church the other morning, as the speaker was preparing her message.
Thursday, January 28 2010 professional
You don’t have to go very far to see the extent to which women are underrepresented in the IT industry - especially as software developers. Recently, I’ve started to ponder the reasons why - and, to quote Walt Kelly: We have met the enemy, and he is us