./cipher -e 212103553030 Euler
./cipher -d 212103553030 2zVrY
./cipher -e 621035533002 Euler
./cipher -d 621035533002 "Lntl'"
./cipher -e 464541032011 Euler
./cipher -d 363630030122 47V6Û
./cipher -e 552200553344 "Dennis Ritchie"
./cipher -d 552200553344 "Dennis Ritchie"
./cipher -e 522552255225 Mandelbrot
./cipher -d 522552255225 i,udle46}f
./cipher -e 522552255225 "Allen Newell"
./cipher -e 212103553030 "Alan Turing"
./cipher -d 212103553030 0VpW@ÚzYtWs
./cipher -e 621035533002 "Stephanie Forrest"
./cipher -d 621035533002 "Ïfl&4,u<l E}''l/f"
./cipher -e 621035533002 "Kurt Gödel"
./cipher -e 621035533002
./cipher "Kurt Gödel"
./cipher -f 621035533002 "Kurt Gödel"
./cipher -e 62103553300 "Kurt Gödel"
./cipher -e 621035538002 "Kurt Gödel"
./cipher -e 212103553030 "Another effective debugging technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes it takes no more than a few sentences, followed by an embarrassed, Never mind, I see what's wrong. Sorry to bother you. This works remarkably well; you can even use non-programmers as listeners. One university computer center kept a teddy bear near the help desk. Students with mysterious bugs were required to explain them to the bear before they could speak to a human counselor. -- Brian Kernighan and Rob Pike (The Practice of Programming)"
./cipher -d 464541032011 "J? v+::b) b:f6#2/6: j? *f:2;92s) j#:f:<v j#: fz&"