Re:Performance comparison: counting words in Python, Go, C++...
by hamburglar on Monday March 15, 2021 @01:42PM
(#26469017)
Being a programmer involves a lot of things that are difficult to test for all at once in 45 minutes. Be irked all you want, but it seems counterproductive to pretend what’s being asked is in anyway unclear or unreasonable when you’re given a pure programming question with a clear spec. You’re supposed to write the code. That’s all.
Re:Performance comparison: counting words in Python, Go, C++...
by Veedrac on Monday March 15, 2021 @01:46PM
(#26469068)
My problem isn't that the spec is unclear, it's that the spec is silly. The task makes no sense, and selects for misusing tools. This makes it a bad interview question as given.
Re:Performance comparison: counting words in Python, Go, C++...
by hamburglar on Monday March 15, 2021 @06:30PM
(#26470138)
I’d argue that the problem does make perfect sense and isn’t a “misuse of tools” if you manage to understand the goal of the interviewer, which is “watch this person write code for a solution to a well-specified but arbitrary (perhaps even silly) problem.”
Re:Performance comparison: counting words in Python, Go, C++...
by EvilEy3 on Monday March 15, 2021 @06:10PM
(#26469895)
This is litmus test to weed out people who pretend to be programmers. You assess complexities hidden behind the task in system design round.
Re:Performance comparison: counting words in Python, Go, C++...
by Veedrac on Monday March 15, 2021 @07:06PM
(#26470481)
I was more viewing this in context of the article, which goes on to micro-optimize a version with an IMO unreasonable set of assumptions.
If it's instead explicitly given that this is a quick litmus test, the choices of the first pass implementation don't really matter, and you'll talk about complexities after, then sure.
There are cases where your task is nice, simple, and well-defined, but word counting is not one of them. It's better to give a more realistic task that allows people to think about the premises.