Programs that "Read like a story" have good decomposition and make the code easy to follow. When programming, you're writing code for other people to read, so you want to communicate the "story" of the program clearly. It's good practice to [break down][1] your code into functions whose names tell exactly what is happening in that function. You can think of the function names as the names of the chapters, so the start function is like the table of contents. [1]: http://codehs.com/glossary/term/7
