Spring has had a really nice unit test framework available for a while now, but the documentation can be a bit daunting. Here’s a super-simple example of adding dependency injection to an integration test:
The topic for this “Software Development Mantras” post is “defensibility.”
First, let me introduce the concept of “TIMTOWDI” (pronounced “tim-toady”). It’s an acronym for “there is more than one way to do it,” and software development may be unique in that for any given task, this holds true.
This is the first in (what may be a series) of posts where I’ll share some concepts, or mantras, that I’ve found helpful in my experiences with software development.
The following are some of the lowest hanging fruit. These should be (but aren’t necessarily) common sense for all software developers:
Installing Karmic Koala from a USB drive proved to be a bit less than effortless. First off the http and ftp servers for the netbook-reloaded ISO images were really slow, and for some odd reason there aren’t any bittorrent links for the netbook-reloaded image. You need to go to http://releases.ubuntu.com/9.10/ to find the .torrent link (which is here).
The installation instructions need some editing, too, but the jist is if you’ve got a linux box, use usb-creator — and don’t panic when the usb-creator main window disappears (and doesn’t get replaced with a progress window for several minutes).
So the main glitch was wireless — it didn’t work out of the box on my HP 110 netbook.