Once I had identified and dealt with the definition versus loading problem, I had a short but productive streak, only to come to a complete halt because of another cryptic problem. While the definition versus loading problem is an obvious mistake (albeit easy to make, easy to overlook, and hard to diagnose), my next cryptic problem was not one that I, or the senior programmers that were kindly helping me, even knew to look for.
ATM: Angular Module - Definition vs Loading
Angular uses a very similar statement to define a new module and to load an existing module. For example, the initial definition for my stage-hand app was:
|
|
While the statement to load my stage-hand module (e.g., at the beginning of the controller and service files) was:
|
|
Note that the only differences are , [] and ;, so it’s easy to make a mistake.
To make matters worse, the symptoms were really cryptic.
All The Mistakes
While starting my stage-hand project I ran into several ‘black box’ problems. After spending a frustratingly inordinate amount of time ripping code apart, I was able to identify two separate problems. One was an easy to make mistake that I thought I had checked for early in the debugging process. The other problem didn’t make any sense at all, but thankfully I stumbled across an explanation that made a load of sense.
Code-friendly Notetaking in Sublime 2
During my time at DevMountain, a couple of students knew they were going to miss a class and asked me to send copies of my notes [1, 2]. My notes’ files subsequently raised a fair number of questions and it became clear that other DevMountain students might appreciate knowing how to take notes in Sublime using Markdown.
DevMountain - First Half
Our second quarter at DevMountain started off like a bad roller-coaster ride. Thankfully, this last week was like the gentle clacking as the car returned to the platform. Where I had a hard-time following Angular, Node was –by and large– super-easy.
Project Introductions
One of the reasons I wanted to do a bootcamp is my own overflow of application ideas. This past week is the first time that I felt like I could start to implement one of my ideas using JavaScript. I’ll be posting a bit more about that in the near future, but first I wanted to share a little bit about the app ideas that are fighting for my cognitive process.
If you’re interested in any of these projects, please let me know!
DevMountain - Week Five
This was another roller-coaster week of Angular. One of the big dichotomies of the week was our variety of instructors. In the end, I definitely felt like I learned a lot, but it’s largely an ephemeral feeling with very little working code.
Promises and $q
Our first introduction to promises and $q left most of us in a serious state of “?huh?”. After asking a couple of mentors and still not feeling like I had even a tenuous grasp, I was starting to worry. But then we were graced with Ryan Shaw’s leadership!
DevMountain - Week Four
This week felt like an Angular roller-coaster. In the end, I seem to be able to make Angular apps, but I definitely still don’t understand Angular.
There are at least four different reasons for this situation: prerequisite expectations, inconsistent documentation, instructional style, and an off-week for my brain.
For those that have read my previous posts, I’m finally starting to link to the projects that I’ve completed. This week’s post and my week one post have a results section at the very end that highlights and links to these projects. I should have week two and week three done next weekend.
DevMountain - First Quarter
This post touches on week three but mostly covers my thoughts on the bootcamp experience thus far. At this point, my cohort has finished three weeks out of our twelve weeks at DevMountain.