4 ms·
I applaud the OP's intentions and I think more attention overall needs to be paid to the "oil/grease" that makes it possible to learn concepts. It's not just in
by danso 13y ago
I applaud the OP's intentions and I think more attention overall needs to be paid to the "oil/grease" that makes it possible to learn concepts. It's not just intellectual effort and spirit that powers learning, but the attention paid toward lowering every source of friction.
To use a higher-level example, I found learning and adopting new JavaScript frameworks was hugely more enjoyable and easier thanks to build systems that set up continuous testing/automatic-reloading right out of the box (yeoman.io, for instance). Sure, running the bash command to compile CofffeeScript and run the tests takes just a second to type and execute...and hitting Cmd-R to reload a webpage after editing the files even less, but those seconds build up, to the point where development because more of a burden than it should feel like. And, well, if I stop programming because I'm tired, I'm not learning.
So I could see how inadequate hardware would be a major impediment to learning to code. The frequency that novices fail to close parentheses and quotation marks (and the inexplicable errors that leads to) is bad enough on a good keyboard...I can only imagine how frustrating it'd be if your Shift key worked only half the time you expected it to.
That said, I disagree with the author's specific examples. His rationale for a bigger monitor, especially. If a novice is using five programs (2 chrome windows, Sublime Text 2, Evernote, and Github(???)) to do simple HTML/CSS tracing...then I would argue that she is trying to do too much and that more of the concepts should be taught in an orthogonal way.
The OP defends his student's habits, saying that instead of learning to do Cmd-Tab to switch, she should work off a 30-inch monitor. I think that's the wrong way to approach the situation, even if you ignore the monetary realities of buying a bigger monitor. Novices not only don't know the concepts, they also don't know how to learn the concepts. The pattern that the student has apparently adopted does not seem like a best practices one.
A tangent discussion could be started on how one might structure the HTML/CSS lessons so that the student doesn't have to have 5 windows open at once...but I'll stop at arguing that the OP presents a sort of false dilemma here. It's not that either the hardware improves, or the student's education will be harmed. There's also the ability to restructure the concepts so that they can be handled one at a time, and the discretion to push the student towards more efficient habits.
To use one more example: in typing class, our teachers made us cover our hands with paper...it wasn't comfortable nor what we would do naturally, but this helped enforce the concept that typing is ultimately done fastest when not looking at the keys.
- TheZenPsycho 13y agoI disagree with your point about the monitor. Of utmost importance in learning and usability is the concept of "visibility", that is, the ability to see at all times the state of a system. An experienced programmer can cope with less visibility since a lot of that system state is in their head. For a novice, with no experience to draw on, they are essentially working blind, having no idea what their changes are likely to do until they see the results. At the very least you need to have both the editor and the browser open. Switching between these two to see changes is more friction than necessary. The additional windows are: 1. to see the lesson 2. to see the website she is copying off 3. I forget. but it doesn't matter anyway. The task of switching between all these windows is enough to shatter the mental context of the real task, which is building the website, making a particular modification. That's the other thing- the workflow aspects haven't necessarily been offloaded into the novice's unconscious mind yet. Switching between a window needs conscious attention that breaks the coding context, and the coding context must be reestablished again and again, on every change. None of these realities go away because of your opinions about how a "real" programmer should be working.