CF401JS First Day — Node environment
Our class is actually very small compared to most 401s, I think we have a total of only ~15 students, an instructor, and a TA. Possibly another TA on the way.
We did a quick intro round around the room and talked about a course outline very briefly. It’s going to be 4 weeks of back-end building an API, we connect the API to a front-end in the later portion of the course. We’ll also be doing data structures and algorithms which are great for learning some of those CS fundamentals that are very important in interviews. We had Brandy Rhodes, the Campus Director give a talk about career development, if you combined Jordan Belfort with a wise sage, that would be the impression I got from her. It was a great inspiring intro to 401, I really resonated with the idea that she presented of having a strong reason, “having a why”, of why you’re doing this, moreso than just transitioning. It’s a good thing to ponder not only for myself but for anyone who’s undertaking a challenge. Nothing good comes easy, and when you’re pushing your comfort zone it always helps to remind yourself why you embarked on this in the first place.
After presentations, we quickly switched gears and hit the ground running. Over the next 4 weeks we’ll be buildilng an API from scratch and today was the first baby step towards that. We learned about the node module pattern and testing using a combination of mocha and node’s built-in assert module. After a quick demo, we went to lab and knocked out tests on a couple of modules. Tomorrow we’ll be learning about some more node tools (Chai?) and context class.
It was also nice to meet up with some familiar faces that I had seen here in my last visit. It’s an incredibly welcoming community of people here, I feel like interacting with different personalities and the walks of life people come from helps soft skills a bit here and there. Today I talked to some of my classmates on troubleshooting that ydkjs error I was having.
More on the solution to that error coming up. Hint: it had something to do with node’s global object. I see you, new subscribers! Stay tuned.