Learn from teacher, author and master programmer Zed Shaw's reflections on the art and craft of writing code. Topics covered include: the role of source code control; Writing readable code; The process of understanding and solving code problems; and Testing
Zed Shaw is one of the most original thinkers and prolific programmers currently active in Open Source. In 2006 he kick started the Ruby web application server market and continues it with the Mongrel2 server. He's an expert teacher and has taught over 300,000 people with his free book Learn Python the Hard Way. In this screencast he builds a code stats tool for tracking errors and warnings. But we think you'll appreciate most the conclusion of the project where he talks about the things he learned from using a previous implementation of a code statistics tool for a full year.
Introduction [Autogenerated] it's a code. Zed Shaw's one of the most independent thinking and productive programmers acts even open. Source today kickstarted the Ruby Web App server market back in 2006 with the Mongrel Server. He's an accomplished teacher with over 300,000 downloads of learned Python the hard way. He continues to produce high quality open source code such a CZ, the Lampson email server and other side projects like friend or a site. For musicians, it's too limiting to refer to Zed is a Ruby Esty, python ista or a C head. Is it heart a programmer and has spent more time than you? Are I thinking about programming and has even run hard numbers to figure out how to do it better in this screen cast, I asked said to recreate the functionality of a project he wrote a long time ago. It's a project to keep track of coding, statistics, test runs, errors, warnings, failures, commits and other metadata such a cz lines of code written. I think this whole screen cast is worth watching, but I'm especially proud of the half hour conversation we had after the project was mostly done, so I've put that in the beginning you'll see the finished project. And then here's Ed opine about software development and the things he learned for recording statistics of his own coating for about a year. Keep watching to see four chapters of development of that tool from scratch. Here's a small sampling of what you'll learn Make it to do list and follow it. Make small, frequent changes. Take breaks always right in else on your If statements use a variety of testing methods code that requires knowledge of its past. History will probably be unreadable. The purpose of writing code isn't to write code. It's to understand and solve problems. Source. Code control is communication. This is the peep code. Play by play Siri's. As such, it's about watching expert developers work. We won't stop to explain much, and some concepts will fly right by. So use the pause button or rewind if you need to hear something again. We've added a bunch of chapter markers throughout to make it easy to jump to specific sections or quotes