The Brief#
So…I build things. Automation that exposes organizational dysfunction and gives it a viking funeral. Terminal configurations that make GUI-centric people question their life decisions. Systems that eat toil for breakfast and make everyone’s lives better. Custom keyboards that shouldn’t exist and whatever else catches my interest that week.
This all started with me building a solar-powered knowledge vault project. It has evolved into my tech playground - the place where I document everything I’m experimenting with, from nvim configs to AWS automation to vibe coding techniques that are unorthodox but get the work done.
If it’s not documented, it didn’t happen. And if it happened, it belongs here - warts and all.
The Setup#
Day Job:
- SRE Manager
- Building tools that make this work less painful
- Making space to allow others to make cool stuff
Night Projects:
- Scrying: AI-powered documentation that generates diagrams and in-depth analysis of the code present and how data flows
- Raptor: Full end-to-end TUI and CLI for tracking jobs and applications and customizing your resume
- Random other stuff I want to dive into
Philosophy:
- If it can be automated, it should be…especially toil-rific processes
- Failure is an option, it’s how we learn, it’s just content waiting to happen
- Terminal is beautiful, live in it
- Documentation isn’t toil, it’s how you prove it works
What You’ll Find Here#
Automation & Tooling:
- Tools that find organizational gaps and fill them
- Infrastructure as code that kind of sorta doesn’t suck
- Security tooling that actually helps people
Terminal & Workflows:
- Nvim configurations and why they matter
- Dotfile deep-dives
- CLI-first development on my Mac, no Windows anything
- Obsidian vault structures for knowledge management
Hardware & Making:
- Custom mechanical keyboard builds (ZMK firmware adventures)
- Badge teardowns and repurposing
- Electronics projects that 20% of the time work 100% of the time
Vibe Coding:
- How I scaffold systems with AI in just a few hours
- Pair programming with Claude
- When AI makes you better vs when it makes you lazy
Experiments That Didn’t Work:
- This is the best ones to document, failure is where learning actually happens
- Sneak Peek: There will be many…so so many
The Why#
I’m tired of people locking knowledge behind paywalls, or proprietary systems or recipe blog like videos. I want things I mess up or figure out to be here. I want my optimizations that work and don’t work - I want it here.
This is not going to be a polished portfolio. This is going to be the actual ugly process of birthing something from my brain into whatever I think it needs to be, complete with dead ends, decisions that boil down to “why not”, and the “uhhh it works..why does this work? It shouldn’t work?”
This gives me the excuse of buying more electronics and calling it “research.”
The Journey#
I started this as an off-grid computing project, which I will continue. It evolved into whatever this is now - a technical blog? A knowledge base? A way of putting my code where my mouth is? Proof that I can build shit like I claim to?
If you’re here, you probably went to page 4 of Google, or you’re the kind of person who opens config files and just goes “what’s this do?”. Welcome to my chaos!
“Build, Fail, Learn, Repeat”