8 Dec
2008

Assembly Partioning Advice

Patrick Smacchia wrote an excellent post on how you should partition your code in multiple assemblies. Because this is one of those subjects that i’m pretty opinionated about, i figured i’d quickly recap the valid and invalid reasons for creating assemblies that Patrick highlighted. Valid reasons for creating a new assembly: Tier separation: separating the […]

Read More
2 Dec
2008

Do Not Litter Your Code With Null Checks

Just read the following post on the performance of try/catch and throwing exceptions. In the author’s small (and completely unrepresentative of real-world scenarios) performance tests, it showed that throwing exceptions is a quite costly operation. Ah… if only it were that simple. Throwing an exception is indeed a costly operation, compared to most other statements. […]

Read More
2 Dec
2008

How Do You Deal With Common Infrastructure Code For Multiple Projects?

Here’s the situation: a couple of months ago we started developing according to a new architecture. Obviously, you need infrastructure code for this. For the first project, we just put the infrastructure code into the project’s solution and everything was easy. We could make changes as we needed them, and it enabled us to ‘grow’ […]

Read More
28 Nov
2008

Genesis: Bridging The Gap Between Requirements And Code

I just read the following post by Robert C. Martin. In it, he says the following: If you can enumerate the states, and events, then you know the number of paths through the system. So if Given/When/Then statements are truly nothing more than state transitions, all we need to do is enumerate the number of […]

Read More