Tales of
not a highlight reel, just what actually happened
Tales of OpenEverest
I'm learning Go by actually contributing to a real project. Not a course, not a tutorial series, an actual codebase called OpenEverest with real maintainers who review my stuff and tell me when I'm wrong. This is where I'm writing all of it down as it happens, before my memory cleans it up into a better story than what actually went down.
what’s actually here
- blog: the issues, the PRs, the review comments that made me rewrite something, in the order they happened.
- about openeverest: what this project even is, in case you land here first.
- architecture: my own notes on how it’s built, from reading the actual code, corrected as I understand more.
- learning go: concepts I write up only after I actually needed them for something. no generic “go for beginners” filler.
why openeverest specifically
I wanted a codebase big enough that I couldn’t fake my way through it, and maintainers who’d actually push back if a PR didn’t hold up. Got both. First fix I shipped got two rounds of review before it was right.