Software is too expensive to build cheaply...

Daniel Steinberg has a note on Java.Net about testing EJBs out of the container, and wonders why people make a fuss about it. There's a simple reason: speed.

Paul Graham wrote about The Python Paradox. Unlike his earlier talk, this one actually had a good point.

Brian Duff gives a good example of a technique to get around visibility problems when unit testing. Believe it or not, this can be a good idea (and this is a strong TDD advocate saying this).

A gentle reminder to myself: don't make things more complicated than they need to be.

Esther Derby describes a notice from Gallup about the lack of recognition and appreciation in modern companies.

Hani makes a surprisingly unbilish point about wrapped exceptions. Wrapping already wrapped exceptions isn't the best idea in the world.

This technique reminds me of the children's game of "Pass the Parcel", where you put multiple layers of wrapping on a gift, and the children never know when they will reach the last one.

I'm as guilty of this as the next person, but I think in future I will modify the constructors of my wrapping exceptions so that if a cause already exists, it uses that as the cause, not the one supplied...

(FWIW, I'm not against wrapping exceptions; what is an ObjectNotFound at one layer is a ConfigurationException at another, and should be reflected as such).

This may, of course, just be a stupid idea, but it's worth exploring.

The JavaMail API is a nice, simple, and effective API. But it's got one problem: it's a bugger to unit test. This is mostly because (unlike most other Sun Java APIs) there are no real interfaces in place, which makes it hard to mock pieces out. An excellent solution to this problem is Dumbster.

On Cedric's latest entry he complains about statics, and quite rightly. However, one of the commentators missed the point.