Testing designs, testing software, testing documents.<\/p>\n
We need to teach students that testing is part of all product development.<\/p>\n
Instead, we focus on details that overlook the final deliverables.<\/p>\n
We edit documents for grammar and spelling. We check code for \u201cstandard\u201d formatting. We compare designs to theories, grading accordingly.<\/p>\n
Do we test what students create? More importantly, do we ask them to test their creations?<\/p>\n
Forget what is \u201ccorrect\u201d in the land of prescriptive, proscribed rules. We obsess over the rules when the works being created might not be usable (or useful). What good is a \u201ccorrect\u201d design or document that doesn\u2019t meet the needs of a genuine audience?<\/p>\n
Make testing part of what you teach. Make it as important or more important than following arbitrary rules.<\/p>\n
I understand that rules help us communicate. They help us pass along code or designs to other team members. Rules have a purpose. Yet, are we focused so much on the rules that we forget a good finished product is one that others will use?<\/p>\n
Just a random rant after a week of watching classes that were all about the \u201ccorrect\u201d indents and the \u201ccorrect\u201d naming conventions, with more points awarded for following rules than creating working code.<\/p>\n","protected":false},"excerpt":{"rendered":"
Testing designs, testing software, testing documents. We need to teach students that testing is part of all product development. Instead, we focus on details that…<\/p>\n