Timeline for answer to How to test a programmer's ability to handle a large code base? by Adam Burke
Current License: CC BY-SA 4.0
Post Revisions
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 7, 2024 at 19:01 | vote | accept | JohnHernandez | ||
| Dec 2, 2024 at 15:11 | comment | added | xLeitix | Pedagogical state of the art suggests using grading rubrics religiously - it becomes harder to get bullshitted if you break down your evaluation of a given design into more narrow criteria. | |
| Dec 2, 2024 at 15:07 | comment | added | xLeitix | Regarding "manipulation by good blaggers, and verbose timewasters" - in my experience as a university teacher, this is a bit of a skill issue on the interviewers side. It absolutely is possible to distinguish between people talking competently about stuff they know and people producing hot air with lots of confidence. But it requires experience with that kind of evaluation, and it feels uncomfortably subjective at first (this feeling of subjectivity passes with experience, though). | |
| Dec 2, 2024 at 9:37 | comment | added | Jonathan | My #1 advice for candidates going into an interview: Get your story together WRT previous projects you worked on, and be prepared to explain it in details. | |
| Dec 2, 2024 at 9:36 | comment | added | Jonathan | "...they shouldn't share proprietary details" - I've heard some interviewers concerned that this would limit this part of the interview. In my experience, there's no problem - candidates know exactly what they can and can not share, and can provide good descriptions even for highly-classified systems, including military ones. | |
| Dec 2, 2024 at 7:57 | history | answered | Adam Burke | CC BY-SA 4.0 |