I have a post out on the Intel Software blog about my experience developing and delivering training for Simics over the past few years. A key observation is that building training is a great way to test the product, and drives changes and improvements in the product. The blog is found at https://software.intel.com/content/www/us/en/develop/articles/teaching-users-drives-product-improvements-in-simics-sw.html
There is one drawback from finding issues… once they get fixed the product changes. And you have to get back in and update the training… repeat. But it is still better than not reporting the issues and improving the product, obviously.
