I have a GitHub account filled with repositories and a personal site I rewrite far more often than I should. What I never had was a place to actually write why any of it exists, and what broke along the way (for example). So, here.
The short version: I work in infrastructure, mid-level dev. CI/CD, containers, some Go and Python, some DevEx along the way. Boring specifics live on my resume; this isn't that. Desktop runs Arch with the CachyOS repos (yes, i use Arch btw - now it's even documented).
What this is going to be about, roughly in order of how often it'll show up:
- logs of how I set something up, configured it, or fixed it, and what went wrong on the way (something always does);
- notes from real work and side projects;
- the occasional "look what I built" just to save it somewhere, sometimes just so the version of me 6 months later remembers.
A word on the bar, which is set low on purpose. Nothing here is "do it my way, I know the correct one." It's closer to "here's what I tried, most of it worked, the rest is taste." I'll be wrong in places, I might even disagree with some of this half a year later, and that's fine. Knowing something might get read makes you check your own work harder than writing for nobody ever does. This also means some of those articles might get silently rewritten to a whatever better version next-year-future-me finds better.
The site itself is its own thing. It's partly a business card and partly a playground: custom CSS, vanilla JS, zero frameworks, and an almost unhealthy race to shave off bytes nobody but me will ever notice. Optimizing a page that maybe 1.5 people will open down to the last kilobyte is, objectively, a questionable way to spend an evening. I like it anyway, and you do come out understanding how the whole thing works under the hood. Source is open, by the way: github.com/hekzory/hekzory.github.io.
Useful to anyone else? Maybe. Useful to me? Definitely - if only as external memory.
Anyway. Let's go.