Twitter | Search | |
✕✕✕✕✕
The official Twitter account of Dwayne 'The Rock' Johnson
8,413
Tweets
254
Following
6,540
Followers
Tweets
✕✕✕✕✕ 16h
Replying to @kwuchu
I've fought a long time trying to generalize/simplify Prometheus (and other whitebox instrumentation client libs) in Go kit, with mixed success. This looks something like the Provider abstraction I was trying to get here: - -
Reply Retweet Like
✕✕✕✕✕ 16h
Replying to @kwuchu
The point of summaries (versus histograms) is that you don't need to declare buckets, so I'm quite confused why there's any bucketing going on at all
Reply Retweet Like
✕✕✕✕✕ 17h
Replying to @kwuchu
Not clear to me why this type exists. Why not have users create and invoke their own metrics directly? (I'm sure there's a reason, just not clear.)
Reply Retweet Like
✕✕✕✕✕ 17h
Replying to @kwuchu
{Counter,Gauge,Histogram} is pretty compact
Reply Retweet Like
✕✕✕✕✕ Sep 21
It strikes me that separating transport from pure business logic in a Domain Driven Design inspired {Clean, Hexagonal, Onion} Architecture is symmetric with the Functional Core Imperative Shell model
Reply Retweet Like
✕✕✕✕✕ Sep 21
Replying to @davidcrawshaw
Tracks with US CPI in some way
Reply Retweet Like
✕✕✕✕✕ Sep 21
"Between 1960 and 2007, the share of disposable personal income spent on total food by Americans, on average, fell [in half] from 17.5 to 9.6 percent."
Reply Retweet Like
✕✕✕✕✕ Sep 20
Had what looks like a short outage in Hayes Valley HV44, can you confirm or is it my equipment?
Reply Retweet Like
✕✕✕✕✕ Sep 20
Replying to @supershabam
Monkeybrains my dude
Reply Retweet Like
✕✕✕✕✕ Sep 20
Do you have advanced monitoring use cases at your org? Novel techniques for observability at scale? CFP closes soon, I'd love to hear from you :)
Reply Retweet Like
✕✕✕✕✕ Sep 20
Replying to @peterbourgon
Repeal the Second Amendment
Reply Retweet Like
✕✕✕✕✕ Sep 19
Replying to @davidcrawshaw
With the caveat that I discount the cost of writing consumer contract interfaces to ~zero, I don't see any advantage to a custom RoundTripper. It's both more confusing than an interface (more cognitive load) and less flexible.
Reply Retweet Like
✕✕✕✕✕ Sep 19
Replying to @davidcrawshaw
If a component needs a dependency to do its work, I've found that modeling it as an interface (defined with the component) is the best default choice. It makes the contractual relationship clear, aiding comprehension, and the testing strategy is self-evident.
Reply Retweet Like
✕✕✕✕✕ Sep 19
Replying to @davidcrawshaw
type Doer interface { Do(*http.Request) (*http.Response, error) }
Reply Retweet Like
✕✕✕✕✕ Sep 18
Replying to @peterbourgon
· ulids
Reply Retweet Like
✕✕✕✕✕ Sep 18
Replying to @copyconstruct
Metrics instrumentation is fine, because you don't need comprehensive coverage to get value. Tracing is different: a single team needs to own the deliverable for the whole org, IME impossible without (a) monorepo, and/or (b) universally used lib/framework (to patch).
Reply Retweet Like
✕✕✕✕✕ Sep 18
thankful for · times new roman · uuids · shasum -a 256
Reply Retweet Like
✕✕✕✕✕ Sep 18
Replying to @NatashaMitchko
i clicked on your script but it didnt work please advise
Reply Retweet Like
✕✕✕✕✕ Sep 18
Replying to @eloycoto
Sure, I think it makes a lot of sense to have delivery routes open e.g. 10AM-4PM weekdays — with permits and strict speed limits
Reply Retweet Like
✕✕✕✕✕ Sep 18
Replying to @peterbourgon
No Cars Zone, phase 1
Reply Retweet Like