Java Thinking

A friend contacted me for advice. He was having trouble writing a test for some code. I asked him to send me the code and the test so I could see what was going on. I encounter this problem quite frequently, so I thought I'd post one of my responses... Okay, here is where I think you are going wrong, and when writing tests becomes hard, it’s usually because of this. It’s important to layer your applications. Web/Services/DB – at least conceptually. What you have is a class that does everything. Web and Service. No-one can reuse your file processing logic without using the web, not even tests! A nice way to code would be to: Write a UNIT test that attempts to process a file. It passes in a file X and asserts that the result is Y. It won’t compile because you haven’t written the file processing code yet! Now you write the service which processes the file The test will compile and run now, but probably fail because you forgot something. Now you can fix your service And

My wife has had a Samsung Galaxy S1 Android phone for over a year now and its been great. Recently though, she'd been having terrible battery performance and had noticed that after charging the phone overnight, it was only at 50% in the morning. My first thought was to buy a new battery, but then I figured I'd try updating the firmware first. Thats when I discovered that windows couldn't recognise the device!! This was a big issue - how could I get all of her photos off the phone? Solutions: Quite by accident, she plugged her phone into an iCoustic USB charger that we got with an iPod accessory pack - this fully charged the battery and now there are no battery issues. She'd been using my iPad USB charger previously and for some reason, this makes a difference. I realized that when syncing the phone with Kies I wasn't using the original USB cable that came with the phone. We'd been using a third party cable we'd bought after losing the original one. Sinc