Visual explanation of the last Google Codejam 2017 question
1–10 of 33 posts
Re: Visual explanation of the last Google Codejam 2017 question
#2Re: Visual explanation of the last Google Codejam 2017 question
#3I wonder if there is a real cause and effect relationship between being good at this kind of games and being a good coder. I suspect not.
I don't even bother replying to their recruiters any more. The interview process tells me more than enough about the company.
Re: Visual explanation of the last Google Codejam 2017 question
#4Re: Visual explanation of the last Google Codejam 2017 question
#5I wonder if there is a real cause and effect relationship between being good at this kind of games and being a good coder. I suspect not.
A lot of people are good software engineers and can wrote good software. To get Jeff Deans that write revolutionary software, we don't yet have a better method than training people in these abstract, very hard problems, making them compete and hoping for the best.
As much as we software engineers / computer scientists believe we are special snowflakes, this exact same method is applied to most STEM PhD to professor tracks, mathematics, classic music instrument players, [athletes], and what have you.
[post] https://www.joelonsoftware.com/2005/07/25/hitting-the-high-n...
[athletes] http://rittersp.com/wp-content/uploads/2014/03/Chambliss-Mun...
[musicians] http://www.nytimes.com/images/blogs/freakonomics/pdf/Deliber...
Re: Visual explanation of the last Google Codejam 2017 question
#6I wonder if there is a real cause and effect relationship between being good at this kind of games and being a good coder. I suspect not.
This is of course a different question than whether this test provides maximum predictiveness of future success. But it seems obvious to me that the test provides some information. It's really hard for a variable to be completely non-informative.
Lastly, I think it's important for us to not be too defensive. I sense, perhaps incorrectly, that sometimes we don't want to give value to tests we are bad at, because doing so would imply we aren't as good as feel we are.
Re: Visual explanation of the last Google Codejam 2017 question
#7I wonder if there is a real cause and effect relationship between being good at this kind of games and being a good coder. I suspect not.
This is about hitting the high notes, as Joel Spolsky put it in his [post]. A lot of people are good software engineers and can wrote good software. To get Jeff Deans that write revolutionary software, we don't yet have a better method than training people in these abstract, very hard problems, making them compete and hoping for the best. As much as we software engineers / computer scientists believe we are special s…
Re: Visual explanation of the last Google Codejam 2017 question
#8Re: Visual explanation of the last Google Codejam 2017 question
#9I wonder if there is a real cause and effect relationship between being good at this kind of games and being a good coder. I suspect not.
The part where you make large software, working in teams, to serve real users, can only be learnt on a job.
These competitions are not looking for anything fancy. They recruit juniors, they'll be trained on the job.