Job Search

Like me, most of us are about to graduate and I am sure that we all want better paid jobs or actually find a job since we will be having a new degree. Well, while I was looking for jobs I got across a really cool job search engine. It is interesting how google is trying to be on top in search engine industry because this tool is powered by them. It is nothing like the famous Monster or Careerbuilder. I could say it is less hassle to work on and actually have better search results.

I am not sure what technology stays behind it, but it pretty much just asks you the type of job city and money that you would like to be paid. From that point the engine searches through different job listing sites and displays them based on the time on which they were posted. For example if you search for an IT job you will get results coming from Dice, Monster, CareerBuilder and even from company's itself.

I think this tool is pretty cool because it takes away the hassle of creating an account and spend time in registering. In addition it pulls listings from multiple resources so you do not have be registered in multiple places. The name of the site is indeed. com

Runningman: Gears, Ajax, and Comet

In the GoogleLab API, there are several awesome examples of apps you can build using Gears. For those of you that don't know what Google Gears is, heres a brief history. Google experimented with offline applications and came to a few conclusions. As they developed offline-enabled applications, they typically found the following design flaws:

• isolating the data layer
• deciding which features to implement offline (connection strategy)
• deciding on the app's modality
• implementing data synchronization

What an offline application can do is allow a user to interact with a web-service and to be productive while a connection is unavailable. Gears localizes several server features to give the user as rich of an experience as possible. Items that are localized on the client side include a data switch, server data layer, local data later, database, and a sync engine. While that may seem like a lot of stress to put on the client side, they have modules included that lighten the work load and only marginally decrease the speed of the application. When a connection is made with a server, Gears uses either Ajax or Comet to transfer data.

So back to these cool applications. The one I read into was called Runningman. Runningman is a program designed for the Android OS that allows a runner to time their run and through the use of the phones GPS, track their path on a Google Map. The group working on the mountian biking website might benefit from this example, since they are doing something very similar.

The Runningman application includes Gears and contains a full code sample that you can download and manipulate on your own. They even have a full tutorial telling you have to write the program. Way cool! As you walk through the tutorial, they show you how Gears lets you create a desktop shortcut, use Comet to update data, use the Gears Localsever to operate offline, and much more.