One thing I’m known for amongst many of my oldest friends is being willing to repeatedly tackle a problem. I will bang my head against a wall until it caves or I do. I’m not one to feel particularly bad about failing at something, nor do I tend to spend a lot of time caught up in self-recrimination. I’ll take a moment to assess what happened and what I could try differently and then get right back to it. I’ve got my limits, of course. I won’t keep tackling a problem I know I can’t solve and I’ll eventually give up for at least a while to rest if I’m feeling particuarly worn out by my efforts, but my limits for this kind of repetition and effort are much more expansive than most people I run into. This is one of the qualities that has made me a good software tester. Unlike a lot of my peers who will write up what they saw and move on if they can’t reproduce the issue quickly, I will (when the situation calls for it) dig in and keep messing with things until I either figure it out or I feel like I’ve done my due diligence. This is an ever-moving goal, unfortunately, but it’s still something I and my coworkers have come to count on. If there’s ever a tricky little bug with a lot of finicky details and no clear cause, I will usually be sent in to figure it out because I will just keep trying stuff without letting it wear me down. It’s worked so well in the past that everyone on my team knows me for this quality at this point, for better or for worse. They can always count on me to do whatever needs doing in as exacting detail as it needs (if not maybe a little too exacting sometimes).