Formalizing programmers errors
        Posted  
        
            by 
                Maksee
            
        on Programmers
        
        See other posts from Programmers
        
            or by Maksee
        
        
        
        Published on 2012-04-15T19:16:25Z
        Indexed on 
            2012/04/15
            23:44 UTC
        
        
        Read the original article
        Hit count: 354
        
Productivity
|bug
Every one of us make errors leading to bugs. Once I wanted to start logging my errors for future analysis, probably mentioning project title, approximate time spent and the most important, the type of error. For example when I copy-pasted a fragment about 'x' and replaced every occurrence of 'x' with 'y' and forgot to replace a tiny piece, this goes to 'copy-paste error'. The usefulness of this approach depends on whether I can formalize my errors at all and probably minimizing the number of types to choose from. Otherwise I would start postponing, ignoring and so on so make this system useless.
Are there existing research in this area, probably a known minimum set of errors? Maybe some of you already tried to implement something like this and succeeded/failed?
© Programmers or respective owner