3 ms·
With my commercial projects I've always had a policy of no known bugs. If I wasn't able to handle this then I'd consider it a warning that the scope of the proj
by tonyedgecombe 8y ago
With my commercial projects I've always had a policy of no known bugs. If I wasn't able to handle this then I'd consider it a warning that the scope of the project was too large.
- vortico 8y agoI wish I was on that side of the spectrum. Mine is on the other extreme. :)
- dbdjfjrjvebd 8y agoAnd this is how to retain users. Although you might struggle to sell support contracts with preferential access to bug fixes...
- rwmj 8y agoI'm interested in how this works. Obviously there are bugs which can and should be fixed - but how about bugs which are really feature requests, or bugs which are extremely complex to fix and only affect 1 person? Do you mean that you close out these bugs very quickly without fixing them, or do you take superhuman efforts to implement everything?
- 8_hours_ago 8y agoBugs can be triaged into deficiencies and new feature requests. Usually new feature requests are handled differently than actual bugs. For hard-to-fix bugs that don’t affect many people, sometimes documenting it as a known issue along with a workaround is good enough.
- tonyedgecombe 8y agoI don't worry if it only affects one person, I assume there are more that haven't told me or haven't found it yet. I also don't worry if it's complex, I have had seemingly simple requests take several weeks although that is quite rare. I have never closed a bug as won't fix.