this is for holding javascript data
Rafael Luque deleted file role-of-failure.tex
over 10 years ago
Commit id: c707df0a923a190a5569fb230cdc3ac107e4f17a
deletions | additions
diff --git a/role-of-failure.tex b/role-of-failure.tex
deleted file mode 100644
index c75e894..0000000
--- a/role-of-failure.tex
+++ /dev/null
...
\section{The current role of failure}
How are you or your team managing the failures?
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.
