Introduction <If It Were Easy, Everyone Would Be Doing It>  I’ve always loved to code. In my second year of business studies at university (way back in 1996), I was up late one night working on a PowerPoint presentation about a factory trip our group had recently taken. (Pretty mundane stuff.) It just so happened that one of my roommates was up around the same time working on a project, coding some HTML. I bore witness to what he typed into Notepad and what he displayed in a browser, and I was blown away by the possibilities. I realized what he was doing and what could come from it. I was hooked. That night I tossed PowerPoint out the window and wrote my first HTML pages with photos from our factory trip, added some back and forth arrows into the page for good measure, ran it in Internet Explorer and shipped my first code. (If all you took from this is that I used Internet Explorer for a presentation, please hear me out.) By the end of it all, I cared more about my hard-coded HTML masterpiece than I did about the presentation that I had spent the last few weeks sweating over. I was downright giddy every time I had to click next and occasionally clicked back when the conversation required it. (I didn’t need it… I wanted to show off.) Out of a class of fifty business students, not one cared about how I had created my presentation. It wasn’t until the very end, after all the “important” questions were asked, that my professor asked how I did it. One person liked what I did. One person. Not the person or people whom I was trying to connect with (and maybe edu- cate), but someone liked it. Good enough for me! From that experience, I realized two things:  1.I wanted to code for the rest of my life. 2.It’s essential to know whom you are coding for.