Book Review - "Dear Evil Tester"

Book Review: "Dear Evil Tester"


If you are a tester, if you are a developer, if you just like really funny shit, you should read this book! 

Dear Alan Richardson,

This book had me laughing at my desk and my coworkers wondering if I had gone around the bin. I was enchanted by the sarcasm and wit, but drawn to the practical advice you had in your answers given with the Evil Tester persona.

I have favorites that I go back to and read on really, really stressful days where I need a laugh. I also find myself in the essay section as well, reading some inspiring stuff. I think the essay which most inspired me was "Unconventional Influences". When I get bogged down in my own self-importance, I remember that in the grand scheme, it's all my own bullshit that is plaguing me. It's good to question things, but it's also good to be open to the answers you get from the questions. Your essay reminds me of this all the time. Influence can be a double-edged sword. Used for good, it can be an amazing tool. Used poorly, and you might cut off your own head in spite of yourself.

I also like the recommended reading section, though Alan, lets talk seriously. Let see some love for a couple of other books like: "Agile Testing" or "More Agile Testing" by Lisa Crispin and Janet Gregory. Or "Explore It!:Reduce Risk and Increase Confidence with Exploratory Testing" by Elizabeth Hendrickson. (Really, I mention those as a counter-point to the ones you referenced. I'm cool with the ones you have already. Honest!)

And because book reviews these days need to have some kind of ranking, I'll give your book four out of five emojis. (I would say 4.5 emojis but giving half emojis doesn't work, have you ever seen half an emoji? Also, the fifth emoji is reserved for something epic and just EPIC. If I ever give something five emojis, I probably sold my soul to it or they own this blog, whichever happens first.)

Humbly blogging,
Mel The Tester

Comments

  1. Alan RichardsonMay 25, 2016 at 4:25 PM

    Dear Mel,

    Thanks for taking the time to write your review. I'm pleased to learn you enjoyed "Dear Evil Tester" and that it caused your coworkers to question your sanity.

    I'm especially pleased to learn that you've read "Dear Evil Tester" more than once - the subliminal messages should now be deeply entrenched and the programming eagerly anticipating its trigger for activation.

    I too have read "Dear Evil Tester" more than once, more than twice, and even more than thrice and ... ye olde English liked to keep things concise, which is nice, so thrice will have to suffice (although to be imprecise I have read it even more than that).

    And seriously. Yes, seriously. Yes...

    I had to be picky with the Recommended Reading, I tried to keep it tight. I wanted a thin slice that would entice, much like a delicious choc ice.

    I did try to hedge though:

    "...there are so many books out there on Software Testing you should read as many as humanly possible".

    That was me sticking an "*" in the testing reading list query; as I knew I would miss out a favourite or two, or three as it were with thee. Hence, I'm cool with your resulting counter-pointed reading list "Agile Testing", "More Agile Testing" and "Explore It!", and I look forward to further reading suggestions on your blog and via your twitter feed. I'm particularly looking forward to seeing the unconventional ones.

    And thank you for the emojis, I shall wear them with pride and use them in every year input field that I encounter.

    "The trigger word is splendid." Thank you,

    @Eviltester

    ReplyDelete

Post a Comment

Most Read Posts

Ready, Tester One? *GO!*

"I handed my passport to the immigration officer, and he looked at it and looked at me and said, 'What are you?'" - Grace Hopper (60 Minutes Interview) The Grace Hopper quote above always makes me think about my job as a tester. Companies that develop software know they need testers, but they generally have hard time figuring out what testers are and what skills they need in the role. There have many discussions about how testers can be more technical and at some point, coding comes up in the conversation. My response on twitter contained a few things on a list I have, which I created for a client, so they could have a checklist of skills. This checklist was a guideline to determine the skill level of the tester applicant. This is by no means a complete list and I would be open to additions to the list. Feel free to add those to the comments or tweet them to me. For clarity, I took the list of skills I had and broke them into levels. I like games and I lik
Read more

Learning From Failure: The Tricky iOS Environment

"You build on failure. You use it as a stepping stone. Close the door on the past. You don't try to forget the mistakes, but you don't dwell on it. You don't let it have any of your energy, or any of your time, or any of your space."  - Johnny Cash There are times when our work, as a team, as testers on a team can give us insight into how we can improve things for the overall success of the product. Often those things are issues or defects which can present themselves at the most inconvenient times, in the most inconsistent ways. When we can learn from them and improve things for everyone on the team, the team benefits. When the team owns the defects and the testing strategy, not only the testers, then customers benefit as well. I was working remotely verifying a release and only had simulators and emulators to work with as I was testing mobile builds. Often folks mistrust builds which only use emulated software and not real devices for fairly good reasons
Read more

Postman In The Pipeline: Newman Delivers

Image
  It's not me, it's the songs.  I'm just the postman,  I deliver the songs....  - Bob Dylan Recently, I've had the chance to work on a project with some other awesome folks which has involved creating a BFF - A back end for front end service. This allows the app to access several API and aggregate calls into something the app can use, or lets the app send information to the BFF for several APIs to receive. Part of the code coverage for the BFF was creating some simple tests with Postman around the business logic and interactions. Learning About Postman I did lots of reading. Lots of reading how others has done things (Danny Danton - big props for being a super help!). Eventually, I came down to a small set of tests which could give us some accuracy about our BFF pipeline and the APIs we were accessing with it. Postman has a couple of options for this, global variables, environmental variables, and plain variables. One of the first problems I came across w
Read more