Timeline for Why are data structures so important in interviews?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 18, 2011 at 23:07 | comment | added | Christopher Mahan | I can imagine that the guy who worked on the ERP system isn't a good fit for the team. | |
| Aug 18, 2011 at 17:14 | comment | added | user3792 | @gnat - That is good too. I guess what I am getting at is that the most in-depth understanding of the fundamentals does not speak to overall ability past a certain point, but there is a trend to assume just the opposite. Data structures are something that most people get taught by someone else (usually a teacher). I want to know what they can learn on their own, because that is how the real world works. Good programmers can design reasonable systems based on best practices. Great programmers can learn the insane systems written by horrible programmers using worst practices and make them work. | |
| Aug 18, 2011 at 15:24 | history | made wiki | Post Made Community Wiki by cdkMoose | ||
| Aug 18, 2011 at 15:19 | comment | added | gnat | Interesting - good list. How about a slightly different look at it? 1. project/time management: being able to prepare things in such a way that data structures waste only small part of interview time. 2. a minimum amount of social skills: a developer that is capable to understand that interviewers typically want to just quickly check basic data structures before proceeding to more interesting areas. 3. the ability to learn new things quickly and continuously without distractions that might be caused by the lacking knowledge of, well, of data structures basics. | |
| Aug 18, 2011 at 14:58 | history | edited | user3792 | CC BY-SA 3.0 | added 867 characters in body |
| Aug 18, 2011 at 14:42 | history | answered | user3792 | CC BY-SA 3.0 |