3 ms·
Some things from your post are spot on! Especially the riddles. Seriously, you got to tell me how many people deal with riddles in your day to day programming j
by kamaal 15y ago
Some things from your post are spot on! Especially the riddles. Seriously, you got to tell me how many people deal with riddles in your day to day programming jobs? Do you pick up blank sheets of paper and work on puzzles a considerable part of the day.
Even if you were, I would personally never want to work at a place which has this kind of a culture. I am out looking for a job where good business problems get solved in the most practical way. Which helps both the business and me make money.
Second kind of questions are asking the candidate arcane and rare facts that can be known only through rote memorization. Like asking him to work on some concept/data structure/algorithm from a CS text book taught in semester 3 on page 345 of a text book 2000 pages big.
There is nothing great about knowing an algorithm, inventing a new algorithm is special but not knowing one. Worse case anybody can know what you know by searching.
Asking irrelevant questions to the job, gives you a very high rate of false negatives. You are missing out on some very good and productive people.
This is exactly what happens, you ask some irrelevant questions and consider the guy useless. The same guy goes works at some php shop which is solving some business problems which get him and the company good money. And here you are searching and filtering candidate as per your requirements. Meanwhile you see, your start up failing and the average guy there winning. Suddenly you shout out 'Worse is better'.
You've got be brutally honest and practical in software engineering. If you are academics its a different game.
Remember your fantasy elitism in building a dream product and plans to hire rock stars to do it is nothing if it fails. The average guy still ends up winning even if he has 1/10 decent the product of your dreams, if he has a product to sell now.