deletions | additions       diff --git a/culture.tex b/culture.tex  index ac8b8d8..f4a9d82 100644  --- a/culture.tex  +++ b/culture.tex 
...
\section{Towards a Learning from Failure Culture}  "Learning from failure" mindset. (Using Poka-Yoke techniques for early defect detection)     This paper describes the poka-yoke quality approach in genral, as well as our particular use of the technique in our localization efforts.     Poka-yoke is providing a simple, robust and painless way for us to detect defects early in our localization efforts.     Defects result from allowing a mistake to reach the customer, and defects are entirely avoidable. The goal of poka-yoke is to engineer the process so that mistakes can be prevented or immediately detected and corrected.     Steve Maguire (1993):   How could I have automatically detected this bug?   How could I have prevented this bug?     The tools in software that most closely resemble poka-yoke devices are the programs such as lint, etc. that examine the syntax of programs and alert the programmer to a possible mistake.     Areas that yield more readily to a poka-yoke approach than to traditional testing.     The sections that follow describe our application of poka-yoke principales to solve a problem that defied a traditional software testing approach.     (Poka-Yoke: applying mistake proofing to software)     It is well established that the cost of fixing a defect amplifies 10 to 100 times depending on how far the defect has gone unnoticed in the development process.     The point of a poka-yoke is. making a mistake is ok, just don't make the same mistake again and again.     We concentrate on more pressing issues, and let poka-yokes catch common and well understood project issues.     Instead of sending multiple bold font emails, crate a poka-yoke to ensure things don't break again.     Whenever there is something to warn to people --- instead of writing long emails and wiki documents, one should pause and introspect. Ask the question: Can I redesign the system/process such that mistakes cannot be made. Or can I put in a check in software, such that if mistakes occur, then they can be caught quickly. If yes, then consider the poka-yoke.