Jason GormanSpeaking of comprehension and reasoning, I've been kicking around ideas for a code comprehension test that devs could take to help them gauge if they're ready for my training.
It's been increasingly a problem in recent years.
My current thinking is that devs would be shown a snippet of code and asked to predict what it will do in specific cases (e.g., what the output of the program or return value of a function would be).
Variations on that theme are possible. e.g., Find and fix a bug, make a change for a new requirement, and so on.
Anders S@jasongorman I also find that showing some code and asking for critique/improvements can work. Maybe a bit more open ended and fuzzy, but good in many instances. 🙂
@anderssv I can't really do that for 10-12 trainees a week 🙂
@jasongorman yeah, get that. Open ended will be more time consuming as well.
@anderssv I think "What will this code do?" is a good way to gauge comprehension. Changing/fixing code would also require that the ability to reason about what it will do. Might even throw in some refactoring :-)