Hacker News Reader

Comment by wolframhempel | Hacker News Reader

I want to test their ability to perform a task - rather than how well they memorized things. Which is not to say that memorization is not important, but it's just one piece of the Puzzle. So when it comes to language tests, rather than having the candidate fill in prepositions into blanks, let's have an actual conversation with them in which they apply their combined skills.

View on HN

I actually adhere to this philosophy when hiring candidates as well. Rather than having them explain how to reverse binary trees on a whiteboard, I have them sit down and do a mini version of the actual task they will have to do in their job later. And, unsurprisingly, knowing how well they do the actual task is a much better indicator of how well they perform at doing the actual task later.

I think this is a good philosophy for hiring employees, but when it comes to education, we wish to go beyond training employees, and what your capabilities are is not the only thing that matters. We should test practical capabilities, but we should test more abstract skills like how many facts you've ingested as well.

When I tell people a story about the history of the french revolution or something, I don't have the opportunity to go research it beforehand. I've already done that research, and I've already thought about those events for months or years, which gave me the opportunity to synthesize an insight or opinion I wish to share.

You don't get that if you don't know things in your head.

I understand what the halting problem implies, what complexity is, what Turing machine means and why they are an abstraction for algorithms, and the basic common memes of programming such as using a stack and a heap, IEEE 754 floating point numbers, 2s complement binary numbering, and so on and so forth.

Yet I don't know a lick of Go. If I were to open up a Hello World tutorial for Go during the interview, would I honestly still have a shot?

I think people who are really into "do the job for an hour" interviews don't understand this. Some skills (particularly programming languages) are just really easy to learn. I learned go in a week for a consulting job. If I had to do an interview in go, I would not have gotten the job.

Then how about you spent the week learning Go and then come interview?

Because there's a big difference between doing a week of unpaid work hoping to get a job and doing a week of paid work after you already have it.

Reply on news.ycombinator.com