A typing test for people who live in the terminal. I kept tabbing out to a browser to warm up, so I wrote the thing I kept opening. Code modes (Go, SQL, Python, shell, regex), keystroke replays, a wpm chart, and a heatmap of the keys you actually miss. One static Go binary.
curl -fsSL https://raw.githubusercontent.com/alirezaudev/ttype/main/install.sh | shI rebuild tools I use every day to see how they work, with the standard library only. Each one came down to one trade-off:
| The problem | What I did | What it costs | |
|---|---|---|---|
 |
A hundred clients share one map. A command that reads and then writes must not have another client land in between. | One goroutine owns the map. Every command is a message to it, so each one runs whole. | Commands run one at a time, on one core. Real Redis makes the same trade. |
 |
A reply repeats the same name in every record and has to fit in 512 bytes. | Point back at bytes already sent (name compression). | Every parser now follows pointers written by strangers. A hostile packet can loop them forever, so I stop at 20 hops. |
 |
On a reused connection, a handler that skips the body leaves the next request starting mid-sentence. | Drain whatever the handler didn't read before parsing the next request. | Mine reads all of it, so a client can make me read 10 GB nobody asked for. net/http drains 256 KB, then hangs up. |
Silver medal, Quera Tech Olympics 2024 (PHP/Laravel) · practice and older work in alirezaudev-archive