Practitioner of what? What is a "wide event"? In what context is this concept relevant? It took several sentences before I was even confident that this is something to do with programming.
Sure, but it would be nice if title submissions made it feasible to predict the topic category of the article for people who are not already in the relevant niche.
> Adopting Wide Event-style instrumentation has been one of the highest-leverage changes I’ve made in my engineering career. The feedback loop on all my changes tightened and debugging systems became so much easier.
What I get is: here's a thing that made a big improvement to how I debug systems.
Except, it turns out that the systems in question are very specific ones.
> The tl;dr is that for each unit-of-work in your system (usually, but not always an HTTP request / response) you emit one “event” with all of the information you can collect about that work.
Okay, but... as opposed to what? And why is it better this way?
>“Event” is an over-loaded term in telemetry so replace that with “log line” or “span” if you like. They are all effectively the same thing.
In the programming I do, "event" doesn't mean anything to do with logging or telemetry.
I had to lookup wide events in the middle of the article, and I can’t say I can viscerally see and feel the benefits the OP was espousing. Just felt like an adderall-fueled dump of information being thrown at me.
"Observability" seems like a weird term for that to me, but okay.
But I don't understand why not just give the appropriate context in the submission, rather than keeping a title that only makes sense to a very specific niche audience and then not saying up front what the niche is.
The concept of an "event" is coherent in many other programming contexts, so the possibility that one could be coherently "wide" is at least plausibly interesting. But then I get there and find myself completely disoriented, and eventually figure out that it's not actually relevant to anything I do. And anyway it looks like a lot of this jargon is really just not necessary to convey the core ideas... ?
That's how I would have titled it.
I get that HN isn't appealing to the general population, but the world of programmers etc. is still quite broad.
You are obviously the one who is not understanding or is perhaps misunderstanding something.
Observability is a pretty standard term in software development.
Events have nothing per se to do with logging or tracing, but you can visualize/trace events with logs/spans.
From my perspective, you seem to misunderstand a lot in the article, I am not judging you for that, just observing this.
I suggest you try to understand the gist of the article instead of scolding the language used.
You’re being unreasonable about this IMO.
Again: not judging, just observing.
Consider that you are perhaps the minority ¯\_(ツ)_/¯
(I wrote it mostly so I could stop re-explaining this concept from first-principles and how to go about implementing it over-and-over again )