April 19th, 2012 by adam

This is from 4 years ago, courtesy of Steve Yegge. I just came across it by accident, it’s wonderfully well written, but one bit caught my attention in particular:

“First, you can’t tell interviewers what’s important. Not at any company. Not unless they’re specifically asking you for advice.”

Wait – what? … why not? Surely – if you’re being an honest candidate – your views on what’s important are a huge part of the interview process? These people want to know what you’ll be like as a colleague, how you tick – no?

“You have a very narrow window of perhaps one year after an engineer graduates from college to inculcate them in the art of interviewing, after which the window closes and they believe they are a “good interviewer” and they don’t need to change their questions, their question styles, their interviewing style, or their feedback style, ever again.”

Ah. Right. Yes, makes sense now. Sad, but true.

I will also add: for all the reasons Steve cited, I *do not run interviews this way*, and haven’t for a long time now. In my late twenties, I learnt the hard way how stupid a lot of those practices are.

Looking back at my sole Google interview, it explains a lot: I had no idea that Google accepted / allowed these practices among their interviewers – I’d assumed they’d have actively stamped them out. Apparently not. It was a big part of why I never considered Google again: if “A people hire A people” and “B people hire C people”, that part of Google’s process stank of the B people. Not a place I wanted to work…

Of course, Steve’s still writing about Google’s hiring, and his criticisms seem to be getting sharper over time. Just last year, he dropped this into a post:

“It’s a match made in heaven, I’m tellin’ ya. It might take you a couple tries to get in the door, because Google’s interview process — what’s the word I’m looking for here — ah yes, their process sucks at letting in all the qualified people. They’re trying to get better at it, but it’s not really Google’s fault so much as the fault of interviewers who insist that you’re not qualified to work there unless you are exactly like them.”

So … given Steve’s one-man crusade to undo the bad work of Google HR, I’d recommend anyone rejected by Google to give them another go. But don’t look at interview prep questions, don’t brush up on obscure programming technique – just read and re-read Steve’s blog posts, and remind yourself that it’s “a stupid process” you’re trying to get past, one that doesn’t fairly represent the company – nor the colleagues – you’ll be working for.

December 9th, 2011 by adam

For the past week, my iPhone’s have been unable to use Gmail. After approximately 4 hours, gmail locks you out of IMAP completely, unless/until you force-kill Apple’s mail client. The problem is … if you force-kill the client, you lose all emails you wrote, and you lose all emails you filed into IMAP folders (Apple’s client refuses to save state – it requires the server to do it).

Nothing has changed on the phones – and Google has been putting up irritating “stop using gmail, use the new gmail” ads for the same period of time – so I’m going to go out on a limb and guess that someone at Google changed something on the IMAP protocol that makes it no longer work correctly with iPhone.

I just had to write the same email for the second time, and re-file 50+ emails for the third time – and I’m giving up. You just can’t use gmail on an iOS 4 iPhone right now (I’m guessing that iOS 5 works OK, or there’d be an internet rage fest going on.

So. What to do. Dump the iPhone (switch to Android as my main phone, perhaps?)?

Or decide that enough’s enough, gmail is just too damn annoying these days (e.g. the 3 week period earlier this year where “reply all” was disabled on my gmail account) … I’ve heard there’s an email-for-life system called … hotmail?

Hmm…

September 7th, 2011 by adam

Today I finally discovered that the iPhone has StreetView.

That means it’s only taken me THREE YEARS to find this secret feature that Google has worked very hard to make sure no-one ever uses.

The best bit? The top two Google results for “iPhone Streetview” were both incorrect, and useless – but claimed to “solve” the problem (one of them was a Yahoo answer, the other a blog).

Eventually, courtesy of this amusingly-titled (yet poor in terms of Google hits) blog post, I found the solution:

  1. There MUST be a pin on screen – either because:
    1. you did a search for a place, and Google has found it and created a pin
    2. you tapped the curled paper in bottom right, then pressed the “drop a pin” button (incidentally: instead of letting you “drop a pin”, that button arbitrarily sticks a non-moveable pin in the center of the (now-hidden) screen. Terrible UX and GUI design. Google’s designers: what were you thinking?)
  2. The popup that’s attached to the pin has a standard button, and a standard icon – BUT THAT ICON IS NOT AN ICON
    1. …it’s an invisible button…

When we’re building iPhone apps for clients, this comes up typically once on every project: if you want to do custom user-interfaces, do NOT make them look like Apple standard interfaces. Apple has trained 200 million (total number of i* devices) to expect that (in this case: ) “a map-popup has exactly one button”. You are fighting against the work of one of the richest companies on the planet, a company famous for its marketing, interface-design, and visual-obsessions.

Worse is if you then go and break all the standards on what a “button” should look like, so that (in Google’s case), they:

  1. Put something in the place that is reserved for a non-clickable icon
  2. Used an icon-image instead of a button-image
  3. Provided no other ways of triggering the feature…even though this is usually NOT the place the user would want to click to get that feature

I laughed out loud when I discovered this – 3 years it’s taken me to get this to work, and me a professional iPhone developer too! How long is it taking the average “normal” user? If nothing else had convinced me Google is fundamentally f***ed by their refusal to design for anything other than “engineers who are exactly like us (and the rest of you plebs don’t matter)”, this would have nailed it for me.