Tuesday, May 29, 2007

Grinding away

Google sourcers are extremely nice over the phone as well. Even if I fail later on I must say that the very professional and, I can't find any other word for it, nice behavior I was greeted with when talking the the google representative. Now it can take ages until a recruting coordinator gets on my case, and I'm actually not certain I want to join google anyway - it might require relocation and so on. But still it's a nice feeling to be courted by the cutest chick on the block, so to speak :)

At the moment I'm grinding away the final part of the code that saves element and infotrons (if present) in the current page. And I know exactly how to manage loading as well, which if I'm lucky will be quite similar to how I render the final vanilla HTML page as well. Don't touch that dial.

Wednesday, May 23, 2007

I've been googled!

Last Friday a recruiter working for google sent me a very nice and friendly inMail on my LinkedIn account. It was a pretty surreal experience. To begin with I didn't know that google actively searched for people, but rather sifted through the tons of incoming applications.

Today we have a scheduled phone meeting, which will probably go OK. Now, if you're not up to speed with the way google works when recruiting this might seems like my big chance. Not so.

My research have confirmed the following points;

1) Google continually searches for potential candidates to various positions withing the company, Note the word 'potential'.
2) Even if you pass the first and second interview (which will be increasingly challenging), the next steps are a grueling two-day interview marathon, where up to 20 different people will challenge you on a variety of topics - not necessarily ones relevant to the position you think they want you for.
3) Every single one of these people will have to recommend you to a final decision-maker, who is not part of the actual interview process who can drop you for "cultural incompatibility" or some such reason.
4) The process can and will take several months to finish, with many irregular starts and stops between start and rejection.

On top of this, I'm not even actively seeking a new job. I'm trying to create my own company with the composer!

To google's defense, it seems that their recruitment process is intended to make pretty certain that they don't recruit any bad apples, even if that means that they'll skip a few good ones in the mean time.

My bet is that I'll pass the two first interview (by phone, since I'm in Sweden and the recruiter - sorry, technical sourcer - is in Denver, for some reason), and then fail miserably on the first day of face-to-face interviews when it is unearthed that I never found George R.R. Martin's books particularly good. Another possible end is that they finish two whole face-to-face ingterview thing, give thumbs up, hide for seven months, and finally send me a machine-generated rejection letter for the wrong position, citing provably false shortcomings.

Or, who know, me and my family might gets whisked out on a magic carpet and relocated - cats and all - near Mountain View.

And _then_ I can sell the composer to google (wringing hands)

Monday, May 21, 2007

Contain the container

I have been wrestling with using draw2d for over a month now (OK, having a vacation in between, but anyway), especially with hierarchic containers. I wanted to make it easy to create a small "group" of things, say; a label, a textfield and an image, and then drop the whole things inside a larger container which has lots of other form elements in it, and most importantly to resize and position the "group" inside the larger container in a simple way.

After losing my mind the third time I finally registered with the forum and wrote a short plea for help. I didn't expect much, after all draw2d is a on-person project (as are all other projects, for that matter), but the next day Andreas Herz had written a fix for hierarchical components just like that. And it worked and it was beautiful. I really hope he puts up the paypal donation button somewhere on his site, so I can thank him properly.

The only downside was that draw2d uses a separate hierarchy beside the actual DOM, so that all 'figures' sit flat beside each other, and move by draw2d logic depending on how draw2d thinks which one is inside the other. I have now learned to live with this, and written some extra logic to handle this, especially for the GenericForm blueprint.

So after some fairly minor amount of hacking I was able to get back to where I was a month ago, but now with a workable and intuitive GUI, with a toolbar and everything.

Next steps are to finally finish the load/save page stuff, so that the created pages can be serialized. And after that comes the holy grail of export as CMS module, with joomla and MAJ as the first CMS targets.