Why Enrichment turns Logs into actual Observability
In my opinion, true observability comes from enrichment—connecting fragmented log lines into coherent events that actually explain what happened.
-
-
Documentation is the Product (We just Pretend it Isn’t)
Docs aren’t an afterthought – they’re the product’s voice. When they fail, the system fails with them.
-
The Gap Between Users and Systems (and Why It Still Exists)
Systems work as designed, but users build their own mental models. When those diverge, adoption stalls. The gap isn’t complexity — it’s translation.
-
Inside My Observability Stacks (and Why I Built them this Way)
What’s in a stack? Elastic or Prometheus or something else altogether? This isn’t about “better,” it’s about answering the real questions.
-
Observability isn’t about Metrics. It’s about Understanding
More data does not mean more clarity. Observability only works when people can actually understand what they are looking at.
-
Systems, Stories, and Signals
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.
-
Why I Shipped It as a Docker Container
Docker wasn’t an afterthought—it was part of the design.
Why Docker? Learn why my UTM + QR code builder ships as a hardened, non‑root container. -
How the App Works: A Simple Stack by Design
“Simple” software stack is often harder to design than complex systems.
Now it’s time to explain how my UTM + QR code builder works (without code). -
Why I Built a Self‑Hosted UTM & QR Code Builder
If you’ve ever pasted a campaign URL into an online QR code generator and thought, “Where else is this data going?”—this project is for you.
