Skip to main content

README

When it comes to programming, it's more than just syntax; it's a way of thinking, a way to look at problems and solve them. I found many developers fried and highly stressed because they aren't really in the right mindset to see problems for what they are. This page is to help those who are looking for that help with tools and techniques.

"You don't learn to walk by following rules. You learn by doing, and by falling over". ~ Richard Branson

Trying to become more comfortable with falling over.

Disclaimer:

For those going through the general assembly's skills gym and reading this documentation, congrats on making it this far and thank you for reading. What I have to say is beneficial to what you are about to go through. To give you a heads up about your debugging challenge, you will have a moment where you wonder why you are given the questions and what you should do with them on earth. Well, here is one of the best ways to work through it, copy the code and run it, then fix it. Sometimes "fixing" means you actually have to build functions to get it to make it work. The only one you should NOT edit the original code is the last one. Work through it to find how to get to what needs to be printed out.