4 ms·
This jives with some of the studies mentioned in the excellent book "How We Decide". Basically, if you want to get good at something, relentlessly question your
by andrewvc 17y ago
This jives with some of the studies mentioned in the excellent book "How We Decide". Basically, if you want to get good at something, relentlessly question your methods, benchmark yourself, and try to get better.
I become a teacher of sorts about a year ago. I teach my boss's kid how to code on the weekends, he's learning Javascript at the moment. I've had to majorly re-adjust my teaching strategy about 4 times over the last year. When I started I was doing a terrible job, and now I know I'm doing a much better job (though I still have a long way to go). Whenever I teach it takes quite a bit of brainpower on my end as I try and get inside of my student's head, so I can see what's working and what isn't. I can only imagine how hard teaching is when you don't have the luxury of focusing on just one student, but rather 5 classes of 30.
In my memories of high school and college (high school in particular) so many of my teachers seemed detached, uninterested, and even bored with a lesson plan that they'd probably taught year in year out. I wonder how these people can be fixed? Can they just copy off teachers who actually try, or are they doomed to mediocrity? Can one be genuinely self-critical if one isn't motivated? My intuition tells me the answer, sadly is no.
- wisty 17y agoHow often do good coders read other people's code (in code reviews, or in their free time)? How often do teachers "sit in" on other teachers lessons?