If there were a place between enthusiast and Geek, I think that is where you will find me. You see, I am never satisfied with the default configuration on any device that I own. That is sometimes good but for the most part leads me to break things first before I even know how to fix them.
I own a Galaxy S currently and as things stand I have flashed the poor device with about 12 different variants of Ice Cream Sandwich that wasn’t made available by Samsung. I previously owned the Nokia 5230 which I flashed with different custom ROMs that I got from the forums of Mobile Phone Talk, that enabled me to do most things that the default Symbian OS installed by Nokia didn’t allow me to do (Yes, custom roms on Symbian!).
You see, I have a perfectionist persona and I always want every part of the device to be exactly what I want it to be. It is one of the reasons that I initially went into programming. Something that still keeps me going today is that I always want to see what is behind the scenes.
With all I’ve said above there’s a very huge catch to all my “experiments” both on mobile and on the computer. The number one thing that I can classify as curse is that most times after tinkering with my devices, things don’t work the way I want them to be or even if they work, it are riddled with bugs.
The number one example of this is that I’m currently running the Windows 8 consumer preview on my computer and there are at least 5 bugs that constantly plague me all because i’m using beta software instead of using a stable version of Windows like any regular Joe would. But hey, I’m not a regular Joe!
The Second thing that I can identify is that because I use up-to-date content about 90% of the time, I tend to think that this is the same for everybody. A classic example was this guy that came to me with an Android phone and told me that his phone had a problem. The first question I asked him was what version of Android he had on it. The guy had no clue!
That wasn’t all either. He kept telling me that the phone had a fault because all the Java applications that he downloaded were not working. I had to sit him down and explain to him that Android does not use “Jar” files. For your information, he was running Android version 2.1 Eclair on the phone (Bad, eh? I know!).
The Third and final curse is when things don’t eventually work or when I spoil something because of my tweaking. I recently had a friend give me his N60,000 Samsung Galaxy S Plus that he broke just a few hours after he bought it. He flashed a wrong build of Android that wasn’t made for the device and to sum it up the device did not live to tell the tale today.
I may not be a full blown geek in accordance with “international” standards, but I also know that I’m still higher than the regular guy in my quest for total knowledge of my devices. Sure on my journey, different gadgets or components of gadgets have gone to the great underworld by my hands. However, I can say in retrospect that it is well worth it. So what is your own curse? Remember that we are all geeks at something.