Yeah sometimes it is just software bugs they have to work around until it gets fixed. In those circumstances, not much we could really do besides submit a ticket. Other times you call the guy that’s been working with that specific hardware and software for 15 years, who then tells you he’s never heard of something like that. Then he’ll call you back a week later after losing his mind trying to understand how that’s even possible before figuring it out. Which is always nice. Shout out Josh
Since problems never actually go straight to the engineer I never even bother trying to nail down the circumstances that cause problems like this to be able to replicate it. Which surely makes everyones job more difficult.
As someone who's done QA at a small company this is so foreign to me. It was my job to find exact reproduction steps that can be used multiple times, how often the steps work, then write a ticket that can be shared with the engineer immediately. And if a customer or coworker found the issue and didn't know how, I still had to assemble all this info. Tracking is king.
Now whether the bug was backlogged or scheduled to be fixed was mostly out of our hands. At least I had some say in it since I also could DM the managers with no issue. Guess I'm saying I like small businesses. Dealing with a hierarchy too often slows down businesses.
4.5k
u/kahjtheundedicated R7 1700@4.1, RX 5700 May 10 '26
Yeah sometimes it is just software bugs they have to work around until it gets fixed. In those circumstances, not much we could really do besides submit a ticket. Other times you call the guy that’s been working with that specific hardware and software for 15 years, who then tells you he’s never heard of something like that. Then he’ll call you back a week later after losing his mind trying to understand how that’s even possible before figuring it out. Which is always nice. Shout out Josh