@jmoiron @davecheney @dgryski and yet when we dig deep we see modern computing kept afloat by a series of caches, delicately balanced https://t.co/uBwBRIFKcS
jmoiron plays the blues
@jmoiron @clofresh ambitious post id keyspace
@jmoiron @breerly @davecheney I don't think "under no circumstances are tracebacks acceptable", methods to prevent them often end up over-eating errors. Tracebacks are just not a replacement for error handling. This is poor: https://t.co/rtyy6XfMvZ
@jmoiron Tracebacks are not error messages and they do not belong in error messages. Do not show tracebacks to your users, even if your users are programmers.
@jmoiron every unhappy on-call rotation is unhappy in its own way
@jmoiron @copyconstruct Survivor bias. Companies who obsess over automation sacrifice things more vital to their revenue driving areas.
@jmoiron @francesc @sourcedtech reminds me of an airbnb I stayed at in paris with a ... peculiar bathroom https://t.co/VVg0UO03UC
@jmoiron the nice thing about eventual consistency is that it can be implemented on top of any datastore
@jmoiron @chimeracoder I'm pretty sure at some point in the past I printed a document and then scanned it so I could get it in PDF
@jmoiron @copyconstruct The etiquette is: if you think you can make it, feel free to cross + caveat emptor. If you can definitely make it, you must cross. I think the grid encourages this as it makes for a lot of intersections.
@jmoiron @copyconstruct @Medium yeah, sounds great!
@jmoiron @copyconstruct @Medium 2nd paragraph describes my experience with twitter, ironically
@jmoiron @RayS ditto
@jmoiron Imagine a world where it is 2017 but this type of replication didn't already exist. Who would be arguing for it to be called master/slave? Probably just assholes. https://t.co/go9a29RANI
@jmoiron Think about code coverage tools like you would infrastructure observability tools. They provide very specific information, an incomplete and sometimes misleading version of reality, just like every other observability tool, but even a little insight is way better than none.
@jmoiron new years resolution: fail any change request in code review that features a new type starting with the word "Abstract"
jmoiron/dotfiles 809b373 i like materialtheme and i dont like material so this messes up tab completion for no benefit
@jmoiron @dgryski twitter's weird concept of a "timeline" made it seem like a recruiter sent you that tired rob pike quote :D
@jmoiron RT @ozbob: This graph is what happens when engineers, across disciplines, work together and solve problems.
Also, big thanks to @VividCort…
@jmoiron how to fail code review https://t.co/8yngAUQnAc
@jmoiron This quote is about water:
“It has a vaguely mild sweetness, a nice smooth mouth feel, nothing that overwhelms the flavor profile,” San Francisco grocery store manager Kevin Freeman told the Times.
https://t.co/LyTspuL5R5
@jmoiron @bryanl I yak shaved this stuff long ago and came up with https://t.co/WeoEmIdmkE + https://t.co/5AQVqygqLd which work the same on osx and linux (bound to cmd-$ in both) and produce https://t.co/LWz2zfH3qc
@jmoiron @jtruk Agreed 100%. I also believe that keeping around those vestigal mechanisms of cleverness continues to have its impact on simple+accessible code because they often cannot be ignored.
@jmoiron @ircmaxell If you build a graph of other code you have to consult to understand the line you're looking at, it's the traversal of that graph. Eg. overridable attribute access adds cognitive load to all attr access. To cope we ignore the load or avoid the features but they still...
@jmoiron The less context you need to be able to read source code, the easier it is to understand. The more understandable it is, the more reliable it will be. Powerful language features like metaclasses, properties, constructors/destructors often add brevity at the cost of distance.