That’s probably not the canonical use case for garage 😅
That’s probably not the canonical use case for garage 😅
My little cluster is getting into shape.
- miniflux for RSS
- continuwuity + n8n for automation (not used yet)
- soju for IRC
- garage for easy hosting of static files
(I am still trying to wrap my head around that tbh)
Maybe it is a mirage, but when I see now some folks don’t write libraries anymore, they provide prompts that generate the libraries and a test-suite to validate the generated implementation, that’s telling imo
I am under the impression the current direction is to stop caring about the little things in the code, treating it almost as an artifact akin to binary blob, and to put in place the safeguard and validation procedure to ensure these artifacts behave as expected.
The best refactor is actually the one everybody notices because they were dying to do it themselves 😁
Be careful is all 😅
I’ve read a few MRs related to the change and I can only commend the dedication
That feels like something that should have been obvious from the start but once you codebase assumes it’s not, it makes so much sense it was hard as f– to fix. Glad we’re about to see that moment happens!
So XMPP is a little weird. I wanted to use it has a n8n control plane of sorts but I think Matrix will be a better fit
Claude Code does not deal with frustration very well.
I really don’t like the pets vs cattle DevOps Analogy
It’s more like pottery vs 3D printing
The bliss of watching all the VMs running my k3s cluster being destroyed and recreated, and everything comes back to life.
oh no they scraped your stuff without permission oh no
A screenshot with a section heading: “Why Kubernetes?”
What can go wrong?
A photo of an ice cream machine with a sign reading, "Anything is possible with ice cream." Beneath that is a hand lettered sign reading, "No ice cream".
2026 basically
It’s shaping up nicely. Won’t be able to finish it today, but I should be able to publish it in a few days.
I hope it will have a similar reach as my previous infrastructure piece
i'm back on IRC 😎
They say we all be act as manager—well, I feel more like a mentor for a very fast, but very naive hire.
Claude Status SUBSCRIBE Intermittent errors in skills-related functionality Subscribe Update - We are continuing to investigate this issue. Feb 18, 2026 - 00:30 UTC Investigating - We are seeing periods of high error rates in a skills-related service used by claude.ai, Claude Desktop app, and our API. Feb 17, 2026 - 20:15 UTC
skill issue
Thank you Claude!
I'm in my text editor, looking at some Rust code, hovering a rule, the rule is named daemon.logs.file. It says the daemon must provide all log output to .tracy/daemon.log in the workspace root.
just fixed tracey hover — so you can see the rule you're implementing just by hovering it
github.com/bearcove/tra...
A screenshot of my next article draft, titled “I Built Myself a Managed Cluster”.
My favorite time of a hobby project.
I have deployed a miniflux instance tonight. If you are looking for a RSS reader and don’t mind it’s not professional grade SLA feel free to reach out
Guess whose idea was deployed?
Claude being like “your idea is nice but for your *scale* that’s no use, let’s go back to *my* idea.”
I mean, excuse me? you’ll spend the next 10 minutes exploring my idea is what will happen.
I can now redeploy my cluster control plane without my website to go down 🎉.
hi folks! long time no see. i’m officially open to work again, primarily interested in the dx + devtools + ai space
if anyone needs a principal engineer or technical product manager with 16+ years in the industry, my DMs are open!
linkedin.com/in/leostera
github.com/leostera