Skip to main content

My Phone Timeline

We were talking yesterday about the phones we owned so I thought I would list my phone timeline. I have had some truly amazing phones and some fairly mediocre ones too!

My phone timeline (not including the approx 150 I have now from collecting old phones)


  • Motorola MR201 - I dispatched of this beast almost immediately, it could store 10 SMS and didn't like the phone number to the SMS
  • Ericsson PF768 - I spent hours creating ring tones on this phone. Such a little beauty. 
  • Siemens C25 - This was a brilliant phone, it had a wicked 3d maze game on it. 
  • Nokia 702 - An absolute classic! 
  • Nokia 7110 - I now have a giant box full of these, I used to love playing wap games on them and don't forget about tennis. 
  • Motorola Timeport 250 - This was the first phone that I had where I thought, this is the future, wow
  • Ericsson T68 - A cool phone but fairly poor in terms of usability. I never really loved it. 
  • Nokia NGage - A true obscenity but I had some amazing games on it (Elder Scrolls, Tony Hawks)
  • Orange SPV - The first Windows phone (in the UK at least)
  • Orange SPV C500 - I loved these SPVs, they did everything for me. 
  • Orange SPV C550 - I loved these SPVs, they did everything for me. 
  • Samsung U500 - This phone was so so thin and had an amazing camera. My only real dislike was the circular design of the menu navigator. I was also dissappointed moving from a smart phone back to something that had very few features.
  • Nokia N70 - Probably my favourite phone when I think about it. It had absolutely everything. 
  • Sony Ericsson c510 - A very close second to my favourite phone. At this time, I think the phone manufacturers had really cracked candy bar phones. Incredible!
  • HTC Hero - My first Android phone, a brilliant phone. When I look at it now it looks like a prop from Battlestar Galactica!
  • Samsung Galaxy S2 - Such a good phone. Wowzers
  • Nokia 1020 - My current phone, I really like it. The camera is far and away the best I have ever seen on a phone. My only gripe is that so few things are compatible with Windows phone which is a real pity as the OS is fairly pleasant. 

Comments

Popular posts from this blog

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

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

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