Five for Friday – October 1, 2021

We made it through another week. Sort of. Between this, that, and some really gnarly other stuff, here are a few links I found that you may find interesting as well.

  • In teams I lead, I do as much as I can to ensure a culture of transparency, accountability, and psychological safety. As such, I’m always interested in articles and research like this, that discuss workplace toxicity
  • The PNSQC Conference Program is out. This has always been one of my favorite conferences for discussing Quality (and not just testing). It’s worth checking out.
  • I’ve been re-reading this article on self-service models for platform teams, and like a lot of what it has to say.
  • This article on teams as networks resonated a lot with me as well.
  • I’m probably behind a lot of you, but I just discovered ohmyzsh and it’s made my mac terminal a lot more fun.

That’s all 5 for this week – I’ll try it again in a week.

Similar Posts

  • Thoughts on PNSQC

    PNSQC is still going strong (although it may be over by the time I post this). Sadly, my North American test conference tour forced me to miss the second day of the conference in order to make it to Toronto in time for the QAI Testrek conference. My opinion of PNSQC is the same as…

  • In the Middle

    Should you automate everything, or nothing? Should you test everything, or nothing? How about leadership – should you dictate every detail of what your team should do, or give them no guidance at all. The answer for all of these questions – as you’d expect, is “somewhere in the middle”. In my experience, most people…

  • Five for Friday – February 15, 2019

    Another week, another random five things I found interesting. Feedspot.com lists AB Testing in their top 10 software testing podcasts. Although it has “Testing” in the name, my 2019 goal is to get AB Testing into more Agile or Software Development podcast lists. Joel Montvelisky, who is one of the three AB Testing listeners is…

  • 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…

  • The angryweasel guide to safe backups

    Warning – not software quality related, but perhaps even more important information follows. I am diligent about backups (and paranoid about losing files)…and frugal, so dumping my backup strategy here for those who may be like minded. First thing to be paranoid about is work in progress. If it’s code or text based, put it…

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.