Five for Friday – July 7, 2023

Last week, I scheduled this post, and somehow in doing that I (debatable) made it a private post for subscribers only. That, of course, means that I’m going to schedule this post for 10 minutes from now to see what happens under careful observation.

  • I scheduled the post last week, because I was walking 70 miles of the Pacific Crest Trail. I first walked on the PCT nearly 50 years ago, and have been a bit infatuated with it (off and on) ever since. Someday, I’d like to walk all 2650 miles of it.
  • Open Org recently released their Employee Handbook Template – and it’s kind of cool – or at least worth checking out.
  • I’m currently balancing my DM and Group Chat time between Teams and Slack (weird, but true). I’m pretty sure I don’t want this, but in my haphazard searching to try and see how other folks balance this, I found that some teams just give up and use a tool like Mio Dispatch to make them both feel like one tool.
    I’ll keep looking for a better answer.
  • I think at a lot of companies, it takes too long to get new engineers up to speed. This article on onboarding new engineers hit’s the main points (and with great citations to back up their claims).
  • Finally, some food for thought. This post asks, Are bugs and slow delivery ok? I think the question is valid – and while I agree that for some products, slow and buggy may be ok, but I disagree that it’s 95%…but I sort of hate that the author is sort of right.
    I need to ponder this some more…

That’s all for this week – apologies again for the posting mishap last week, I’ll try to keep my shit together.

Similar Posts

  • The Test Test

    I am always frustrated and somewhat sad when I hear testers whine or complain that they are not treated fairly; or that they are not respected; or that their development peers look down on them. I’ve been sitting on this post for many months wondering if I should post it or not when this thread…

  • Five for Friday – March 11, 2022

    Another week gone, and I’m still frustrated with the world around me. Trying to stay positive, but…sheesh. Here’s some stuff worth reading. I’m cheating, but this is worth it. Here is a post highligting seven must-reads for women in tech. I don’t often highlight AB Testing podcasts here, but we had Anne-Marie Charrett on a…

  • Let it happen

    I come across this frequently enough that I’m sure I’ve blogged about it before, but context dictates that I do it again. The story I hear goes pretty much like this: My team really needs to improve X, but nobody is taking responsibility for it. The fix is obvious – we need our exec /…

  • Why bugs don’t get fixed

    I’ve run into more and more people lately who are astounded that software ships with known bugs. I’m frightened that many of these people are software testers and should know better. First, read this “old” (but good) article from Eric Sink. I doubt I have much to add, but I’ll try. Many bugs aren’t worth…

  • Who are you?

    I’ve been thinking about how professional testers describe themselves. We have high level labels like Tester, SDET, or Quality Engineer, but beyond those (mostly meaningless) titles, many of us have our own personal missions or visions – the words we want people to associate with us. For example, my twitter bio is, “Long time software…

One Comment

  1. Yes, all posts (also historical) became private.

    I thought you did it to protest the Twitter debacle 😀

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.