Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My test whenever I get handed someone else's code with a debounce routine is to hammer the buttons with rapid presses, gradually slowing down. That shows if the filter is too aggressive and misses legitimate presses. I also see strange behavior when they're implemented wrong like extra presses that didn't happen or getting stuck thinking the button is still held when it isn't.


What kind of line of work gives you the ability to discuss debounce routines as an everyday enough occurrence to speak with authority on the matter, if you don’t mind me asking?


Pretty much anything that involves direct conversations with hardware.

I build medical devices.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: