Faults are bound to happen, as bugs are bound to be introduced. Developing MyFlickr involves modern techniques for preventing bugs such as TDD, but I want a better way to prevent issues in the long run.
A simple and powerful main strategy for handling bugs is a process that evolves to prevent bugs of a similar kind to reccur. Just fixing a bug kan be harmful in that it stops the process from evolving to limit future opportunities for similar bugs to get introduced. The development and maintenance process should periodically or continuously evaluate the root causes of the problems so far.
So, to start with MyFlickr
MyFlickr has had four faults so far that has impacted live usage:
XXX users would probably like a record of problems.
XXX issue tracking should be used to record problems that have occured.
XXX alarm log file
A simple and powerful main strategy for handling bugs is a process that evolves to prevent bugs of a similar kind to reccur. Just fixing a bug kan be harmful in that it stops the process from evolving to limit future opportunities for similar bugs to get introduced. The development and maintenance process should periodically or continuously evaluate the root causes of the problems so far.
So, to start with MyFlickr
MyFlickr has had four faults so far that has impacted live usage:
- 3pp library using non-thread safe XmlParser having an object re-use check causing sporadic race-conditions; (Fixed with patch for the library)
- Null-pointer exception when saving site settings with no prior custom CSS setting.
- Problems when registering towards Flickr because authentication tokens where not reset for unregistered users. Could have been handled by 3PP, incorrectly assumed to be so.
XXX users would probably like a record of problems.
XXX issue tracking should be used to record problems that have occured.
XXX alarm log file
0 comments:
Post a Comment