3 ms·
I think you're misunderstanding their claim, because you are both saying the same thing. They are claiming that juniors are unable to see (imagine, anticipate,)
by scubbo 6y ago
I think you're misunderstanding their claim, because you are both saying the same thing. They are claiming that juniors are unable to see (imagine, anticipate,) the cases in which _the code that they have delivered_ is crap; whereas the senior, with the benefit of painful experience, are able to predict the failure cases of this currently-apparently-working _delivered_ code.
- BlargMcLarg 6y agoI'm hard-pressed to see seniority being the main attribute for this rather than personality type, unless people wish to go into semantic discussions that having a more introspective and critical outlook is part of being a senior (in which case, we could easily dismiss the majority of seniors as being expert juniors).
- scubbo 6y agoI think it's breadth and depth of experience - both in using software, and in writing/supporting it - that is the truly correlated variable. (EDIT: though, yes, you're right that introspection and thoughtfulness also help. Someone who's been through a hundred firefights and not learned from them will not think about those things - but also, an introspective and thoughtful person who hasn't experienced or heard of certain failure cases won't have easy references or checklists to call to mind)