From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Sat, 18 Aug 2007 16:06:04 +0300 From: Michael Shigorin To: smoke-room@lists.altlinux.org Message-ID: <20070818130604.GP24364@osdn.org.ua> Mail-Followup-To: smoke-room@lists.altlinux.org Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.1i Subject: [room] Three Questions About Each Bug You Find X-BeenThere: smoke-room@lists.altlinux.org X-Mailman-Version: 2.1.9rc1 Precedence: list Reply-To: shigorin@gmail.com, =?koi8-r?b?y9XM2NTV0s7ZyiDPxtTP0MnL?= List-Id: =?koi8-r?b?y9XM2NTV0s7ZyiDPxtTP0MnL?= List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2007 13:06:07 -0000 Archived-At: List-Archive: Здравствуйте. Мож пригодится кому... http://www.multicians.org/thvv/threeq.html The key idea behind these questions is that every bug is a symptom of an underlying process. You have to treat the symptoms, but if all you do is treat symptoms, you'll continue to see more symptoms forever. You need to find out what process produced the bug and change the process. The underlying process that caused your bug is probably non-random and can be controlled, once you identify what happened and what caused it to happen. 1. Is this mistake somewhere else also? 2. What next bug is hidden behind this one? 3. What should I do to prevent bugs like this? -- ---- WBR, Michael Shigorin ------ Linux.Kiev http://www.linux.kiev.ua/