| ▲ | gertop 15 hours ago | |
To be fair it also stinks of arrogance to think that you have the skills to know "what is clearly a bug" 100% of the time in projects you don't own. | ||
| ▲ | Const-me 14 hours ago | parent | next [-] | |
> to know "what is clearly a bug" 100% of the time in projects you don't own Owning a project is counter-productive for QA. If it’s your project, you know where to click and where to not click. OTOH, you don’t need to know anything about a project to conclude that a crash with access violation, or hang with 100% CPU usage, are clearly bugs. | ||
| ▲ | RobotToaster 12 hours ago | parent | prev | next [-] | |
>90% of the time it's usually pretty clear if something is a bug, especially if there's log files full of errors. | ||
| ▲ | pbhjpbhj 12 hours ago | parent | prev [-] | |
Fwiw, you might have misinterpreted the idiomatic expression "all the time" as meaning "100% of the time". It just means "often" or "commonly". The parent is just saying they often find bugs, they know they're bugs through experience. Of course anyone can make a mistake. Maybe you prefer the 'discussions' route because it's only seemingly then possible for a projects own devs to make a mistake in creating an issue. | ||