I worry a little bit about things like this. If they were just using debouncing on a band-aid rather than dealing directly with the bad input that led to the ph

I worry a little bit about things like this. If they were just using debouncing on a band-aid rather than dealing directly with the bad input that led to the phantom breaking, then that would seem to imply that the project is falling into the classic death march project trap. It turns out that the last 10% of the project is going to be 90% of the work. Meaning that the original schedule was off by an order of magnitude. But the business has made made huge promises that mean that the team is not at liberty to adjust the schedule accordingly. And so they're under ever increasing pressure to cut corners and pile on quick fixes.