I have not considered a Nokia phone in years. Who needs a phone that is three or more years out of date?
I just bought a Nokia back in May after a few weeks looking at the available options because, and this was the primary criteria, it worked the best as a phone. The sound quality was superb and reception was excellent. The smart-ness off the phone was a distant third in priority, behind the usability of the phone and the usability of the camera (in my job it's handy to be able to take site photos at any time).
This is interesting, but it doesn't seem to match what I have seen.
Last week, as an experiment I switched the (Sing-Tel) SIM in my unlocked iPhone (purchased in Singapore unlocked) with one from another company (M1). It worked straight away. I actually made a call to test. I certainly didn't log into itunes.... Admittedly I was in Australia at the time, so there may have been something to that (perhaps the global roam overrides the lock?) but I would have thought it would have made it less likely to work, not more....
So what gives?
This rocks, though. My laptop stutters when I have Pidgin, Firefox and Thunderbird running at the same time; I hope that I will see a much smoother X performance with this next version.
Not to troll, but I had a similar experience that I fixed by uninstalling Firefox in favor of Midori, although it looks like I may be giving this Uzbl thing mentioned in another article a spin shortly. I'm not sure whether there's legitimacy to the Firefox devs' complaints about X, but I don't really care if there are browsers out there that don't bring my whole system to a halt to load a webpage.
Obviously, when you are in a position of authority, you will know to not hire those people.
I have learned in my working life (I'm 51, and have always had a job since the age of 15) that one does not work in isolation, and the people who do best are people who surround themselves with competent and trusted colleagues: teams, essentially. The team can be: Program director, project manager A, project manager B, project A programmers 1, 2, and 3, project B programmers 1, 2, 3, QA staff 1, 2, 3, Office Admin. - about a dozen people. How did programmer B3 get on the team? Because programmer B1 knew him in university, and knows he does good work. QA dude #2 is there because lead QA 1 was hired by project manager A who was in a school play with QA 1 and knows what kind of a critical mind he has.
It goes on from there.
Your critique, while interesting, and certainly valuable, is far off the mark of the Real World. We are a social species and our social administration is always done by people working with people. You can be the lone programmer, but if you need your entry badge renewed, you better be nice to the Admin. You can be the lone programmer, but if you're a dick, you will go from one project to another, and will be consistently passed over by the better connected and more socially adept programmers.
THAT is the real world - it is not one of individuals - it is one of societies of individuals. With humans, it is not the individual who is fittest, but the group that is fittest...
And these groups form at a young age and continue through life. Young people should nurture these relationships and develop tight social networks. It can mean the difference between a daily grind and a worthwhile vocation.
RS
Many people are unenthusiastic about their work.