Learning Web App Development
by Semmy Purewal
In early 2008, after about six years of grad school and teaching part-time, I found myself hoping to land a job as a full-time computer science professor. It didn't take me long to realize that professor jobs are really hard to come by, and obtaining a good one has almost as much to do with luck as it has to do with anything else. So I did what any self-respecting academic does when faced with a scary academic job market: I decided to make myself employable by learning how to develop web applications.
This may sound a little strange. After all, I had been studying computer science for about nine years at that point, and had been teaching students how to develop software for about six years. Shouldn't I have already known how to build web applications? It turns out that there's a pretty large gap between practical, everyday software engineering and programming as taught by computer science departments at colleges and universities. In fact, my knowledge of web development was limited to HTML and a little CSS that I had taught myself at the time.
Fortunately, I had several friends who were actively working in the web development world, and most of them seemed to be talking about a (relatively) new framework called Ruby on Rails. It seemed like a good place to focus my efforts. So I purchased several books on the topic and started reading online tutorials to get up to speed.
And after a couple months of really trying to get it, I nearly gave up.
Why? Because most of the books and tutorials started out with the assumption that I had already been developing web apps for years! And even though I had a pretty solid background in computer programming, I found all of the material extremely terse and difficult to follow. For example, it turns out you can take an awful lot of computer science classes without ever coming across the Model-View-Controller design pattern, and some of the books assumed you understood that in the first chapter!
Nevertheless, I managed to learn enough about web app development to get a few consulting gigs to support me until I managed to land a professor job. And through that, I realized I enjoyed the practical aspects of the field so much that I continued consulting outside of teaching.
After a few years of doing both, I was offered the opportunity to teach my first class in Web Application Development at the University of North Carolina at Asheville. My initial inclination was to start with Ruby on Rails, but when I started reading the latest books and tutorials, I realized that they hadn't improved much over the years. This isn't to say that they aren't good resources for people who already have a background in the basics, it's just that they didn't seem suitable for the students I was teaching.
Sadly, but not surprisingly, the academic books on web development are far worse! Many of them contain outdated concepts and idioms, and don't cover the topics in a way that make platforms like Ruby on Rails more accessible. I even reviewed one book that was updated in 2011 and still used table-based layouts and the 'font' tag!
For version control, I picked Git, because —well— it's Git and it's awesome. Plus, it gave my students the opportunity to learn to use GitHub, which is becoming immensely popular. Although I don't cover GitHub in this book, it's pretty easy to pick up once you get the hang of Git.
I decided to use jQuery on the client because it's still relatively popular and I enjoy working with it. I didn't use any other frameworks on the client, although I do mention Twitter Bootstrap and Zurb Foundation in Chapter 3. I chose to stay away from modern client-side frameworks like Backbone or Ember, because I think they are confusing for people who are just starting out. Like Rails, however, you should be able to easily dive into them after reading this book.
On the server-side, I chose Express because it's (relatively) lightweight and unopinionated. I decided against covering client- and server-side templating, because I think it's essential to learn to do things by hand first.
I selected Cloud Foundry as the deployment platform because it was the only one of the three that I considered (including Heroku and Nodejitsu) that offered a free trial and didn't require a credit card to set up external services. That said, the differences between the platforms aren't huge, and going from one to another shouldn't be too hard.
Is This Book for You?
This book is not designed to make you a "ninja" or a "rock star" or even a particularly good computer programmer. It won't prepare you for immediate employment, nor can I promise that it will show you "the right way" to do things.
On the other hand, it will give you a solid foundation in the essential topics that you'll need in order to understand how the pieces of a modern web app fit together, and it will provide a launching point to further study on the topic. If you work your way through this book, you'll know everything that I wish I had known when I was first starting out with Rails.
You'll get the most out of this book if you have a little experience programming and no previous experience with web development. At minimum, you probably should have seen basic programming constructs like 'if-else' statements, loops, variables, and data types. That said, I won't assume that you have any experience with object-oriented programming, nor any particular programming language. You can obtain the necessary background by following tutorials on Khan Academy or Code Academy, or by taking a programming course at your local community college.
In addition to being used for self-study, I hope that this book can serve as a textbook for community classes in web application development, or perhaps a one-semester (14-week) college-level course.
Learning with This Book
Developing web applications is definitely a skill that you'll need to learn by doing. With that in mind, I've written this book to be read actively. What this means is that you'll get the most out of it if you're sitting at a computer while reading it, and if you actually type in all the examples.
Of course, this particular approach is fraught with peril--there is a danger that the code examples will not work if you don't type them exactly as they appear. To alleviate that risk, I've created a GitHub repository with all of the examples in this book in working order. You can view them on the Web at http://www.github.com/semmypurewal/LearningWebAppDev. Because the full examples live there, I try to avoid redundantly including full code listings throughout.
In addition, I leave big portions of the projects open-ended. When I do that, it's because I want you to try to finish them on your own. I encourage you to do that before looking at the full examples I've posted online. Every chapter concludes with a set of practice problems and pointers to more information, so I encourage you to complete those as well.
Teaching with This Book
I definitely cover things in a more 'computer-sciency' way than most books on this topic, so it might be a good fit for a course in computer science programs. Specifically, I cover mental models such as trees and hierarchical systems, and I try to emphasize functional programming approaches where they make sense (although I try not to draw attention to this in the narrative). If you find yourself teaching in a computer science program, you might choose to focus more clearly on these aspects of the material.
I currently have no plans to post solutions to the practice problems (although that may change if I get a lot of requests), so you can feel comfortable assigning them as homework and out-of-class projects.
Where to Go for Help
As mentioned before, there is a GitHub Repository with all of the code samples contained in this book. In addition, you can check out this page for errata and other updates as they are necessary.
I also try to stay pretty accessible and would be glad to help if you need it. Feel free to tweet at me @semmypurewal with quick questions/comments, or email me any time email@example.com with longer questions. I also encourage you to use the "issues" feature of our GitHub repository to ask questions. I'll do my best to respond as quickly as I can.
General Comments on Code
I've done my best to stay idiomatic and clear wherever possible. That said, those two goals are sometimes in conflict with each other. Therefore, there are times when I didn't do things "the right way" for pedagogical reasons. I hope that those places are self-evident to experienced developers, and that they don't cause any grief for novice developers in the long run.
All of the code should work fine in modern web browsers, and I've tested everything in Chrome. Obviously, I can't guarantee things will work in older versions of Internet Explorer. Please let me know if you find any browser compatibility issues in the Internet Explorer 10+ or modern versions of any other browser.
Thanks to the nice folks in the Computer Science department at UNC Asheville for letting me teach this class twice. And, of course, thanks to the students who took the class for being patient with me as this material evolved.
Thanks to my editor Meg Blanchette for doing her best to keep me on track and--of course--her constant patience with missed deadlines. I'm going to miss our weekly email exchanges!
Thanks to Simon St. Laurent for offering lots of advice early on and helping me get the idea approved by O'Reilly.
Sylvan Kavanaugh and Mark Philips both did a very careful reading of every chapter and gave lots of very helpful feedback along the way. Emily Watson read the first four chapters and gave lots of thoughtful suggestions for improvements. Mike Wilson read the last four chapters and gave invaluable technical advice. I owe you all a debt of gratitude and hope I can repay the favor one day.
Bob Benites, Will Blasko, David Brown, Rebekah David, Andrea Fey, Eric Haughee, Bruce Hauman, John Maxwell, Susan Reiser, Ben Rosen, and Val Scarlata read various revisions of the material and provided helpful suggestions. I sincerely appreciate the time and effort they put in. You rock!
Despite the all-around-excellence of the reviewers and friends who looked at the material, it's nearly impossible to write a book like this without some technical errors, typos, and bad practices slipping through the cracks. I take full responsibility for all of them.