Skip to main content

The big choice

By the gods themselves. It's time for the big choice again. My phone can be upgraded tomorrow.?

I currently have 3 choices in the pipeline.?

  • Motorola Atrix
  • Samsung SII
  • Apple White iPhone and iPad combi
It's a hard choice. My reasoning behind the selections are...?

The Motorola Atrix is a nice enough phone, very sturdy and has a nice screen to look at. I have had some time using it and one of my worries is that the batt life seems a little short (I have heard this of the SII as well though). I like that the deal comes with the work and play kit although I wish it came with that Laptop attachment instead as I don't really need a computer on my television downstairs, that's what my 50 computers knocking around the house can already do and I like to watch tele whilst surfing. It's dual core, high res and is currently out now so is an easy choice. I could also get the cost of my contract reduced most likely as well...

The Samsung SII... Lord of the Android horde. It's well known that this is truly the cream of the Android crop. There are so many cool things about this phone it's hard to list them. How about Samsungs facility to let you log on to the phone from the net and carry out file management and read text messages! Wicked (although I would worry about security perhaps). The phone has a high rez screen, is super fast and is supposed to extremely slick. I could probably keep on my current contract and get this as an upgrade. The biggest curse is that the Orange Shop has it as a "coming soon" in the upgrade section. Boo!

The?Apple White iPhone and iPad combi. Ah how tempting. I would absolutely love the iPad. The biggest bain of this deal is that there is a ?99 upfront cost and also I would have to up my contract by ?15.... I am also very tied in to Android services in general with gmail, contacts, tasks, docs and just about every other service. Leaving them would be upsetting.?

Anyway time will tell. (Well, we will see tomorrow!)

Comments

Post a Comment

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.
Post a Comment
Read more

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi
Post a Comment
Read more

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second
Post a Comment
Read more