Five for Friday – March 29, 2024

Happy Friday everyone – read on for some potential interest…

  • First, an announcement. Wednesday, April 3 is the Tenth Anniversary of the AB Testing Podcast – and it’s also our 200th episode. We’re going to record it live at 6:00pm PDT – it’s basically a podcast / webinar.
    If you want to take part, join our Slack group and you’ll find a gcal link in the #general channel – or if you don’t do slack, I’ll plan to post details on linkedin beginning on Monday.
  • I’m a little late in posting today, because I took the day off for first hike of the spring. The Wallace Lake Loop was perfect – with a few side trip, it was a fun ten miles.
  • As a current remote worker – and an advocate, I found a lot of interesting points in this 2024 State of Remote Work.
  • This article is targeted at Quality Engineers, but everyone should read it – RAG for Quality Engineers
  • And…I stumbled this article from Ryan Peterman that was clear, accurate, and valuable The Tech Lead’s Playbook.

That’s all for this week, and that’s all for March 2024. Hope to see some of you (virtually) Wednesday night.

Similar Posts

  • What Happened?

    As I approach the half-century mark of existence, I’ve been reflecting on how I’ve ended up where I am…so excuse me while I ramble out loud. Seriously, how did a music major end up as a high level software engineer at a company like Microsoft? I have interviewed hundreds of people for Microsoft, who, on…

  • Five for Friday – November 8, 2019

    From Sweden this week – I’m attending and speaking at the Oredev conference this week. In fact, I had a few interesting conversations this week about the convergence of DevOps and quality. But…is DevOps a role or a culture? This podcast from CodingBlocks discusses just that. A few months old, but I enjoyed this article…

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

  • Testing for Brown M&Ms

    One thing I’ve learned in my testing career is that where there are bugs, there are more bugs. Some of my colleague Nachi’s research shows that components with a high number of pre-release bugs has a corresponding share of the post-release bugs. The heuristic works well on a smaller scale too – if I find…

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.