4 ms·
Our QA has zero working hours overlap with backend engineering, which has one working hour overlap with mobile engineering. QA’s bug reports never include the r
by closeparen 6y ago
Our QA has zero working hours overlap with backend engineering, which has one working hour overlap with mobile engineering. QA’s bug reports never include the relevant IDs on the first pass, so if it’s potentially a backend issue where we need logs, we have to comment on the JIRA and wait 24 hours. It’s amazing. I wish we could have zero bug tolerance or drop everything to fix bugs. Local management would even like to. But a globally distributed cost-conscious company is physically incapable of collaborating that fast. All we could do is sit there and twiddle our thumbs while waiting for our peers around to the world to wake up and see our messages. So we work on features.
- samus 6y agoThis rather sounds like your management struggles to improve the bug reporting process, or that they don't care. Features can always be developed separately and parked in a branch or Pull Request (plenty of open source projects work that way). But it must be crazy to have ~24h turnaround time. If it's a more complex bug then you are looking at a week completely lost just waiting for the sun to rise on the other side of the world!
- chrismorgan 6y ago> But a globally distributed cost-conscious company is physically incapable of collaborating that fast. Penny-wise, pound-foolish. Sounds like they’re saving money by cutting corners and that that is incurring a cost greater than the amount saved.