Inner Drive Software

My colleague Cameron Beatley sent me this handy comparison guide for programming languages.

Just this morning I wrote about choosing a class over a struct to take advantage of inheritance and abstractness. It turns out, I was wrong.

I've encountered a problem familiar to veteran C# developers: whether to use a class or a struct for a particular design. So I'm going to follow my own advice and develop first for elegance and second for execution speed.

Genius Boy here just spent ten minutes debugging a class because I used the private field directly inside the class, instead of the property accessor method.

The Inner Drive Extensible Architecture™ contains a very useful namespace called Quantitative that contains classes and interfaces to use in measuring things. Essentially, there is a trio of interfaces, IQuantity, IUnit, and IPhenomenon, that allow you to create and convert any kind of measurements. The principal implementation of IQuantity is the Numeric structure.

I've finally added an explanation of Evolutionary Delivery to my corporate site. I wrote this as part of a proposal to a client in September, and for reasons that passeth understanding, I neglected to publish it online.

By the way, I write software for a living, so if you're reading this and realize you need a small, agile development team for a .NET project, send us a message.

An example of a piece of code that desperately needs refactoring.

Read Microsoft's Framework Design Guidelines, written by the guys who wrote the .NET Framework.

Compiler warnings tell you stuff you need to know. Read them.