3 ms·
> The tasks <...> come out of the designs we've implemented. I guess the tasks are something like "take this scaffolding and implement thing x". What would you
by friendzis 6y ago
> The tasks <...> come out of the designs we've implemented.
I guess the tasks are something like "take this scaffolding and implement thing x". What would you think if the candidate responded saying the scaffolding does not allow to implement X properly without sacrificing things y and z, and instead of turning in code for review would show up for a discussion about the compromises and deficiencies in the scaffolding?
- cutemonster 6y ago> if the candidate responded saying Responded how, when? (At what point in the process)
- friendzis 6y ago> At what point in the process > > instead of turning in code for review I.e. something like instead of turning in code example they turn in a motivated analysis of why the scaffolding provided cannot support "proper" (and then analysis of so called proper) implementation of the thing asked, provide analysis for changes required in the scaffolding. Basically, the candidate would turn "provide and review code" process into "let's talk about architecture, implementation and tradeoffs". Would you discard such a candidate for not following the process because you expect seniority or would higher level thinking be a plus?