|
|
|
|
|
|
by loup-vaillant
5411 days ago
|
|
|
How is this a problem of the teaching approach? I haven't read the book, but my guess is that it is basically unavoidable, short of providing working code. No OS without a computer, and no game without OS, right?. Plus, it is probably easier to use something you actually built. Anyway, if you really want to learn this stuff (well, any stuff), you have to "work his ass off until you figure it out"[1]. No pre-set time limit. Someone who is stuck will just take her time, go for help, rest, or whatever. On a final note, I fail every single program that I write. Several times. Then I fix them. Every single one. And for several failures, I have nothing more than one success. It may sounds gloomy, but it feels good, actually. [1]: Dr Tae, here: http://vimeo.com/5513063 |
|
|