User testing is hard, and it takes years to master the skills to consistently deliver the kind of user tests that produce breakthrough insights. The good news, however, is that the skills you need can be learned, refined and polished over time. In this post, I look at seven of the most common mistakes made in user testing, and how to avoid them.
There are a lot of discussions, articles, and blogs around the topic of code quality. People say – use Test Driven techniques! Tests are a “must have” to start any refactoring! That’s all cool, but it’s 2016 and there is a massive volume of products and code bases still in production that were created ten, fifteen, or even twenty years ago. It’s no secret that a lot of them have legacy code with low test coverage.
In the twelve months since Ephox and Moxiecode merged we’ve been very focused on bringing new value to TinyMCE. We have added a variety of new capabilities to the open source version of TinyMCE, including image editing tools in 4.2, media embeds and code snippets in 4.3, and the new, minimalist “Medium-style” InLite theme in our latest update, 4.4.
The engineering team at Ephox tries to respect Brooks’ Law and keep it wholly. Breaking the law is nonetheless a constant temptation for managers when faced with schedule slippage. Every manager thinks, “There must be something we can do.” As a matter of fact, there is something to be done, but not by adding more developers.