500 Lines or Less
"What I cannot create, I do not understand."
-- Richard Feynman
This is the source for the book 500 Lines or Less, the fourth in the Architecture of Open Source Applications series. As with other books in the series, all written material will be covered by the Creative Commons - Attribution license, and all code by the MIT License: please see the license description for details. In addition, all royalties from paid-for versions will all go to Amnesty International.
The production of this book has been made possible by the financial support of PagerDuty.
Every architect studies family homes, apartments, schools, and other common types of buildings during her training. Equally, every programmer ought to know how a compiler turns text into instructions, how a spreadsheet updates cells, and how a database efficiently persists data.
Previous books in the AOSA series have done this by describing the high-level architecture of several mature open-source projects. While the lessons learned from those stories are valuable, they are sometimes difficult to absorb for programmers who have not yet had to build anything at that scale.
"500 Lines or Less" focuses on the design decisions and tradeoffs that experienced programmers make when they are writing code:
- Why divide the application into these particular modules with these particular interfaces?
- Why use inheritance here and composition there?
- How do we predict where our program might need to be extended, and how can we make that easy for other programmers?
Each chapter consists of a walkthrough of a program that solves a canonical problem in software engineering in at most 500 source lines of code. We hope that the material in this book will help readers understand the varied approaches that engineers take when solving problems in different domains, and will serve as a basis for projects that extend or modify the contributions here.
|Name||Affiliation||Project||Online||GitHub||Email (if you choose)|
|Audrey Tang||g0v.tw, Socialtext, Applefirstname.lastname@example.org|
|Taavi Burns||Previously at Points, now at PagerDutyemail@example.com|
|Guido van Rossum||Dropboxfirstname.lastname@example.org|
|A. Jesse Jiryu Davis||MongoDBemail@example.com|
|Ned Batchelder||edX||templating firstname.lastname@example.org|
|Leah Hanson||static email@example.com|
|Christian Muise||University of Melbournefirstname.lastname@example.org|
|Cate Huston||Image Filter email@example.com|
|Yoav Rubin||Microsoft||In-memory functional database||yoavrubin|
|Dessy Daskalov||Nudge Rewards||Pedometerfirstname.lastname@example.org|
|Carl Friedrich Bolz||King's College London||object email@example.com|
|Jessica Hamrick||University of California, Berkeleyfirstname.lastname@example.org|
|Allison Kaptur||Hacker School||byterun||@akaptur||@email@example.com|
|Daniel Rocco||BrightLink Technology||contingent||@firstname.lastname@example.org|
|Dann Toliver||Bento Boxemail@example.com|