@jmoiron@buckwilson btw if you like jazz a lot and don't listen to bossa nova then you're missing out on a small but wonderful world of excellence
@jmoiron@buckwilson yea or charlie parker, coltrane, thelonious monk.. I suspect they reach technical heights but are just not celebrated
@jmoiron@buckwilson super into that too, had a jazz band at my wedding! but any old list of standards generally does it for me :\
@jmoiron@buckwilson np, this covers the chill/rainy/whisky side, if you want funky/dancy stuff check out genres "future funk" / "french house"
@jmoiron@buckwilson I also really like visioneers dirty old hip hop https://t.co/0WJeXr9OBC
@jmoiron@buckwilson ya i don't make this shit up, jazz-hop is neo enough for me.. for a particular artist i quite like https://t.co/epNZVWthh5
@jmoiron@buckwilson otherwise if you like instrumentals ("neo jazz-hop") check out @arotomusic's mixes https://t.co/ERufdxPBlx
@jmoiron@buckwilson marcus D for sure, if you liked eg. metaphorical music https://t.co/Znh3w5MdOl
@jmoironautocomplete is a dumb feature for "pros" but look at github and tell me we won't use better access to emoji
@jmoiron@davecheney that's pretty vague.. are you saying that replacing a keyboard that's fine with one that is bad is like.. power steering?
@jmoiron@calebspare on the plus side if you use a mac this short cut won't be available much longer
@jmoironUsing a butterfly keyboard is the typing equivalent of thinking you've got one more stair when you haven't
@jmoiron@darron usually at least _some_ are right though; oh yeah, and butterfly keys :(
@jmoironEvery rumored change to the macbook/pro line makes them worse: touchscreen instead of fn buttons, no magsafe, no sd slot
@jmoironabstraction is like optimisation, it's always premature, and by the time it isn't, everyone knows
@jmoiron@rakyll getting diagnosed with a serious AI condition 2 years ago was a big blow, but the 7 years of not knowing was worse.. best of luck
@jmoiron@francesc IIRC you get two choices, good beer or free beer
@jmoiron@bryanl I stand by my original answer then :D
@jmoiron@bryanl whoops, my brain converted that to "value receiver" but now I realize I read it wrong and don't know :)
@jmoiron@bryanl yes, mostly for bad reasons (eg. avoid heap, gaps in escape analysis) + occasionally a way to get a kind of immutability
@jmoiron@rob_pike looking at it from pass-ref-by-value style (py,ruby,etc) perspective, having to add "*" to get the "right" behaviour may feel odd
@jmoironI've never thought about it from this angle, but `foo.Stuff()` operating on a copy of `foo` is definitely not intuitive. https://t.co/W2HwUjkhHV
@jmoironRT @chimeracoder: We wrote an article about the project I spend my days working on! https://t.co/k0liN8FvzU @stripe #golang
@jmoiron@PreetamJinka an EBS outage caused me 16h of downtime once
@jmoiron@amontalenti if you don't know how it's operated, how can you know how to write it?