"I don't wait to understand everything before I build — I build until I understand everything."
Every trajectory has equations behind it. Mine runs through pure C, Rust TUIs, x86 Assembly written register-by-register, and Python tooling that ships to real package managers. I don't wait for permission to explore a new layer of the stack — if it compiles (or doesn't), I want to know exactly why.
| Package | What it does | Install |
|---|---|---|
| letx | Modular Python developer toolkit — smarter debugging, plain-English error explanations, and code cleaning from the terminal | pip install letx |
Personal git standup tool written in pure C. See what you committed by day, week, month, or year. No dependencies — just git. Ships on both winget and an Ubuntu PPA.
$ git-recall --week
$ git-recall --month -2 # last 2 months
$ git-recall --day > recap.txt # pipe to file
paimon Rust JavaScript
Keyboard-driven Rust TUI for injecting code snippets and project structures into your working directory instantly. Snippets are embedded inside the binary at compile time — no internet, no Python, nothing extra needed.
$ paimon --code -ls
# ↑↓ navigate ENTER select ← back q quit
letx Python
Modular Python CLI toolkit. Debug smarter with plain-English error explanations, get fix suggestions, and clean your codebase — all from the terminal.
$ letxDebug -a my_script.py # run + explain + suggest fix
$ letxFix -rm -cmt src/ # strip all comments from a folderASSAMBLY x86 Assembly
63 Assembly programs written register-by-register — animated ASCII bouncing balls, a desktop-lite shell, quadratic equation graph visualizations, GCD, Hamming weight. Most devs skip this layer. I didn't.
