more files

files/bumper-stickers.txt

@@ -0,0 +1,10 @@
+Pi seconds is a nanocentury.
+The sooner you start to code, the longer the program will take.
+Testing can show the presence of bugs, but not their absence.
+The first step in fixing a broken program is getting it to fail repeatably.
+Electricity travels a foot in a nanosecond.
+Whenever possible, steal code.
+Don’t use the computer to do things that can be done efficiently by hand.
+Don’t use hands to do things that can be done efficiently by the computer.
+Eschew clever rules.
+The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time.

files/five.txt

@@ -0,0 +1,5 @@
+one
+two
+three
+four
+five

files/words.txt

@@ -0,0 +1,10 @@
+one
+one two
+one two three
+one two three four
+one two three four five
+two three four five
+three four five
+four five
+five
+one-two-three-four-five-six-seven

files/words2.txt

@@ -0,0 +1,5 @@
+0 1 2 3 4
+5 6 7 8 9 
+0 1 2 3 4 5 6 7 8 9
+zero one two three four 
+five six seven eight nine

files/zen.txt

@@ -0,0 +1,21 @@
+The Zen of Python, by Tim Peters
+
+Beautiful is better than ugly.
+Explicit is better than implicit.
+Simple is better than complex.
+Complex is better than complicated.
+Flat is better than nested.
+Sparse is better than dense.
+Readability counts.
+Special cases aren't special enough to break the rules.
+Although practicality beats purity.
+Errors should never pass silently.
+Unless explicitly silenced.
+In the face of ambiguity, refuse the temptation to guess.
+There should be one-- and preferably only one --obvious way to do it.
+Although that way may not be obvious at first unless you're Dutch.
+Now is better than never.
+Although never is often better than *right* now.
+If the implementation is hard to explain, it's a bad idea.
+If the implementation is easy to explain, it may be a good idea.
+Namespaces are one honking great idea -- let's do more of those!