Handcrafting a Bug Report Like a Champion (part 2)

As we have already gotten ourselves acquainted with the building blocks and the semantics of how to communicate our program faults with a programmer, now its time to stress on the importance of the eloquence of the report. Albeit there is no silver bullet and each and every programmer would prefer bugs reported in a different way we hope to throw some light on the general economic consent of the blogpost - to save time for both parties.
Continue reading

Handcrafting a Bug Report Like a Champion (part 1)

Both customers and developers view bug reports in a different way. From the customers' perspective a bug report is the message that the customer sends when something is not working. Whereas the developer views the bug report as the needed information to get the problem fixed.
Continue reading