Gehringer 2008

De wikicap
Révision datée du 22 août 2014 à 11:14 par Eric (discussion | contributions) (Page créée avec « Catégorie:communication = Damage Control: What to Do When Things Don’t Work = <BR> == 1. Références == * '''Référence complète APA''' : Gehringer, E. F. (2008)... »)
(diff) ← Version précédente | Voir la version actuelle (diff) | Version suivante → (diff)


Damage Control: What to Do When Things Don’t Work


1. Références

  • Référence complète APA : Gehringer, E. F. (2008). Damage Control: What to Do When Things Don’t Work. Proceedings of the 2008 American Society for Engineering Education Annual Conference & Exposition.



2. Copies


  • Copie physique :


3. Mots-clés



4. Résumé officiel / abstract

What should you do when your software breaks, when your labs don't work out, when your tests are bombed, when your homework has errors? These are questions every instructor has faced. This paper brings together a set of tips from dozens of experienced educators in dealing with these awkward situations. They tell us that it is best to be honest with students and admit your mistakes. Students will recognize that you are human, and besides, errors and changing requirements crop up on the job too, so learning how to handle them is good experience for real life. Often a mistake in an assignment or lab can be turned into a learning experience. There are many options in dealing with test questions that don’t work out for some reason. The weighting of questions can be adjusted in various ways, or homework assignments can be given to give the students a second chance to learn the material.


5. Résumé personnel (facultatif)

Sur base d'une enquête menée dans deux mailing lists d'enseignants en informatique / sc. appliquées,


6. Voir aussi