News for hackers. Stuff that matters.

A comment on Google I/O 2013. Parent comment

Re:Google I/O 2013 by grimlck on Friday February 22, 2013 @04:33PM (#5267003)
One way to solve it is to make people pass a quick programming test before they can buy a ticket
[ Parent | on HN ]
Re:Google I/O 2013 by ben1040 on Friday February 22, 2013 @04:54PM (#5267127)
They were threatening to do that for last year's meeting, and then backed out on it. There was no test.

http://googlecode.blogspot.com/2011/11/google-io-2012-extend...

In the meantime, be sure to brush up on your coding skills. They’ll come in handy when the new application process opens in February. That’s all we can tell you for now, but we’d advise against making travel arrangements until then.

[ Parent | on HN ]
Re:Google I/O 2013 by xxpor on Friday February 22, 2013 @04:44PM (#5267066)
CAPTCHA: FizzBuzz edition.
[ Parent | on HN ]
Re:Google I/O 2013 by chadscira on Saturday February 23, 2013 @03:03PM (#5271230)
http://codepen.io/icodeforlove/full/eudqF
[ Parent | on HN ]
Re:Google I/O 2013 by chadscira on Friday February 22, 2013 @05:51PM (#5267449)
this sure would make it a lot easier to get a ticket!
[ Parent | on HN ]