Javascript was my first programming language. While it was fun to use, it was also very syntax heavy. The amount of ()’s and {}’s pretty much drove me insane.
After learning the basics of Javascript I started to look for other languages that would be relevant to my goal of web development. I had come to learn how Javascript was incredibly important making web pages function, and I wanted to learn the skills to drive the essential pieces that run in the background. That’s right, I wanted to take a look into the back-end.

I like to think of writing code similar to designing puzzles. The more simple the code, the easier to dissect each individual element and know the code with exact precision. However, I have a fondness for diving deep into code I don’t understand. One of my favorite things to do is to find a method on ruby-docs that I know nothing about, and pick it apart piece by piece. Originally, I used mass amounts of puts and tabbing back and forth between my editor and irb. During my first day at the IronYard my Instructor James introduced me to Pry.

Git is glorious.
I once thought it was annoying, countless git add . followed by
git commit -m “why am i doing this?”

My initial understanding of git was limited. I understood it was a VCM (Version Control Manager), but didn’t really grasp how powerful it was to backup code.