Origami Around
đȘŒ
pixel skylines
YOU ARE THE REASON
occasionally subtle
let's talk about Bridgerton tea, my ask is open
izzy's playlists!
Monterey Bay Aquarium
The Stonewall Inn
noise dept.
No title available
No title available
⣠Chile in a Photography âŁ
macklin celebrini has autism
Today's Document
romaâ
tumblr dot com
Noah Kahan
KIROKAZE
almost home
seen from Germany
seen from France
seen from Germany
seen from Uzbekistan
seen from Uzbekistan
seen from Uzbekistan
seen from Uzbekistan
seen from Uzbekistan
seen from Singapore
seen from Australia
seen from Kuwait
seen from United States
seen from United States
seen from United States
seen from United States
seen from United States
seen from TĂŒrkiye
seen from United States
seen from United States
seen from United States
@kmsigma
Your Dashboards Are Bad and You Should Feel Bad
The name and inspiration for this post comes from an excellent resource Iâve had to the pleasure of knowing for several years. Nick, Iâve shamelessly stolen it. Iâve been building dashboards for nearly twenty years. Some were good. Some were terrible. Most were somewhere in between. If youâve built dashboards in an IT environment, youâve probably had the same experience. So, this isnât a shameâŠ
Breaking Down a Complex System So Anyone Can Understand It
Iâve spoken about documentation and the growing divide between the systems we design and the end users consuming such systems, but thereâs something almost ephemeral that bridges the two: learning how to break down a story. Iâve always had a passion for learning different things â outside those that are part of my career â and thatâs helped me build up a generous thesaurus of analogies. IâveâŠ
The Care and Feeding Playbook: How to Build a Community That Lasts
If you read Communities Fail When Theyâre Treated Like Features, you already know the problem. Treat community like a feature and it will behave like one: temporary. This is the hands-on playbook. This is the stuff you can use tomorrow. I wrote this from the inside. I was a community manager, a product manager for products discussed on that community before that, and a member as a customerâŠ
Communities Fail When Theyâre Treated Like Features
Letâs be blunt: building a community and checking boxes look the same on a roadmap. Both get resources assigned, both get line items, both can be marked âdone.â But they are not the same thing. A community is a living system. It grows, it needs food, it gets sick, and it thrives when people care for it. Treat it like a feature â something you ship, measure by a single metric, and forget â and itâŠ
Why Enrichment turns Logs into actual Observability
Logs are often treated as if theyâre complete, atomic truths: a line appears, something happened, and thatâs the end of the story. But anyone who has ever tried to build real observability knows that a single log line rarely tells you anything meaningful. Logs are fragments. Observability is the reconstruction of what those fragments actually mean. The difference between the two isâŠ
Documentation is the Product (We just Pretend it Isnât)
Thereâs a quiet truth in every technical organization: documentation is the product. Not the UI. Not the API. Not the architecture diagram. Documentation is the thing that determines whether people can actually use what we built. But we rarely treat it that way. We treat documentation like a side quest. Itâs something weâll âget to later,â something thatâs ânice to have,â something that existsâŠ
The Gap Between Users and Systems (and Why It Still Exists)
Picture it: Youâve spent weeks and weeks building a new observability stack. Everything is in there: metrics from servers, traces from various applications, details about APIs, synthetic transactions, even NetFlow. Youâve reached monitoring nirvana â everything is in there and it looks beautiful. You present it to the management, the application owners, the other teams, and⊠crickets. UntilâŠ
Inside My Observability Stacks (and Why I Built them this Way)
At some point, reading about observability stops being enough. You actually have to build something. In my case, that turned into building not one, but two different stacks that Iâm running side by side. One built around Elastic, the other taking a different approach with Prometheus. The goal is not to pick a winner. It is to understand how they behave in the real world. Which has beenâŠâŠ
Weâre not short on data. Weâre short on understanding. This series explores how complex systems become something people can actually use, combining observability, product thinking, and a focus on user education. Basically, turning technical garble into understandable stories.
Why I Shipped It as a Docker Container
In part 1 I wrote about why I built this. In part 2, I wrote about some design decisions. In this part Iâll explain why I wanted Docker as the platform. Docker Was a Product Decision Docker isnât just packagingâitâs User Experience (UX). The goal was: âYou can deploy this in under a minute.â With Docker, that becomes: docker run -p 4278:4278 kmsigma/utm-qrcodes:latest No SDKs. No installs.âŠ
I got tired of UTM + QR code tools that required accounts, stored my data, or charged for basics. So I built a selfâhosted, openâsource alternative in .NETâno DB, no auth, no tracking. I just published a blog post explaining the why behind it.
I love the promise of a fully automated IT infrastructure, but regardless of platform, the future is still unknowable.
I'm on a personal mission to backup everything important in my home lab. First up is my #pihole devices providing DNS filtering. And I'm doing it via #PowerShell because I'm me.
Convert PowerShell ISE Snippets to VS Code
I cut my teeth with PowerShell ISE and still have fond memories of it. But VS Code now rules my world â and thatâs ok. Moving forward is progress. But one of the annoyances Iâve had since moving my PowerShell coding from the ISE to VS Code is the lack of the original snippets. In truth the PowerShell snippets that ship with VS Code are (generally) vastly superior and I use them all the time. ButâŠ
It's my 10 year anniversary on Tumblr đ„ł
I'm just here for the Terry Pratchett posts and fan-fic (good or bad).
I was thinking about my docker setup and how I don't have a good way to backup my volumes. It led me to a PowerShell script (of course it did).
PowerShell Modules can be Painful
Preamble Building a PowerShell module should not be too hard. In fact, on the surface itâs pretty simple. Collect a bunch of functions, classes, enumerations, (whatever else you want), bundle them together and provide a wrapper in the form of a PSD1/PSM file. My go-to reading and guidance material for this is PowerShell Scripting in a Month of Lunches. Building a module should be straightforwardâŠ
View On WordPress