Re:Engineering whiteboard interviews: yay or nay?
by ngngngng on Thursday August 09, 2018 @03:53PM
(#17727878)
My most recent interview involved a coding assignment, which I topically don't do, but this one was a very interesting challenge that would make a good blog post afterwards so I did it. What was surprising is the interview not only included going over my code from the assignment, but also whiteboard problems about recursion. I've still never used recursion in my day job. Can interviewers really not gauge technical ability from my GitHub as well as chatting about problems and solutions?
[ Parent
| on HN ]
Re:Engineering whiteboard interviews: yay or nay?
by jarsin on Thursday August 09, 2018 @04:04PM
(#17727982)
Interviewer: I see you have built an app just like ours five years ago. That's great. OK now let's get to the important stuff. How many cakes can you steal from the queen if your duflle bag hold 5 pounds and there are 10 different kinds of cakes?
True story.
Re:Engineering whiteboard interviews: yay or nay?
by crsv on Thursday August 09, 2018 @04:31PM
(#17728199)
You have a software engineering job and you never used recursion of any kind? This strikes me as super odd.
Re:Engineering whiteboard interviews: yay or nay?
by dpiers on Thursday August 09, 2018 @06:32PM
(#17729133)
I can only think of a couple occasions in my professional career where recursion made more sense than iteration. Both involved traversing trees with unknown depths (parsing XML and scanning a file system).
That hasn't stopped it from showing up in every programming interview I've ever done.
Re:Engineering whiteboard interviews: yay or nay?
by redisman on Thursday August 09, 2018 @09:40PM
(#17730064)
I haven't really used it for anything other than super simple things with a very tightly bound max input. Stack overflow and honestly many recursive algorithms are quite hard to parse in your head especially once you add some edge cases and some other entropy.
Re:Engineering whiteboard interviews: yay or nay?
by dragonwriter on Friday August 10, 2018 @08:36AM
(#17732688)
> Stack overflow
Well, yeah, other than tail recursion with tail call optimization, stack consumption, if not stack overflow, is always an issue.
> and honestly many recursive algorithms are quite hard to parse in your head especially once you add some edge cases and some other entropy.
I find lot of things are easier to conceptualize recursively than iteratively, though parsing really depends a lot of the language.
Re:Engineering whiteboard interviews: yay or nay?
by jpindar on Thursday August 09, 2018 @09:57PM
(#17730144)
I do embedded work. In this field some compilers don't even allow recursion.
Re:Engineering whiteboard interviews: yay or nay?
by vesrah on Thursday August 09, 2018 @04:36PM
(#17728237)
They might generally use a library that handles a lot of common usages for recursion, like traversing a tree for whatever reason.
A question I've had in an interview was what is the difference between recursion and iteration. Fairly easy to explain, including examples of usage.
Re:Engineering whiteboard interviews: yay or nay?
by mushka on Friday August 10, 2018 @04:27AM
(#17731585)
I too never used it. Recursion is usually an inferior solution.