Interesting article, couple of opinions/takeaways:
I take issue with the term “monkey testing” as the activity to throw random scenarios at the software is a subset of exploratory testing. That’s what I would like to call. In some circles, I even came across people referring to Exploratory Testing as Monkey Testing.
Doing the testing in short sessions is absolutely crucial, not only does it allow you some break but it also gives you the opportunity to think on how the software has been behaving up until now; and what the next course of action should be.
Checklists, mind maps and just some old fashioned lists are very important as they keep important information ready on the go for you.
Another thing I’d like to add is planning. Plan your test session by jotting down pointers. Go free writing, just a sentence or two about the check and what oracles are relevant to it. I use a column approach and sometimes a mind map.
What the other testers(or anyone else in a testing role) would not have thought of?
Test less. Instead get myself involved with stakeholders, business, sales, marketing, and other people invested in the product and understand their assumptions and desires.
Start from the final point, explore backward, and analyze the branching and data domains.