Viewing profile — sagichmal

Yup. Somewhat formalized: https://peter.bourgon.org/blog/2018/08/22/observability-sign...

This is definitely not true (shrug) Attrition has more than doubled and most engineering teams are critically understaffed.

Most do, though, because there does tend to be a more correct position on this class of stuff.

> A handful of people left They lost close to half of their engineering team, significant percentages of their operations teams, and many senior leaders.

No, I don't know anyone at Basecamp.

I'm not sure why you think people who care about justice harass coworkers as a matter of course. It's strictly the opposite, in my (considerable) experience.

(laughs) OK dude.

I’m not sure why you think people who care about justice draw that energy from the same pool that motivates their work, as if it’s a zero-sum calculus. It isn’t. People who think a…

Friends in engineering at Coinbase?

My point is that DEBUG level logging is (hopefully!) not on by default, and that this is what it makes the production log volume manageable. My experience has been that 1 customer-…

They lost almost half of their engineering team. Product development has almost stalled. I dunno, man.

"People like [the OP]" are in my experience consistently better at what they do than the sort of folks which Coinbase is now apparently soliciting.

Yes. All of the "private" correspondence he's received, which of course he cannot share, has been overwhelmingly positive. Indeed.

I'm always so delighted that when someone says something stupid, and people say that it's stupid, there's precisely this response somewhere in the comments. It's just so (chef's ki…

Hah! OK, sure.

I am currently at an organisation where Splunk is a bottleneck.

Only at trivial request volume. It’s easy to overwhelm any logging system without discipline.

Log after is SOP in any reasonably large architecture. Too much logging is a problem you encounter very quickly with nontrivial traffic.

Logging is significantly cheaper than tracing to maintain in a usable state.

You only emit a single log event (line) per request. Problem solved.

Yes, it’s useful, but that occasional usefulness is substantially outweighed by it’s perpetual cost.

Nope, this produces unmanageable log volume.

When I read MVC I guess I take it pretty literally, in that you would have packages named model/s, view/s, and controller/s. That's what I'm speaking to. Of course, abstractly, man…

You continue to assert that error handling adds noise to a block of code. This is an opinion, that's fine, but it's not an objective truth. In many many domains -- in fact the doma…

That is not at all what those links indicate.