I seriously can’t believe we’re already in the midst of week 11. Time is seriously flying by. That said, I can’t believe how behind I actually feel. There’s really no reference to whether or not this feeling is particularly justified, but given that we have algorithms and data structure lectures starting next week, which includes projects, I’m already feeling behind because of the lack of progress with my JavaScript project. Additionally, I’m still working on my other job application materials, so that includes things like resume, cover letter, and personal pitches.

I just barely got feedback for some of those materials yesterday so I definitely need to address them since they’re not ready for me to actually start applying for jobs just yet. Therefore, alongside my JavaScript project, and job search curriculum lectures and workshops, I need to revise my materials, as well as update my professional social media. Oh, I also need to create a portfolio page too. So much to dooooo.

I’m still working on parsing the source code for interactive resume, and it’s taking a lot longer than I expected, just because of the sheer complexity of each method. I think I really should only parse for three main points, and then I’ll be ready to implement my own solution:

1. Multi-directional window movement with uni-directional scrolling
2. How directional changes in window movement are determined
3. How and when animations are triggered, both for the main character, as well as other entities

I think understanding these points will help me map out what I need, and only what I need. Robby goes to great lengths to ensure compatibility across browsers and devices. I don’t currently have the time luxury to be able to accomplish that, but if I can manage it on desktop, I’ll be in a good place. I’m hoping to accomplish this before the end of the week, and really start with the graphic work over the weekend and pretty much finish the project before the weekend is up. The idea is to have this project completed and behind me while I’m working on algorithm and data structure projects during the following two weeks.

Additionally, yesterday we covered technical mock interviews. We paired up and answered behavioral questions like, “Tell me a little bit about your background,” and “Tell me a time when you took initiative.” Along side these behavioral questions, we also white boarded toy problems. It’s easy when you can code out without having to make sure the spectator/interviewer understands what you’re doing and end up with the correct answer, but to whiteboard in the the context of an interview is an entirely different ball game. We were presented with a whiteboarding framework to use that included steps such as ensuring understanding of the problem, planning out what you’ll be coding, and coding itself. But something that was emphasized more so was testing and analyzing at every step of the process. I definitely believe this framework will help me whiteboard better, but it’s going to take a lot of practice. Thankfully, we’re doing this every day.

This pretty much summarizes my day from yesterday. Another interesting observation I made was that the newest cohort that started in March, already started pair boarding, something we started a couple weeks in, I think 4th or 5th week in? March cohort is only on their second week. I think this is a really great addition to the curriculum.

That’s pretty much it! I’ll talk to you guys tomorrow!