Five for Friday – September 27, 2019

Happy Friday everyone – here’s some stuff to dump from my head to yours.

  • As I type this, I’m listening to Dead Man’s Pop – the remixed version of the Replacement’s Don’t Tell a Soul. I was/am a big Replacement’s fan, and these recordings are all kinds of excellent.
  • This article on how Boeing’s Managerial Revolution Created the 737 Max Disaster is fascinating, with far too many parallels to software disasters than this frequent traveler is comfortable with.
  • I liked this infographic on Agile Team Dynamics.
  • Not sure why HTTP/2 can be problematic, or how TCP and UDP fit intot he equation. And what’s this about HTTP/3 – here’s a fantastic summary of HTTP 1, 2, and 3 in a Nutshell
  • Another profoundly true quote from Drift Into Failure
    Murphy’s law is wrong: everything that can go wrong usually goes right, and then we draw the wrong conclusion.

Similar Posts

  • LOL – UR AUTOMASHUN SUCKZ!

    There’s a pretty good presentation from the folks at Electric Cloud making the rounds on “why your automation isn’t” (and other variations on that title). The premise is, that testers spend too much time babysitting (supposedly) automated tests, and that testers end up doing a lot of manual work in order to keep their automation…

  • 2012 Recap

    As 2012 comes to a close, I thought I’d recap the year. I think this little exercise is mostly for me, but I suppose new blog readers (or people with too much free time) may find some points of interest. Some more from the non-Microsoft front follows. My most popular blog posts from the last…

  • Just Fix It (mostly)

    Chris McMahon’s latest post (Just Fix It) proposes that as far as bug tracking goes, the best course of action is to skip the “tracking” part of the workflow and “Just Fix It.” I’m a huge fan of this approach and think that for the most part, tracking a large number of bugs in a…

  • Failure to Launch

    In my role on Teams, I was “in charge” of quality – which eventually turned into everything from the moment code was checked in until it was deployed to our end-users. At one point during development, we had a fully usable product with no known blocking issues. We were missing key features, performance was slow…

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.