I read this piece on Sunday and this paragraph has stuck with me all week:

The point of the hackathon was to sketch out in code potential solutions to “robot tasks”—routine aspects of a teacher’s job that don’t require teaching skills. Kimberly Johnson, the head of product success and training, addressed the team. “Basically, what we have told teachers is we have hired you for your creative teacher brains, and anytime you are doing something that doesn’t require your creative teacher brain that a computer could be doing as well as or better than you, then a computer should do it,” Johnson said.

I’ve been racking my brain all week trying to come up with a “robot task” I do that consumes more than ten-fifteen seconds. Some robot tasks are also things that students should learn to do as part of daily life: organizing their work into a table of contents or plugging up computers or taking care of the room. And most “robot tasks” I like to use as a break from intellectual work: taking attendance or passing back the initial pile of papers for kids to sort themselves.

None of these add up to even five minutes over the course of a day.