If Google sees that you're searching for specific programming terms, they may ask you to apply for a job as Max Rossett writes that three months ago while working on a project, he Googled “python lambda function list comprehension.” The familiar blue links appeared on the search page, and he started to look for the most relevant one. But then something unusual happened. The search results split and folded back to reveal a box that said “You’re speaking our language. Up for a challenge?” Clicking on the link took Rossett to a page called "foo.bar" that outlined a programming challenge and gave instructions on how to submit his solution. "I had 48 hours to solve it, and the timer was ticking," writes Rossett. "I had the option to code in Python or Java. I set to work and solved the first problem in a couple hours. Each time I submitted a solution, foo.bar tested my code against five hidden test cases."
After solving another five problems the page gave Rossett the option to submit his contact information and much to his surprise, a recruiter emailed him a couple days later asking for a copy of his resume. Three months after the mysterious invitation appeared, Rossett started at Google. Apparently Google has been using this recruiting tactic for some time. "Foo.bar is a brilliant recruiting tactic," concludes Rossett. "Overall, I enjoyed the puzzles that they gave me to solve, and I’m excited for my first day as a Googler."
(Score: 0) by Anonymous Coward on Saturday August 29 2015, @08:03PM
Real Programmers don't use interpreted brogramming languages.
OH NO I am no longer a real programmer! The horror THE HORROR! /sarc
I personally love the new way of programming. Instead of having 10ft of books laying around I occasionally use. I now google for it and have the full doc in front of me and usually about 15 different examples of how to use it. Then if it does something weird there is usually about 20 examples of what I did wrong and how to fix it.
What chaps my ass is the number of SDKs you have to work with and understand now. Because of the 'brogrammer' you are going to be dealing with will suddenly decide he wants to work somewhere else and wants to 'pump up the resume' and dumps some sort of shit in there.
(Score: 3, Touché) by Anonymous Coward on Saturday August 29 2015, @08:30PM
The way of code is thus:
1. Google it.
2. Ignore links to documentation.
3. Click on first StackOverflow link.
4. Copy paste first answer.
5. Run code.
6. Copy error message.
7. Paste error message into StackOverflow.
8. Whine until someone fixes it for you.
9. Congratulations, you are now a coder.
(Score: 0) by Anonymous Coward on Saturday August 29 2015, @10:11PM
10. Profit!
(Score: 2, Informative) by riT-k0MA on Sunday August 30 2015, @08:34AM
I must be oldshcool. I actually try to understand the StackOverflow answer before attempting to implement it. Then again, the code in the answer is usually only part of the solution to my problem...
(Score: 2) by Runaway1956 on Saturday August 29 2015, @09:30PM
LOL @ "brogramming".
(Score: 0) by Anonymous Coward on Saturday August 29 2015, @10:06PM
You're forgetting that management at any tech company in the West knows that, if it got rid of you and your salary, it could hire six "experienced engineers" working in India to write code the same way you do.
(Score: 0) by Anonymous Coward on Sunday August 30 2015, @02:21AM
That only works for one or two cycles until they find out how shitty outsourcing returns are in terms of productivity and results.
(Score: 0) by Anonymous Coward on Sunday August 30 2015, @11:53PM
But you are just managing them wrong. Here are 2 other people to help you manage them. Make sure you do more code reviews.
Wait.... the number of people you assigned to manage it I could DO this project....