diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2015-05-15 23:01:37 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2015-05-15 23:01:37 -0700 |
commit | 9846759ef887eb5f71ff2f12fdad8f308adbda40 (patch) | |
tree | faacd5873c4bbeca9345d9f25f807ecd86dcd90b | |
parent | 87ef6a67a37ccb3e5e1568738631d9059f9d2019 (diff) | |
download | mu-9846759ef887eb5f71ff2f12fdad8f308adbda40.tar.gz |
1381
-rw-r--r-- | Readme.md | 15 |
1 files changed, 14 insertions, 1 deletions
diff --git a/Readme.md b/Readme.md index 9f59b35e..27a1053b 100644 --- a/Readme.md +++ b/Readme.md @@ -317,7 +317,20 @@ allocator and a few other places). --- -Try running the tests: +If you're still reading, here are some more things to check out: + +a) Look at the [chessboard program](http://akkartik.github.io/mu/html/chessboard.mu.html) +for a more complex example where I write tests showing blocking reads from the +keyboard and what gets printed to the screen -- things we don't typically +associate with automated tests. + +b) Try skimming the [colorized source code](http://akkartik.github.io/mu). I'd +like it to eventually be possible to get a pretty good sense for how things +work just by skimming the files in order, skimming the top of each file and +ignoring details lower down. I'd love to hear feedback about how successful my +efforts are. + +c) Try running the tests: ```shell $ ./mu test |