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

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