ecoffey

7 ms·

1.
by ecoffey 5mo ago
Would love to hear more, since I largely used SLOs on backend services (which in turn called other services that also had their own SLOs). As far as timespans for the error budget consumption, I’ve seen 1 hour -> 1 day -> 1 week. The
2.
by ecoffey 5mo ago
I certainly agree in spirit that the alerts are important, and should be actionable. But I wouldn't start at just "looking at the service" and then trying to define the first set of alerts. Instead I would move up a level and
3.
The Complexity of Simplicity [video](youtube.com)
4 points by ecoffey 10mo ago|1 comments
4.
by ecoffey 1y ago
Interesting! Reading the headline before the article, my brain immediately thought of "jitter". I wonder if you could extend the `In-process synchronization` example so that when `CompleteableFuture.supplyAsync()` thunk first does
5.
by ecoffey 1y ago
Northguard doesn’t look like it’s been open sourced? I’d be curious to know how it compares to Apache Pulsar [0]. I feel like I see some similarities reading the LI blog post. 0: https://pulsar.apache.org/
6.
by ecoffey 1y ago
That is tough, I’m sorry for your loss.
7.
by ecoffey 1y ago
Even loose coupling is still coupling. For the things that have to be coupled having the code organized in the same place, being able to easily read the source for “the other side”, make a change and verify that dependees test still pass, e
8.
by ecoffey 1y ago
In my experience microservices are easier to manage and understand when organized in a monorepo.
9.
by ecoffey 1y ago
Monorepo is one of few things I’ve drunk the koolaid on. I joke that the only thing worse than being in a monorepo, is not being in one.
10.
by ecoffey 1y ago
> perfect ASMR for nerds. Haha yeah I like to have this on it the background when I’m doing other things.
11.
by ecoffey 1y ago
Bartosz links to it in the Further Reading section, but wanted to highlight the Wristwatch Revival YouTube channel[0] as well. Really great content and very understandable after reading the article! 0: https://www.youtube.com&#x2
12.
by ecoffey 1y ago
https://en.m.wikipedia.org/wiki/Rule_of_least_power
13.
by ecoffey 2y ago
> LSP optimizes writing the code. I would actually phrase that as “LSP optimizes for understanding” (which is of course important for writing code). For example, when doing code reviews I routinely pull the branch down and look at the di
14.
by ecoffey 3y ago
Makes me think of this project: https://www.vesta.earth/
15.
by ecoffey 3y ago
Trying to see from specs and such if the mesh supports ethernet backhaul vs wifi radio like the google wifi does.
16.
by ecoffey 3y ago
There is a great book called The Emerald Mile that touches on some of this history, and other Grand Canyon history, using the story of the fastest traversal as the narrative device. Highly recommend. https://www.goodreads.com&#x2
17.
by ecoffey 7y ago
re: implicits... https://twitter.com/ecoffey/status/1179198362924404736?s=21
18.
by ecoffey 7y ago
last year we got solar installed (8kW system + 10kWh battery): https://twitter.com/ecoffey/status/1212399375986487296 replaced a minivan with a leaf: https://twitter.com/ecoffey/status/10
19.
by ecoffey 9y ago
You can shift click a range, or command click a disjoint set, of tabs in chrome. And then with one mouse drag move all of them to an existing window or create a new one. It's a feature that I wish safari had (although I have tried tab
20.
by ecoffey 11y ago
You can still have the question. But my answer is a random 32 character string of alphanumerics :)
21.
by ecoffey 11y ago
A linked list of levels reminds me of Binomial Heaps
22.
by ecoffey 11y ago
Reading that man page sounds like the way to go about it is start with `tame(0)` as early as possible in the program and see how it fails. then iterate pushing `tame()` down and expanding the flags until the program functions.
23.
by ecoffey 11y ago
I don't know :) titles are inherently political. They don't exist in some platonic vacuum. So some part of the progression is about broadcasting the status change to the larger organization. Beyond that I think the ladder becomes
24.
by ecoffey 11y ago
While Management usually the only thing equated with "soft" (hate that word beeteedubs) skills, moving up the IC ladder also requires good inter-personal skills. Above senior you are allowed and expected to go "heads down&quo
25.
How to Avoid Burnout(medium.com)
4 points by ecoffey 11y ago|0 comments
26.
by ecoffey 11y ago
Great point. Different scale needs different things for sure. Even at the scale that I've found this successful in you still have to consider that backward/forward compatibility, albeit at a much coarser grain.
27.
by ecoffey 11y ago
> because each component was released and versioned separately. For SOA a mono-repo with synchronized releases is a huge help. In one commit you can refactor a shared module and update all apps that depend on it. And you know when you de
28.
by ecoffey 11y ago
> That's assuming that things haven't become deeply coupled within the "call stack". Yep; Monolith or SOA you still have to write SOLID code :) > Separating things across a socket often forces a separation of conce
29.
by ecoffey 11y ago
Yes, but discovering and refactoring to those clear APIs is easier across the in-process call stack. Have to delay the "hoist and introduce a socket" until you're /reasonably/ confident you have the API more-or-less
30.
by ecoffey 11y ago
For me the big takeaway is this: Refactoring across the call stack is orders of magnitude easier than refactoring across a socket. Sacrificial or not, you can still write the Monolith as "Service Oriented", just that boundary is t

More ›