Just finishing our section on Meteor. It's been awesome. I'm finding it very intuitive, more than anything else I've used so far. But, I'm hearing from both students and teachers that I shouldn't rely on it too much at this point in my learning. That I should learn better how to do things the hard way first, which makes sense to me.
We've also gotten started on our personal projects, which has been exciting, and a little daunting, to be honest. I'm thinking about making a music discovery web app using the Rdio API.
Zooming In and Out
The biggest way I can improve my coding is to step back from the code sometimes. I get lost in the details and forget what the bigger picture is. I need to be able to regularly move between the big picture and details of making the program work.
Marcus Phillips advises us to gradually progress from an abstract plan to code, making the plan more detailed and code-like at each step. This framework has helped keep me from feeling overmatched by problems.
I am starting to learn that when my code isn't working, and I am just tweaking random things, hoping they'll fix it, without being able to explain to myself why they should fix it, I need to stop thinking in code. I need to draw a picture, or write a sentence, reminding myself what the bigger picture is. Then I can gradually zoom in on that picture until I return to the details of code, with a clearer understanding of what I need to do.
When I was trying to teach myself to program, I thought of programming as just typing stuff in a strange language. Now I see typing code as the step that comes once I have distilled a vague solution to an unclear problem into a series of detailed, very unambiguous steps. It's fun.