I came across the My Favourite Word website while I was browsing del.icio.us, and I had to submit an entry for sesquipedalian: This word makes me laugh, because it can be used to describe itself, as well as anyone who uses the word. It's like a self referential joke. This has been my favourite word … Continue reading Sesquipedalian
I've updated the JUnit AntiPatterns article after receiving a number of emails giving feedback on suggested improvements and new anti-patterns. I've made the following changes: Added sections for Misuse of Assertions and Redundant Assertions, and reorganised the anti-patterns that relate to assertions. Anti-pattern examples and the refactored solutions are now styled differently.
On the subject of changing jobs, here's a few points I've been considering: I'm in a stress free but relatively low-paid job as a software engineer in an insurance company. Three miles from home to the office is very handy, especially considering I often have to pick up children from nursery. However... I'm generally frustrated … Continue reading When to Change Jobs
Mike Clark mentioned my Ant dependencies article on Pragmatic Automation last week. For a low traffic site such as Exubero, it's easy to look in the referrer logs to see how that reference has spread to various other blogs. I was relatively surprised about the effect that social bookmarking has on propagating ideas. I haven't … Continue reading Pragmatic Automation and Social Bookmarking
I've updated the JUnit AntiPatterns article with a new anti-pattern: Multiple Assertions.
I've written a new article on managing Project Dependencies using Ant. From the overview: This article discusses a technique for managing the build order of separate sub-projects in a large software system purely using task dependencies within Ant scripts. Unlike other solutions, this technique for managing dependencies does not need any external tasks to those … Continue reading Project Dependencies Using Ant
JUnit AntiPatterns is an article on JUnit worst practices that I have written, in response to some scary examples of software "engineering" that I encountered during code reviews. Feedback is always welcome!