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

Popular posts from this blog

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

Accessing the UI Thread with Tasks in F#

I have a Windows Forms program written in F# that can deploy a code base to n number of sites at once (you select the sites you would like to deploy to and it goes off and completes a number of tasks (backing up current sites, various unpacking and moving of files etc... ). Once you start it, it begins it's merry journey and begins to update the UI with what has happened. At the moment this method of updating the UI is not pretty because the threads I am doing the work on can't update the UI so I perform some fiendery to make that happen (don't ask). I knew there was a better way using some newer .NET features but I just hadn't got round to having a fiddle yet. I have now found that if you use the built in Task class but break your code up in a nicer way and then chain the tasks together you can then pass the correct context into the task that you want to talk to the UI. Here's a little script to give you a feel for it. You can press the "start" butt

NESTA - Next Gen.

via nesta.org.uk Following on from an article on the BBC about Raspberry Pi, this next gen report has some interesting findings. The scariest stat which I picked out from the BBC website was "out of the 28,767 teachers who were awarded Qualified Teacher Status... in 2010, only three qualified in computing or computing science as their primary qualification" Having worked as a computer science teacher for a year in a school that was a specialist in Computing I can concur that the uptake in Comp Sci was woeful. 2 Students for A2... The other teachers backgrounds in Computer Science was also fairly woeful (most knowing a bit about Office but still a paltry amount even about that). I couldn't speak for my counterpart that I was covering however. I suspect they were fairly up on things. All in all what kills me is that Computer science is not a secondary level subject. Areas are often covered, a little in IT, a little in DT subjects (if kids choose Systems and Contr