Viewing posts from October, 2005
A small gotcha witha too smart printer.
I have a PostScript capable printer (Lexmark C510) connected to one computer and I ofter print to there from my notebook trough CUPS. I noted that sometimes the printer would blink "busy" lamp and then go back to "ready" without printing anything. Usually I just printed to a PS file, converted it to PDF with ps2pdf and then it worked. (I had no time to investigate then)
Now, I found, what the problem was - some apps on the notebook were generating Letter size Postscript and the printer only had A4 paper, so it simply ignored the data after parsing it. Doh!
Also today I got a call from Google office in Dublin - I am flying there next Thursday, stay at a hotel overnight and then there will be an on-site interview on Friday afternoon and on Saturday I will be on my way back home.
Looking forward to that challenge.
Planning to buy a Canon Digital Rebel XT as my first SLR and can't decide on the lenses. What I know is that my current camera (Sony F717) has a fixed lens that is equivalent to 24-125mm and I would like to have a lens set that is wider at both ends.
I am already decided to take a Canon 50mm f/1.8 II prime lens - for portraits and for low light situations (in-house sports, ...). All experts say that this is a must have lens - it is very fast and gives wonderfully crisp pictures for a price of 75-80$.
Now I can't decide whether to buy the kit lens (Canon EF-S 18-55mm f/3.5-5.6) or go and buy something better right in the beginning. After reading a comprehensive review of the best Canon lenses from Bob Atkins I am more confused then before.
One of the best compromise "walking" lenses is actually narrower then Sony's range - Canon EF 28-105/3.5-4.5 USM. Buying this lens would mean that after some time I will probably buy the kit lens or a 500-600$ lens for that wide end and a Canon EF 75-300/4-5.6 for the telephoto end. That is a total of 4 lenses - what a waste!
Now, if I would relax myself a bit on the money, I would take a Canon EF-S 17-85/3.5-5.6 USM and then extend to the telephoto end with Canon EF 75-300/4-5.6 or (new, much better, more expensive) Canon EF 70-300/4-5.6 IS USM.
Lets see what the numbers say:
Option 1 - kit lens + Canon EF 28-105/3.5-4.5 USM + Canon EF 75-300/4-5.6 = 100$ + 200$ + 150$ (or 450$ with IS and USM) = 450$
Option 2 - Canon EF-S 17-85/3.5-5.6 USM + Canon EF 75-300/4-5.6 = 520$ + 150$ (or 650$ for the great new Canon EF 70-300/4-5.6 IS USM) = 670$
My start-up lens choices vary from the recommended 350$ (kit + Canon EF 75-300/4-5.6 + 50mm prime) or 270$ (Canon EF 28-105/3.5-4.5 USM + 50mm prime) to 1250$ (Canon EF-S 17-85/3.5-5.6 USM, Canon EF 70-300/4-5.6 IS USM, 50 mm prime). We must also remember that I will also have to buy the camera itself (500-600$), a carrying bag (50$) and a CF card (100$). Ouch.
Spending 2k$ on a hobby, that is just very not me.
Finally. I got the reply from Google - they want me to fly-in for an on-site interview. They will handle the flights, hotels, eating and other relevant issues and all I will have to care about is providing good answers to the questions that their engineers will be bombarding me thorough the day.
Unfortunately this silver lining has a little cloud in the middle - USA is out of H1b visas 'till Oct 2006, so I am asked to work at the Dublin office.
When I analysed the locations they gave me in the beginning, the Dublin office scored just below the Mountain View office. The good things were: being closer to Latvia and being inside EU (no visas, easier to travel), and the bad things were: weather and Irish terrorism.
Well ... let's see what they'll offer me in the end and maybe I will go to the Dublin office and then in a year or two transfer to the new Moffet Field facility or to the Chinese office :D
UPD: I am told that my gut feeling about IRA being a threat in Dublin is very far from reality. I must find out more about this city.
Many people have mailed/irc'd/called/commented asking my what's up regarding that Google thingy. Well ... everything is still up in the air.
Apparently Google recruiters have hard time getting a report back from one of the engineers that interviewed me. :)
The rule of crunchy goodness.
I have no idea if anyone has formulated this before, but here it goes. While I was making myself a salad (yes, that happens if you get addicted to that in HEL) I recalled that one of my friends was doing some experimentation to derive the optimum size of pieces to cut stuff in for a dish of his making. Basing on this i summarised my experience in the realm of salad and came to a conclusion:
Cut crunchy stuff in big pieces and chewy stuff in small pieces!
Following this simple rule we would cut salad leafs quite small and cabbage would come out relatively big. This way the salad will be crunchy and not slimy. Also you must remember that some stuff gets un-crunchy after the dressing soaks in.
That's all for the salad theory today - have some as a homework :D
A few hours ago I went trough the third Google job interview. In many ways it was very similar to the second one - the difficulty level was almost the same, the questions were similar in nature and detail. The only problem is that I stumbled twice on this interview. First of all I needed a tiny reminder to do a bit of strace'ing before diving into source to debug a problem. However that was tiny compared to the fact that could not remember some details about the physical layout of a file system, specifically the structure of inodes was a bit under my radar.
I must say that I am really enjoying the questions - deep, insightful and satisfyingly complex. It is a pleasure to see my knowledge (or lack of it, sometimes) exposed in a professional way. :)
Many have asked me what to expect from a Google job interview. I must say - expect good questions. Ask yourself, if you would need to uncover as much of your relevant knowledge over a phone line, how would you do it? Expect factual questions about powers of two, programming algorithms and data structures, learn everything that goes on on all OSI levels, practise debugging problems, be inquisitive.
You can only be a true geek if you always want to know how exactly every thing works. You are a true geek, when you do know and understand it. You are a true hacker, when you can use it to your advantage.
If you are a true hacker, then you will have no problems on the interviews.
(Just being a geek also might just cut it ;))
P.S. I tried to follow the latest meme, but according to Google, I need nothing. I wish it was so :D
A tiny Google Maps bonkers - Google does not exist!
Okay, why this, the fact that I had to talk a lot about my involvement with the anti-swpat campaign in EU on my my second Google job interview, and the fact that they have contacted me for a third phone interview (seemingly from a different department) seem to make my brain go *click*?
A quick note to those few people that read this blog and have at least a remote chance of bouncing into me in Real Life - I have shaved my mustache.
Yes. Really. No, I am not kidding you. I am perfectly aware that this is the first time I've done it in my entire life.
Anyway, if someone you do not recognize comes up to you on the street and is very friendly and a bit familiar, do not hit him with a baseball bat until you are sure that he is not me. :D
P.S. No photos of me without mustache exist, so hackergotchy must remain painfully out of date, for now.