Five for Friday – May 17, 2019

Here we go again…

  • The Heisenbug Conference call for papers is open. These folks treat speakers like rock stars, and I highly recommend the conference.
  • Speaking of conferences, it’s almost time for the Online Test Conference. The lineup is incredible (and I’d say that even if Brent Jensen and I weren’t speaking), it’s free, and you can attend from home.
  • Here’s a secret – I’m a fan of almost everything Al Shalloway writes. This article is no exception. The Five Whys of Lean as an Answer to the “But” of Scrum (note – he recently republished this – it was originally written in 2009).
  • This week I found the Jira Python library – which, for better or for worse, is something I expect I’ll use to some extent (the library is great; it’s Jira that I worry about).
  • If you’re like me, when you hear someone talk about “cultural fit”, you either cringe or stop and ask, “wtf do you mean by cultural fit?”. This article on What’s the Difference Between Cultural Fit and Cultural Impact? cleared up a lot of my worry and confusion.

Similar Posts

  • Network and influence

    I gave a short talk to an internal MS community this week. The topic of the day was “influence”, and I thought it was appropriate to talk about the value of building (and maintaining!) an informal network – and the impact of that network on influence. The advice to have an informal network isn’t new…

  • Star Canada

    It’s been a long time since I have had to talk so much, but I had a great time, and met some great people. As promised (to many people in my talks), here are the links to my presentations. My Tutorial My Keynote My Track Session

  • A week of bad code

    Earlier this month, I spent a week in beautiful Copenhagen at what’s called a R&D Training week. The goal is that every new Unity engineer spends a week at the Copenhagen office, learning about the systems we use, and about engineering at Unity. Granted, since I’m on the services side, a big chunk of the…

  • ET and Me

    I’m a big fan of exploratory testing. I’ve used the approach long before I knew what it was called and think it’s the core of good testing. it’s so ingrained in the general approaches I’ve used in my career that I often don’t differentiate between exploratory testing and plain-old-testing (I’ve gone as far to say…

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.