![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjcDam84dyZQ2-y-K3RHDSaPOCelU6p56_RYXSxoCY7-XC2ui3P9hroM89ZMCbMrkcF0YwlA-gcNUNHmnvYTE5cCvTtGWQJrcGk_pmcjmCwc3xEMaSLHfIjrc5Uu0-sHD696vFUaWBzqNw/s640/vgl9n.png.jpg)
Now, here's an interesting way to motivate developers: Name the person who likely created the error. Rather than a stack trace, display the name of the developer who last checked in the code that failed? ;)
when software discombobulates
Software testing tools: Heuristics for recognizing problems.
from James Bach
and Michael Bolton
0 Comments:
Post a Comment