Jeff McAffer

Long time open source type, now at GitHub doing open source stuff. Father, husband, race car builder/driver, sailor, and apparently, traveller.

[Jeff McAffer @jeffmcaffer]

Long weekend project phase 1's a go! Dumpster ordered. 10 yards of gravel ordered. 5 pallets of wall blocks. ordered. Bobcat ordered.

[Jeff McAffer @jeffmcaffer]

Was really interesting presenting at #DOES20 London. Pre-recorded in my garage in Seattle, up at 0530 to answer questions live on slack from folks in, well, wherever they were.

[Enterprise Tech Leadership Summit @ITRevSummit]

Taking the stage on Track 2, @jeffmcaffer of @Github!

#DOES20

[Jeff McAffer @jeffmcaffer]

Proof: necessity is the mother of invention.

[Jeff McAffer @jeffmcaffer]

@amandaksilver Flat earth

[Jeff McAffer @jeffmcaffer]

@timheuer @andreychukna @jthake @EricJensenTV With you @timheuer.

[Jeff McAffer @jeffmcaffer]

@iamwillbar @github Codespaces FTW! I think there's huge potential there for an easy "get started" flow that gives you a fully configured dev environment. No fuss no muss.

[Jeff McAffer @jeffmcaffer]

@unixterminal I changed jobs and founded the office in April 2015.

[Jeff McAffer @jeffmcaffer]

@MeganRisdal Smelltalk

[Jeff McAffer @jeffmcaffer]

@MeganRisdal C

[Jeff McAffer @jeffmcaffer]

@jaketapper Rash

[Jeff McAffer @jeffmcaffer]

Hmm. 4 of us on a call. 100% of us named "Jeff". #lowdiversity

[Jeff McAffer @jeffmcaffer]

@zpao I too am in the market for a new provider. @comcast techs have been here 3 times and the problem still isn't fixed with no indication that it will be. Let me know what you find/do.

[Jeff McAffer @jeffmcaffer]

@sonatypeDev @_JamesWard Funny that. Some of my biggest challenges are around YAML and JSON. If you're using predefined structs then I'd say it's on par with other systems. User-defined content puts you in reflect hell.

[Jeff McAffer @jeffmcaffer]

@irbull Writing your own takes time. Doing it repeatedly leads to making your own `utils` library that you reuse but have to maintain. Not sure how that's better and certainly is not "enabling me to do more with less code". The base class libraries should have these table stakes.

[Jeff McAffer @jeffmcaffer]

I've been messing about with @golang recently. Lots of great stuff but the term "rocks and sticks" keeps coming to mind. Could totally be me but, lots of basic things appear to be missing. I keep hearing "the idiomatic way is to <explanation boiling down to write it yourself>"

[Jeff McAffer @jeffmcaffer]

@sonatypeDev @_JamesWard Agreed on the there by default but we'll have to disagree on the "less code" part. I have written much more basic "table stakes" code and repetitive error handling in my little bit of Go than ever before. Of course, I could be doing it wrong... I suppose it's all relative.

[Jeff McAffer @jeffmcaffer]

I'm keeping an open mind and am only a couple weeks in so who knows where I'll end up. Need to see more of the system come together... What's your experience been like?

[Jeff McAffer @jeffmcaffer]

And I don't quite buy the perf argument. Of course, I agree that map[<your_type>]struct{}{} is faster than map[interface{}]bool but we're talking nanoseconds here. Important in some cases but in the face of doing network calls that take 100s of ms, not so much.