3 ms·
You seem to very much focused on data structures and algorithms, which I do understand is the only way many organizations can quantify prospective programmers (
by aryehof 7y ago
You seem to very much focused on data structures and algorithms, which I do understand is the only way many organizations can quantify prospective programmers (other than knowledge of "technologies" and "languages").
I'm curious what your response would be to the following interview question ...
"How would you model into code the operation of an elevator?"
(I'm wonder whether your viewpoint is solely one of data structures and algorithms that transform them. Or whether you might also have some other perspective of how to go about approaching the design of a software application?)
- lilsoso 7y agoThe elevator question is deceptively difficult and I find there aren't any decent answers to it on the internet. People have devoted phd papers to this topic. And there are sparse Leetcode discussions on this subject.
- aryehof 7y agoI suggest it is particularly difficulty if you have no method or approach to apply. That in itself says a lot about an applicants design and programming ability. Given that much of software development is about modeling systems (real or imagined) into code, is it too much to ask that a "programmer" know something about it?
- thorin 7y agoIt is difficult, but that doesn't mean it wouldn't be an interesting 10 min discussion as part of an interview.
- zimpenfish 7y ago> "How would you model into code the operation of an elevator?" "I refer the honorable gentleman to TAOCP, Volume 1, page N where DEK discusses this extensively." I think it's V1 but it's been a while