When my daughter started to learn how to walk, we immediately started buying corner protectors and had multiple scans of our apartment to see if there were any dangers lurking that we had to remove or cover up. We wanted to make it safe for her (to fail).
When it comes to software development, I think it’s also important to make it safe for people to fail.
People make mistakes.
It happens to everyone – and in my opinion, it’s not a bad thing.
Continue reading “Why it’s important that it’s safe to fail”
Outside of work I consider myself a minimalist.
The definition of minimalism I most closely align with is
Minimalism is a tool to rid yourself of life’s excess in favor of focusing on what’s important—so you can find happiness, fulfillment, and freedomhttps://www.theminimalists.com/minimalism/
For the past few years I’ve done my best to not over-consume and to donate or sell things when they are no longer providing value to me.
Continue reading “Minimalism and test documentation”
One of the things that frustrates me the most about baking is the fact I don’t tend to find out whether or not my baking was a success until the very end when I slice into that cake or bite into that cookie.
Even attempts to check out how things are going don’t guarantee good results – you can look in the oven to see if the cookies look like they are the right colour before you take them out, or you can use a fork to check the doneness of a cake or muffin, but these checks are only looking for one aspect of quality – doneness.
Continue reading “Waterfall, Baking and Slow Feedback”
I’ve had many first days in a team since I started my testing career almost nine years ago. But it’s always been daunting and there’s a lot to take in.
I’m often trying to gain my bearings and not necessarily looking to start testing on my very first day. (For getting started on a testing project, read this)
Continue reading “Bloggers Club: First day in a team”
I tend to be wary of giving unsolicited feedback in general, even with the best intentions, it doesn’t always go down well.
Let me give you an example: I used to work with a tester who wrote the bare minimum when it came to bugs. There was hardly ever any information on steps to reproduce, no information on OS version, screenshots sometimes were provided and actual result vs expected result were never there.
Continue reading “Feedback: Solicited vs Unsolicited”