I can’t remember whether it was during a conversation, or a meeting, or somewhere else that I heard these words this week, but wherever and for whatever reason, they’ve had a powerful impact in a [probably] completely unintended way.
Refactor as soon as you notice you need to, otherwise you’ll probably forget later.
Sadly I don’t get as much opportunity to focus on code as I’d like. So I’m not going to apply that thinking to code. What I am going to try and do is write a quick blog as soon as something captures my attention or interest. Since if I don’t, I’ll probably forget or not get around to it later.
What that means for you dear reader, is hopefully more blog posts akin to Knowing Versus Doing, published earlier this week. Kind of random, in that they won’t necessarily be related to product or testing – but hopefully interesting still. And with any luck, over time some trends or themes will emerge that I can explore in more detail.
- I very much enjoyed listening to Matthew Parker (AKA @TestingTackled) at the #MidsTest meetup last Wednesday, tweeting as much here. Communication skills has been a favourite topic of mine in the past, so I’ll take this opportunity to dredge up a few of my own thoughts on the subject, from the archives 🙂
- After the speaking bits were over, I enjoyed a conversation with Matthew, Robert and others about the joys of contracting and bringing an entrepreneurial mindset to the table. Again, areas that I feel quite passionate about – but instead of bigging up my own writings on the same, I’ve seen a few of Mark Crowthers pieces around contracting recently and can heartily recommend you go check them out, e.g here: Contracting – Entrepreneurship
- If you’re a regular, you’ll know that I talk about the books I’m reading, have read or plan on reading in the future a lot! ReadIng is a big part of my approach to self and career development, and life generally. So, I enjoyed reading this piece from Michael Simmons, and thought some of the tips were genuinely insightful. Particular takeaways for me were the ideas of treating books as experiments (though, I already do this I hadn’t framed it in quite this way before) and treating unfinished or I started books as a reminder of what I don’t know yet.
- I needed to brush up on my approach to one-to-one’s recently and found this article quite helpful as a primer for openness and potential awkwardness: The Art of the Awkward 1:1
- Sign-up for our Winning at Reporting webinar this Thursday if you have some time. Lead TestRail support engineer Marco Garcia and myself will be talking about all things reporting and trying to help folk get the best out of our built in functionality.