So after much deliberation, I’ve decided to really dive into Robby’s code and parse it to understand how he did everything. I’m having incredible difficulty trying to figure out how to implement my idea from scratch with the limited timeline I have. I figure the best use of my time is to parse his code and understand how he did it, and implement it myself.

That said, the source code for his interactive resume is insanely dense. At a little under 1400 lines of densely packed JavaScript, it’s not the easiest to read.

My main objective with this first pass of his code is to really understand how he set up all the layer movement. What’s really interesting is that, although the screen appears to move horizontally, then vertically, then horizontally, then finally vertically again, it’s simply one button, or one direction of scrolling in order to achieve this multi-directional path. There’s also a scroll bar on the side to show this concept as well. I’m struggling to visualize and understand how he was able to do that.

Upon looking at his code thus far, I’m noticing that he’s using A LOT of browser DOM API methods as opposed to jQuery, but it looks like that’s also because his code considerately takes into account compatibility with multiple devices, as well as multiple browsers. For now, my goal is to get the resume looking good with just Chrome. I’ll definitely come back to refine this project at a later date. Before that actually, I want to take what I’ll have developed, and migrate it to my own implementation of jQuery. I think it’ll be really impressive on a resume to be able to say that I used my own custom JavaScript library modeled after jQuery.

Otherwise, that’s pretty much it. I got a lot of work to do to catch up. I’m already feeling behind on my JavaScript project despite the extended deadline, and I also need to keep up with job search application materials. Thanks for reading! And I’ll catch everyone tomorrow!