3 ms·
Display bugs are pretty harmless (e.g., a label being a few pixels off its correct position). Also, consistency bugs are hard to notice sometimes. These bugs
by amichail 18y ago
Display bugs are pretty harmless (e.g., a label being a few pixels off its correct position). Also, consistency bugs are hard to notice sometimes.
These bugs irritate the developer, but probably not the user.
- scott_s 18y agoThere's more to "user experience" than display.
- amichail 18y agoWhat do you mean? One could restrict the intentional bugs to various types that are known to be minor.
- scott_s 18y agoSay, something as basic as passing around user data. Bork that and the user is paralyzed. Software systems are already complex and difficult to reason about. Intentionally making them more complex with no appreciable gain and more difficult to reason about for a problem a tiny fraction of the population has seems like a Bad Idea.
- amichail 18y agoIntroduced bugs would be guaranteed to be minor by restricting them to types where you can ensure that this is the case. There is no need to do any of this if none of your developers suffer from this problem. But I suspect that many developers will get this problem as a result of their profession.
- scott_s 18y agoWhen reasoning about the system, one still has to reason about the introduced bugs, because it's always possible there's a bug in the introduction of bugs. In fact, given the difficulty of proving the correctness of non-trivial programs, I think it's likely the introduced bugs would bleed out into the rest of the system. I sincerely doubt any developers would "get this problem." The behavior you're describing is severe OCD. You don't catch it like a cold. If one's OCD is that severe, it will probably manifest in many more areas of their lives than just programming. There's also the fact that most developers work in teams, and the people who don't have this form of OCD would not tolerate having purposefully introduced bugs. I know I wouldn't.