deletions | additions       diff --git a/introduction.tex b/introduction.tex  index 9b7ba2a..479166b 100644  --- a/introduction.tex  +++ b/introduction.tex 
...
Construction and aircraft industries publish their mistakes so lessons can be learned.  There are innumerable sources reporting engineering disasters like Tahoma bridge collapse, etc. However, except few exceptions (Writing Solid Code), there are no equivalent references in the software industry. Neither the more popular and acclaimed books about the code of conduct for professional programmers (The Clean Coder: A code of conduct for professional programmers, The Pragmatic Programmer: from journeyman to master) refer a word about the practice of learning from failure.\subsection{The current role of failure}     The focus is in fixing the bugs as soon as possible, not in how to improve the software development process that allowed the bug progress through to production.     In the best cases: write emails to the development team or write defects catalogues in a Wiki.     Can software defects be prevented by simply logging them into some "defect tracking tool", documenting them and providing fixes for them? How we can share lessons learned to avoid future defects?     Currently, software failures are an embarrassing subject, but we should learn from other engineering disciplines and used them as an opportunity to improve our future designs.