technically a blog
- #accessibility (3)
- #advent-of-code (1)
- #advice (1)
- #ai (7)
- #aid (1)
- #april-cools (1)
- #art (3)
- #ask-nicole (1)
- #backups (2)
- #books (6)
- #career (1)
- #chess (5)
- #cnc (1)
- #coffee (1)
- #conference (1)
- #containers (2)
- #databases (8)
- #debugging (4)
- #devops (4)
- #documentation (1)
- #electronics (1)
- #ergonomics (2)
- #ethics (9)
- #formal-methods (1)
- #fp (1)
- #git (1)
- #goals (2)
- #golang (3)
- #heresy (2)
- #history (1)
- #homelab (3)
- #humor (8)
- #hurl (5)
- #language (1)
- #leadership (5)
- #licensing (1)
- #management (3)
- #math (2)
- #naive (1)
- #neovim (1)
- #networks (1)
- #neurodivergence (1)
- #ohio (2)
- #on-call (1)
- #one-day-build (1)
- #open-source (4)
- #pair-programming (3)
- #paper (5)
- #performance (6)
- #personal (7)
- #philosophy (2)
- #pi-day (2)
- #pl (7)
- #practices (9)
- #presentation (1)
- #profiling (3)
- #programming (38)
- #python (5)
- #recurse-center (16)
- #reflection (5)
- #remote (2)
- #review (7)
- #rust (24)
- #safety (2)
- #scam (1)
- #security (8)
- #server (1)
- #simulation (1)
- #software-engineering (38)
- #sourcehut (1)
- #speculation (2)
- #systems (2)
- #teams (3)
- #terminology (1)
- #testing (4)
- #theorem-provers (1)
- #theory (1)
- #til (3)
- #trans (4)
- #values (3)
- #vim (1)
- #visualization (1)
- #web (1)
- #work (23)
- #workshop (1)
- #writing (6)
- #yaks (1)