rust becomes the tool

by october i'd stopped studying rust and started just using it to make things. the questions changed from how does this work to make me a tool that does this. i was figuring out what i liked by building it

things in the terminal

i liked the terminal. a ratatui example that scrolls. a background widget. a game ui with borders and blocks. a demo of shared state with arc and mutex. these weren't coursework. i was trying out what a terminal could draw, and it was fun

servers

the earliest notes had a multithreaded server. october brought a kanban board in async rust — a web page where changes show up for everyone live. i built it to learn websockets and real-time web without using a framework. it worked, and that felt like a real thing

sound

rodio played a sinewave, then a provided sine source. later a tinnitus simulator, generating randomized waves to mask high-frequency tones. sound from code, with no window at all. i was curious whether the terminal could be more than text, and it could

the borrowed discipline

rust kept teaching me the hard way. borrowing errors. checked subtraction. the compiler refusing to let shared state slip. each error a small lesson in ownership — you can't share what you haven't lent. i carried that mental model everywhere after

造 is to make. by the end of october that was the whole point — not studying, making things that work