jmoiron plays the blues

6a1b5b08 to gotk3 Merge remote-tracking branch 'upstream/master'

@jmoiron @PreetamJinka @davecheney @xaprb sure, but which do you think is more often undercooked? it's the same as my problem with DRY

@jmoiron @davecheney @xaprb I suspect people who log the world are underutilizing metrics which are much better for aggregate behaviour vis

@jmoiron hopefully someday google maps will understand that despite being only 1km away, Astoria takes ages to get to from UES

@jmoiron either all this tinnitus spam I get is oddly specific or I'm missing out on some newfangled euphamism

@jmoiron @jedthian @theglobehk all is good in the rugby universe https://t.co/XnPiXHA4Xr

@jmoiron @jedthian @theglobehk @hongkonghooters @TheCannyManHK thanks Jedi!

@jmoiron @jedthian where's the best place to catch the rugby championship matches in 852 today?

@jmoiron I had always just assumed "containerd" was a demonym

@jmoiron need to add this emoji to unicode, it means "system wide failure at catastrophic scale" https://t.co/1hDwnlDIBO

@jmoiron @dgryski I've used redeo in production for over a year and had no issues with speed or reliability.

@jmoiron @peterbourgon this survey felt like it was asking "how much like npm/pip/gem should we make dep management" and my answer is "not very"

@jmoiron @mkrupnic that might have been one of the courses at my wedding

@jmoiron @PreetamJinka "lots of redirtying of already dirtied pages" is TSDB 101 but sure why not postgres

@jmoiron android auto-completed "saag paneer" -> "saag panzer" and now I want a spinach tank

@jmoiron sqlx passed 2000 fake internet points, thanks internet! https://t.co/n3ZbALDEbr

@jmoiron @benbjohnson I felt this way when I told everyone to stop using ioutil.ReadAll, feelsgood.

@jmoiron Mach go go gopher https://t.co/WezV67Ixfg

@jmoiron RT @jeffbarr: New from @datadoghq - #AWS Lambda Integration / support for Serverless Arch - https://t.co/qkgoNrBQzq https://t.co/6UJ5dyMIkA

@jmoiron @sdboyer but you're right, the edge weight is a measure of coupling, and existence may be too rough an estimate.

@jmoiron @sdboyer there are _definitely_ other heuristics to be had here, eg. don't want to pull in lib upon lib upon lib for 1 func

@jmoiron @sdboyer Yeah I think the edge existing implies a coupling, how tight it is would be how many different exported things it uses..

@jmoiron @sdboyer eg, you use a big framework, but a standalone lib can be simpler in the long run than an add-on, because no relationship to sync

@jmoiron @sdboyer also 2 deltas might be useful, one for what it adds new and one for the complexity it adds to your existing graph

@jmoiron @sdboyer delta is more useful I think, esp if you consider the case of replacing one lib with another