4 ms·
> That sounds as if you're steering close to a whiteboarding interview which a lot of people will claim isn't great. One major difference is that unlike a whit
by bzbarsky 6y ago
> That sounds as if you're steering close to a whiteboarding interview which a lot of people will claim isn't great.
One major difference is that unlike a whiteboarding interview there are presumably clear expectations as to what one is expected to have learned in the class and therefore what topics the discussion will cover, and at what depth.
Another issue with whiteboarding interviews, specific to computer-related subjects, is being asked to write code on the whiteboard, which is a severely unnatural act in all sorts of ways compared to the way one normally writes code. But an in-person assessment in a proofs-based math class, for example, would not have that problem. Similar for a CS (as opposed to software engineering) class.
And in a software engineering class, the concept of "test" is pretty odd, for the same reasons that whiteboarding interviews are; I'd expect longer-term projects to be closer to the right evaluation tool.
- seg_lol 6y agoI could see notebooks being a useful way to both handout homework and projects as well as automatically check for correctness. A merge/code review tool could be used to annotate individual problems. Have you seen this done?
- Jugurtha 6y agoWe have collaborative notebooks on iko.ai[0] which makes it easy either to pair program/troubleshoot on the same notebook, or for a teacher or instructor to review work. We haven't added autograding yet as it is specific, but nbgrader[1][2] comes to mind. - [0]: https://iko.ai/docs/notebook/#collaboration https://iko.ai/docs/notebook/#collaboration - [1]: https://nbgrader.readthedocs.io https://nbgrader.readthedocs.io - [2]: https://nbgrader.readthedocs.io/en/stable/command_line_tools/nbgrader-autograde.html https://nbgrader.readthedocs.io/en/stable/command_line_tools...