Why I started Lorebow
I kept forgetting what I'd learned, and words alone never brought it back. Lorebow is where I put it back together, drawn out so it sticks.
Working in tech, across software, infrastructure and DevOps, I'm always learning something new. A tool, a platform, a different way to build or run things. For a long time I kept notes so I wouldn't have to learn the same thing twice. Then, months later, this happens:
$ grep -ril "rolling update" ~/notes /home/k/notes/k8s/deployments.md $ cat ~/notes/k8s/deployments.md ## Rolling updates - maxSurge 1, maxUnavailable 0 - don't forget the readiness probe thing!! $ # what readiness probe thing?
The words were all there. The picture I'd had in my head when I wrote them was gone.
That's where Lorebow comes from. I wanted a wiki for my brain: somewhere to put what I learn so that coming back to it is quick, even after I've forgotten.
#Words weren't enough
Some ideas are hard to get from text, however well it's written. You can read every word and still not see it. What stays with me is the idea I've watched happen, especially when it lands next to something I already know:
1.Words alone
You read an explanation and it makes sense. A month later, most of it is gone.
So on Lorebow, if something moves, I show it moving. Diagrams step through what happens, one stage at a time. Commands type themselves out the way they would in your own terminal.
#What keeps me going
These are the values I've written by since my first notes on karchunt.com, and Lorebow runs on them too. None of them works alone: each one feeds the next, all the way round. Pick one to see where it sits.
1.Build with passion
Passion means everything to me. It's what keeps me going when something is hard, and why I want to build things that could make a real difference.
That's also why this site is public. I love helping people learn, and if I got stuck on something, someone else probably is too, right now.
#Where it starts
I'm starting with software, because it's what I know best. More topics will follow, and later other fields.
I'm not doing it alone, either. R draws the diagrams and L runs the terminals. You'll meet them on almost every page.
The name says what I'm going for. Lore is the knowledge people pass on. A bow ties loose threads together, so each idea gets its own page and every page is tied to the ones it builds on.
If a page here helps you understand something, or keeps you from giving up on it, I'd love to hear about it. That's the best message I could ever get.
Comments
Sign in with GitHub to comment. Comments are kept as GitHub Discussions.