I lead all things technical during the day and take things apart for fun the rest of the time. CTO at @washmore
I learn by building. Pick something I don't understand, start constructing, hit a wall, research through it, keep going. Repeat until it works or until I've learned enough to ask a better question. Most of what I know came from that loop running a few thousand times.
The repos here are what happens when curiosity meets a free weekend or late night Some are polished. Most aren't. All of them taught me something.
None of these are practiced perfectly — but they fail loudly when I ignore them.
be organized — Work like you'll inherit your own mess in six months.
always be learning — "I don't know" is a starting line, not a finish.
over-engineer some, ship the rest — One builds depth. The other builds momentum. Pick honestly.
determination > motivation — Motivation leaves when the dopamine does. Determination is a choice you keep making.
enjoy the process — The interesting part isn't the result — it's the version of you that emerged from building it.
languages
infra & ops
hardware & home
