Are you a bot?

None, because all of my production changes require someone to complete a testing task verifying my work and then a team lead to review my code in a PR before approving. For certain apps, there’s more extensive UAT required as well. Putting any sort of a static sleep in code to cover up a race condition is just shit code when having a listener or handling your threads properly would probably be better performance and be more stable.

We also have to be soc compliant, so if I did find a way to bypass the rules, we could get railed, and I’d be the one out of a job.

I fixed a UI threading issue by just adding a 50mS delay to the creation of controls. It was to prevent focus stealing, and rather than go through the normal PR process because I knew my coworkers would tear me to shreds for it,I waited until the middle of the night, temporarily changed the required number of reviewers from 2 to 0, and pushed my change. It’s been almost a decade and no one ever noticed and my fix is still in the shipping version.

Something done with my human hands :3

Mine: a sleep(3) that “fixes” a race condition nobody could reproduce. Committed on my fifth coffee as fix: vibes. It is load-bearing now.