Welcome dear subscriber! Glad to have you here with us. This is our first newsletter from PM/QA side. Big thing, much wow!
Once a month, we will be sending you #goodreads that we find interesting. We will even try to slip in some bad joke to cheer you up. Enjoy the reading!
A software tester might do several different things throughout the day, but reporting bugs are still the bread and butter of the job. A good bug report means bugs can be squashed faster, and the faster they do, the sooner the product can be declared shippable. This post will try to lay out the basic how-to’s which could prove useful to any aspiring tester, project manager, designer, or your run-of-the-mill bug aficionado.
When athletes want to improve, they typically spend hours reviewing video of their performance. In the white-collar workplace, it’s hard to get such vivid feedback.
Sometimes complicated solutions are necessary, but simple rules often outperform complex algorithms, making them more efficient than sophisticated, difficult flows.
If following a ‘company rule’ is obviously ridiculous in a particular situation, such that it would make for a great Dilbert cartoon, then the rule should change.
The feedback you give -- and the way you give it -- can be the difference between a project everyone loves, and a project everyone wishes had never started in the first place.
