For a few years, I had a crappy mobile phone. I used it for what I thought was the primary function of owning a phone. You know, make and receive calls. For this purpose, the phone I had was quite satisfactory.
I had an ulterior motive as well for not wanting a new phone.
I had an interesting phone chat with a friend based in Bangalore, India using Skype (I am based in Australia). While not going into specifics, he outlined his take home pay and as he was saying it, it hit me like a thunderbolt.
His take home pay was only 10% less than my take home pay.
In news that is sure to drive further the fragmentation issues of development using Java ME, Motorola has announced that it is going to develop its version of Java ME under the Apache license. As the report says: "it's not clear whether the Motorola and Sun projects are complementary or competing".
I was browsing through the Sun supplied Location API examples in the latest Wireless Toolkit when I came upon this:
Ok, so it's just a few lines of code that are, to put it mildly, exceeding the generally accepted 80 character limit.
Disclaimer: UNLIKE my previous article on interviewing, I am not criticizing any company, processes or interviewers. This post is JUST a blog entry and documents my inability to clear a technical interview.
One of the benefits of Sun's decision to open source Java ME (along with the rest of the Java brand, but I am concentrating on Java ME), especially for an author and writer, is the ability to peek inside the code to understand what's going on.
JCP has quietly released the 1.2 API specification for MMAPI (JSR 135). This is only a maintenance release and contains mainly documentation changes in the API.
In fact, last time I checked, I wasn't a 'mock' anything. I get 'mocked' a lot for my photograph above, but that's the maximum 'mocking' in my life sadly.
So why does Javablogs.com classify me as a mock Sun employee?
If Sun would like to offer me a position, I will be more than happy to call myself a mock Sun employee.
If you have read my previous entry on a 30 second guide to using AJAX, you know that it was a surprise to me that implementing AJAX is so simple (There were other lessons in that entry too, about how much hype driven AJAX really is and why there is a whole market for AJAX that should really be the DHTML and Javascr