My perception of hard drives is that they are slow, bulky, power hungry, put out too much heat, noisy, unreliable and prone to catastrophic failure instead of graceful degradation. Given a choice I’d rather not store my precious data on such a device.
I long for the day when an evil genius invents a solid state device the size of a matchbox that stores several TB’s uses the same power as ram and will put those ancient spinning things to shame when it comes to reliability.
Anybody know of any solid state devices that are showing promise at the developmental stage?
Here’s someone that agrees with me
I don’t like my iPod or my iPod shuffle, I hate iTunes and can’t
find an alternative. I recently downloaded the latest version of iTunes
and it spat the dummy when I connected the shuffle saying that the
firmware needed updating.
I went to download the firmware at 53MB! for a shuffle firmware update Apple get my bloatware 2005 nomination.
I am quite particular when it comes to arranging my MP3 collection
and so I would like to be able to transfer files to a portable MP3
player using Windows explorer and preserve the tree structure, again with
apple ipods this is a big no no.
That said they do look great.
Scott Hansleman, Joe Stagner and Omar have put together a podcast with some useful insight on the DasBlog blogging engine. The quality is less than perfect but the content is great. Check it out if you want to learn more.
The short answer is if making changes to your production environment is costly then getting changes right the first time becomes vital. If your delivering software to a client then you will build confidence with the client if you deliver ‘bug free’ software. If you must peform business as usual testing or as some call it regression testing then a test driven development approach may lessen this burden with time.
An equally important question is when wouldn’t you use test driven development? Well when there is relatively little expense in changing the production environment and when bugs making it into the production environment don’t represent a disaster. Prototyping would not require it nor would temporary applications.
Do you need nUnit to do test driven development? No, all you need is to be able to create something that will test your code, this could be a vbs script, windows app or a keyboard macro. nUnit is just a tool that takes care of the more mundane aspects of TDD. Test Driven Development is an approach not a toolset.
To me it really comes into it’s own when you are constructing components/services that will be used by other developers. The tests will serve two purposes they will prove your code works (hopefully) and they will be examples on how to use your components and services.