Get the latest tech news
Separation of Concerns in a Bug Tracker
[Simon Tatham, 2024-11-01] I write software, both professionally and on a ‘serious’ basis in my free time. So I interact with bug trackers.
Certainly they’ll need to refer to each other; you’d need to do atomic transactions in the tracker that cover both at once; and in some cases you’d want to enforce that both things are updated at once (because the data would be left in an inconsistent and nonsensical state otherwise). As I said earlier, one reason it’s a bad fit is that real bugs can usefully have a bunch of data fields that don’t really apply to the lack of a feature, like “when was the problem introduced?”. Maintaining the software turns from a labour of love – “I program because it’s fun for me, and it makes people’s lives better too, everyone’s happy!” – into a chore that at best reduces the level of guilt (“oh, god, I suppose I ought to at least get some of this to-do list done this weekend”).
Or read this on Hacker News