Friday, February 11, 2005

The Job Market Tightens for Developers

Based on my small sample, it seems to me like the job market is the strongest since the Internet bubble burst. For the first time since then, I don't personally know anyone who is out of work. Also, my company has been trying to hire a junior level and mid level Java programmer in the RTP area, and we have only received just a few resumes - after posting on Monster and the corporate site. Two years ago, I was flooded with resumes after a similar posting.

Hope that trend continues. I wonder if anyone else has other data to confirm my theory.

Thursday, February 10, 2005

Mapquest, Eat Your Heart Out

The beginning of the end came when Mapquest removed the My Mapquest feature. I only had a dozen maps in there. Thanks for not telling me before you deleted them.



But now it's over. I've found a new, better map provider.



Google has done it again, this time with Google Maps.



Just enter an address or the name of a location. Here, I've searched for "New England Aquarium, Boston, MA":







There are two things I would like to see with Google maps. First, I need one-way streets to be labeled. In cities like Boston, there's just no getting around without knowing the one-ways. Second, I'd like to have a search for finding my destination after selecting "To here". In the example above, I would like to type "Fire and Ice, Boston, MA" in the box; Google should then present me a list of choices. I pick one, and the directions are drawn on the map.



Good luck, Mapquest.

Wednesday, February 9, 2005

Redefining Cool

If you are not using sage on Firefox, you are just not cool.

Tuesday, February 8, 2005

The Cuckoo's Egg

I was reminded yesterday of Cliff Stoll's book, The Cuckoo's Egg. This book is an easy read and it is so entertaining that I read it cover-to-cover in 2 days. I recommend it to anyone who has an interest in systems or programming, or hacking, or who just enjoys a good mystery.Buy it. Read it. Enjoy.

Monday, February 7, 2005

The Importance of the Tivo API

I took the Tivo Java API for a test drive recently, not because I thought I had the next killer Tivo app, but because I think the API itself could prove to be an important development.



I don't think it's important for the reason most developers will point out - it empowers developers to write applications that run on a Tivo (which is really a linux box under the covers). It is important because developers everywhere can now write applications for a home appliance.



We have a Tivo at home, and my wife and I use it just like any other appliance or electronic device that isn't a computer; we turn it on and use it: record shows, watch shows, change channels. We don't think about it being a computer inside.



In reality, most users don't think about it being a computer - most don't know how it works. (Of course, they don't know how their computer works either, but they know a computer is a computer.) They don't recognize their Tivo as a computer - it's just a Tivo. It records things. It's an appliance, taking its place alongside the family DVD player.



Tivo is the first mainstream appliance that allows home users not only to dictate how they use it, but to dictate what they use on it. Users can now extend their tivo to show them virtually anything, from a grocery list to the latest RSS feeds to games written for Tivo.



"Ho hum." you say. "The Tivo might be an appliance, but other appliances don't need an API." Well, maybe you're right. Maybe Tivo is just using developers to find a way to sell more Tivos. (And developers will have to go through Tivo get their applications deployed to the mainstream user base.)



But maybe the Tivo isn't the only appliance that could benefit from a public programming interface. I certainly don't want to run custom code on my coffee maker, but it's not out of the question that other applicances will take on more traits of a Tivo in terms of user programming and control.



And, in case you're wondering, the API is pretty good. I wrote a simple application in just a few minutes. It doesn't offer hooks into the really interesting Tivo data, like season passes and what's queued to be recorded, but it's a start...

Wednesday, February 2, 2005

Geeks Really do get Chicks

And here is proof from www.wickedlysmart.com:

Tuesday, February 1, 2005

Politics-Oriented Software Development

This is a very funny, but surprisingly useful guide on politics and software development. My favorite part:



"9. Overtime only counts when people see it.



It's usually better to do overtime in the evening than the morning, if there are more people around to see it. Weekend overtime is usually pointless since there are rarely witnesses.



Remember that you're not just being visible to your boss, but the office as a whole. Your overtime is useless to him unless it's visible to his boss, or else other people who contribute to your team's reputation.



Keep to the minimum possible. Remember that the earliest part is most valuable since there are more witnesses: better to do half an hour Monday to Thursday than two hours on Wednesday. It also sounds better to say: 'I've worked late four nights this week.' No-one will be keeping track that closely anyway."