Introduction

Mastering a programming language or framework demands more than merely reading through the documentation or cruising through one tutorial; it requires that you read a ton of code written by other developers. For the same reason, art museums don't have works from only one painter, or Beethoven's symphonies aren't written for one instrument, or the best technology companies don't rely on the ideas of one engineer. Complex, analytical, and creative thoughts are best stimulated by multitudinous, diverse, and often orthogonal channels of input. Gleaning the inner machinations of someone else's mind by dissecting their work is an intensely intimate and educational process, and reading their code will provide you with an escape from the echo chamber of your own mind.

As you consume more and more code, you will be inundated with an understanding of the idiomatic methodologies that can make a great technology just a little bit better. Often, within that code...