@jmoiron @chimeracoder What do you expect it is a 1200 year old vending machine
jmoiron plays the blues
@jmoiron RT @dgryski: DDSketch: A fast and fully-mergeable quantile sketch with relative-error guarantees
We present the first fully-mergeable, rel…
@jmoiron RT @PyLadiesGhana: Meet Stephanie Sher, experienced in product and growth and has consulted for various companies in the robotics and machi…
@jmoiron for me not for you https://t.co/akk0Bhq1Nr
@jmoiron @chimeracoder It's cliche, but imho pasteis de belem is worth the hype, and so is cervejaria ramiro. They'll be full of tourists, but so will the rest of Lisbon.
@jmoiron @chimeracoder @jxxf I'll be there that week :)
@jmoiron RT @joshuawongcf: HK Riot Police fired bullet and headshot a young lady. I am not sure whether her right eye will turn blind or not but it…
@jmoiron @dgryski @DrEugeniaCheng "Acknowledgements:
This study was funded by Pizza Express"
@jmoiron @davecheney oh yeah on call at a monitoring company is probably easy
@jmoiron @UkiahSmith @NateTheFinch @elithrar https://t.co/aqpxQ0lxnJ
@jmoiron @UkiahSmith @elithrar @NateTheFinch For readability, you'd prefer {required, optional} order so you can always scan without context. {o, r, o} means your brain has to figure out that first (). Receiver could have gone after the func name, but it would have been less readable.
@jmoiron @petar_donchev Methods are restricted from taking additional type parameters https://t.co/BNsB4PHNz5
@jmoiron func name()() () { } is just too many ()'s in a row
@jmoiron @xaprb The Spartan "If."
@jmoiron If you're new to Go and using sql, https://t.co/bZygzEN9d1 is an excellent dive into the nuances and behaviours of database/sql. Just the "Common Pitfalls" section will likely save you hours of frustration.
@jmoiron RT @davidcrawshaw: @_rsc @peterbourgon @goinggodotnet @davecheney @markbates @NataliePis There's lots of feedback you won't get until you s…
@jmoiron This document, prepared in 1979, contains within it the seed for nearly every "modern" software practice: encapsulation, a separation of unit, integration and contract testing, code review, automated deployment, cost estimation strategies, software observability.
@jmoiron "as individuals and managers became more experienced, schedule estimations became more and more reliable. No panacea was ever discovered except that of better familiarity with the tasks to be accomplished."
@jmoiron "even though a particular design already may have been implemented successfully somewhere, a team with little background related to that design should recognize that their activities will contain a large component of uncertainty due to the research they must do [to learn it]"
@jmoiron "It is now obvious that the Multics development would have been much easier if a simpler language had been chosen for implementation. [..] However, having been successfully developed, PL/I is now one to the strengths of the system." -- https://t.co/wUgtiFXwXH
@jmoiron "The language chosen was PL/I partly because of the richness of its constructs and partly because of the enthusiasm of those planning to implement the compiler. The [...] language implementation became an inadvertent research project."
@jmoiron RT @ladykan: Diversity Initiative. #awssummitnyc #diversityinitiative #wit https://t.co/P7RWBKPxtS
@jmoiron @dayorbyte @copyconstruct @mattklein123 If try makes code harder to read, then your ability to abstain doesn't prevent it from being potentially a bad change. I don't understand this argument; surely we should avoid a situation where everyone has non-overlapping approved subsets...
@jmoiron @carmatrocity @davecheney People need to adopt the moiron score for software dependency cost modelling and also to learn how to pronounce my name.