This workbook outlines key ideas but additional independent study is crucial to success. I prefer to avoid step-by-step instructions, so that you have a chance to learn and experiment. You should use online tutorials that suit your learning style to supplement this workbook.
Instead, I will be focussed on helping you critique the code that you write, to think more broadly about what you are doing and to understand the principles of what you do as a developer.
I usually receive two kinds of feedback in the classes that I teach:
- Developer A
-
“I wish there were more hands-on teaching and guided examples. I find that I learn best with step-by-step instructions.”
- Developer B
-
“I like that you don’t provide tedious content. When I experience a problem, I like to learn by being guided to the answer rather than just being told the answer.”
Do you identify more with Developer A or Developer B?
If you identify with Developer A, I would like to apologize in advance. If this is you, then you may find this workbook frustrating. If you choose to stop here, I will not be offended. I understand that not every resources suits everyone. However, if you continue, I ask that you stay open-minded. Please try to enjoy the experience (despite the discomfort) and give this approach a chance to work for you, rather than becoming more-and-more frustrated with time.
Here are some strategies to make the most of this workbook:
-
Complete exercise and reflection activities listed in these notes: think about your answers and write them down, rather than skipping to the answer.
-
Experiment with different ideas: try different designs and different tools.
-
Use a range of resources to study. Combine this workbook with other online resources.
-
Aim to spend perhaps 40% of your time on functionality, then 60% thinking about and improving the design.
-
Use discussion boards to not only get answers but also to get feedback and discover better questions.