sagichmal

5 ms·

1.
by sagichmal 1y ago
Yup. Somewhat formalized: https://peter.bourgon.org/blog/2018/08/22/observability-sign...
2.
by sagichmal 5y ago
This is definitely not true (shrug) Attrition has more than doubled and most engineering teams are critically understaffed.
3.
by sagichmal 5y ago
Most do, though, because there does tend to be a more correct position on this class of stuff.
4.
by sagichmal 5y ago
> A handful of people left They lost close to half of their engineering team, significant percentages of their operations teams, and many senior leaders.
5.
by sagichmal 5y ago
No, I don't know anyone at Basecamp.
6.
by sagichmal 5y ago
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.
7.
by sagichmal 5y ago
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 about things systemically tend to apply that perspective in a
8.
by sagichmal 5y ago
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-facing byte tends to generate something like ~10 DEBUG-level
9.
by sagichmal 5y ago
Yes. All of the "private" correspondence he's received, which of course he cannot share, has been overwhelmingly positive. Indeed.
10.
by sagichmal 5y ago
Hah! OK, sure.
11.
by sagichmal 5y ago
I am currently at an organisation where Splunk is a bottleneck.
12.
by sagichmal 5y ago
Only at trivial request volume. It’s easy to overwhelm any logging system without discipline.
13.
by sagichmal 5y ago
Log after is SOP in any reasonably large architecture. Too much logging is a problem you encounter very quickly with nontrivial traffic.
14.
by sagichmal 5y ago
Logging is significantly cheaper than tracing to maintain in a usable state.
15.
by sagichmal 5y ago
You only emit a single log event (line) per request. Problem solved.
16.
by sagichmal 5y ago
Yes, it’s useful, but that occasional usefulness is substantially outweighed by it’s perpetual cost.
17.
by sagichmal 5y ago
Nope, this produces unmanageable log volume.
18.
by sagichmal 5y ago
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, many programs tend to be structured in
19.
by sagichmal 5y ago
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 domains which Go targets -- error handling is equally
20.
by sagichmal 5y ago
That is not at all what those links indicate.
21.
by sagichmal 5y ago
Wow! No wonder you find this tedious. Your gateway struct hopefully looks something like type Fooer interface{ ... } type Barer interface{ ... } type gateway struct{ f Fooer; b Barer; ... } newGateway(f Fooer, b Barer, ...
22.
by sagichmal 5y ago
CRDTs and smart contracts are almost totally unrelated to each other.
23.
by sagichmal 5y ago
> Is there any theoretical groundwork happening on how CRDTs can preserve domain semantics? Effectively using CRDTs requires a fundamentally different model of state. Typical CRUD stuff simply doesn't work. If you're unwilling
24.
by sagichmal 5y ago
I don't understand why you would reply with this comment. If the question is "how do I do X?" and X isn't something that you should be doing, why is it not constructive to point that out?
25.
by sagichmal 5y ago
When something is unsound it is valuable to point it out. It prevents harm.
26.
by sagichmal 5y ago
I'm sorry if you've had bad experiences with this approach in the past, but it emphatically does not lead to low quality and/or meaningless tests. It's the essential foundation of well-abstracted and maintainable softwar
27.
by sagichmal 5y ago
This isn't in the relevant domain.
28.
by sagichmal 5y ago
"MVC" is not an idiomatic pattern in Go.
29.
by sagichmal 5y ago
Maintainable software projects are modeled as a dependency graph of components that encapsulate implementation details and depend on other components. func main foo, err := NewFoo() handle err bar, err := NewBa
30.
by sagichmal 5y ago
Because when the author writes or speaks about the project, they consistently demonstrate a fundamental lack of understanding of the domain. There is a reason that GunDB is never mentioned in literature or papers.

More ›