A little energy-conciousness
I like when things take care of themselves. But before you can automate backups, the machine to be backed up has to be awake. Pennsardin — my big desktop tower running a RAID 5 array — has an annoying tendency to sleep deeply. Instead of leaving it powered on 24/7 just “for convenience,” I chose energy sobriety. My main server stays on, but the others only wake up when they actually have work to do — in this case, during nightly backups.
Running for a month : the debrief
It’s been a month since I got back into running, after several failed attempts. First victory: I’m still not injured! That’s already something. Of course, not everything went perfectly—far from it. What was planned When I started again at the end of September, my goal was simple: get moving again, be able to run for 30 minutes, and learn to run in easy endurance, all without getting hurt. Sounds easy, right? Well, the last two times I tried, I did too much, too soon—and boom, knee trouble.
Refurbished Thinkpad T480
I just wanted a machine to mess around with, test things, break things. Build and deconstruct — that’s how you learn. Basically, a computer for quiet evenings. Why not go for a refurbished one? I’d never tried that before, so I started browsing around. I quickly settled on Lenovo’s ThinkPad line: quality machines, easy to upgrade — RAM, drives, even the battery or screen. I didn’t need much power; I mostly wanted to test different tiling window managers at first. Even for RAM, 8 GB would be plenty.
Polar lied to me
I’ve been back to running for less than a month now — two sessions a week — and I still have a decent endurance base from hiking, including a mini-trek of 54 km over two days. Nothing exceptional, but enough to think I could handle some light training. Except… Since getting back into running, I’ve felt like a complete noob. Everywhere you read that to run in aerobic (zone 2) training, you need to stay in zone 2. Except…
Rewriting Git History: Changing Commit Authors
Recently, I took a bit of a turn — new direction, new mindset, new goals. I dropped some services, cut a few habits, and doubled down on others. It’s not the first time — and definitely won’t be the last. Every time, same story: new alias, maybe a new URL, and off we go again. This time, though, I wanted to change the authors of my Git commits — just to avoid looking like I’ve got multiple personalities committing to the same repo. You know, before someone starts suspecting schizophrenia.
Leaving the track
I skipped the second session this week. Or maybe I just hit my limit. Running in circles around a stadium — again and again — it wears you down. Last time, I finished strong, the last five minutes flat out. Today, I just needed air. Asphalt. Dirt. Exit the track. I started easy. Legs felt good. Bit by bit, I picked up the pace without really meaning to. It felt great — almost freeing.
NixOs update workflow
I update my NixOS systems once a week, on Sundays. Gone are the days of frantic updates on Arch Linux for a package that changes twice a day! I start on my desktop machine by updating the repositories and freezing the versions in Git. It’s my anchor point — the one that validates a successful update. nix flake update git add flake.lock git commit -m "FLAKE: update" git push origin master Then I update the desktop itself, with a bit of cleanup. I keep eight days of generations, which means I always have a complete, stable version from the previous week.
Against the clock
Tuesday, I was convinced I’d had a good session. I ran very slowly, stayed in the endurance zone, even managed to finish without any pain. In short, I thought it was a success. Except… today, after comparing, I realize I was completely wrong. ##xTuesday — the misleading session At the time, I thought I felt “fine.” But to avoid blowing up my heart rate, I had to slow down drastically — over 10 minutes per kilometer, almost walking. My Polar watch gave me a mediocre score, and I figured it was exaggerating.
Goaccess install on NixOs
When you self-host, there comes a moment when curiosity takes over. Who visits my site? At what time? Which pages actually get attention? And, sooner or later, the big question: Is anyone, anywhere, really reading what I write? You could go for Google Analytics or Matomo — but that comes with its own baggage: Questionable privacy practices, Third-party scripts injected into your site, Extra weight on every page, And a dependency on services I don’t want. GoAccess, on the other hand, takes the minimalist route. No scripts, no tracking, no cookie banner — it reads directly from the web server logs (in my case, Caddy) and generates a clear, efficient report.
It’s gonna be pitch dark… SHUT UP!!!
RRRrrrr!!! October 1st, 11 p.m. I clock out of work and the street is dead dark. No streetlights. The city flips into “winter mode” and leaves me with nothing but the moon to guide me. I walk home like I do every day—picked up the habit while losing weight. Two lousy kilometers, way too stupid to drive. But now it hits me: I can’t see shit. Safety? Yeah, not great, especially with headlights blasting in my face.
- 1
- 2