Archive for the 'Implementation' Category

Exception Handling Policy – Logging Exceptions
Monday, July 13th, 2009

This is the last part of my series on exception handling which will deal with logging exceptions and other noteworthy events.

A summary of the series:

Throwing Exceptions Using Assertions Catching Exceptions Logging Exceptions (this one)

General guidelines

We’ll start off with a few general guidelines for [...]

Exception Handling Policy – Catching Exceptions
Monday, July 6th, 2009

This is the third installment in my series on sensible exception handling and will cover when and how to catch exceptions.

To quickly summarize, the series looks as follows:

Throwing Exceptions Using Assertions Catching Exceptions (this one) Logging Exceptions

The information in this post is divided [...]

Exception Handling Policy – Using Assertions
Monday, June 29th, 2009

This is the second part in a series of four on exception handling and it focuses on an area related to exceptions — assertions.

A quick summary of posts in this series:

Throwing Exceptions Using Assertions (this one) Catching Exceptions Logging Exceptions

Guidelines for assertions

An assertion [...]

Exception Handling Policy – Throwing Exceptions
Monday, June 22nd, 2009

This is the first post in a series of four on exception handling.

The series will cover what I think is a good and sound strategy for handling exceptions and errors in your application.

It is written with Java in mind, but is applicable to most languages which feature exceptions.

A quick summary of the coming posts:

Throwing Exceptions [...]

Scope control
Thursday, June 21st, 2007

Again, the book Test-Driven Development: By Example by Kent Beck provides me with an eye-opening experience. It explains how test-driven development is useful for scope control when developing.

Refactoring vs performance optimization
Wednesday, August 30th, 2006

The thought popped up into my mind a while ago, that there is actually a striking similarity between refactoring and performance optimization.

Full statement coverage
Tuesday, August 15th, 2006

When I read Ron Jeffries Soduko articles, I was wondering why he was writing such sloppy unit tests. He didn’t seem to test even half of the code he wrote. A short email conversation later I had realized that he of course wasn’t sloppy, but rather just much more clever than I was (not that surprising, really). ;-)

Why Doing Nothing May Crash Your Program
Tuesday, June 21st, 2005

Visual Basic 6 programmers are protected from the “real world”. The upside is that VB programmers really can get much more useful things done in less time, the downside is that there are limits for what you can do in VB… and the fact that VB’s behavior sometimes can be really, really strange.