←back to thread

94 points justin-reeves | 1 comments | | HN request time: 0s | source
Show context
LiamPowell ◴[] No.46004693[source]
See also: The VLC bug that incorrectly applies right crops as left crops [1]. This bug report is from 2023, however the bug has existed as long as VLC has as far as I know.

I'm always surprised to see bugs like this where an extremely easy to test part of the spec just seemingly isn't tested and ends up as a bug that never gets fixed until many years later.

[0]: https://code.videolan.org/videolan/vlc/-/issues/28279

replies(2): >>46004894 #>>46004920 #
moron4hire ◴[] No.46004920[source]
I firmly believe every product team needs to be split in two: one half works on the issue of highest importance, the other works on the easiest issues. If only to avoid the embarrassment of easy to fix bugs that were passed over for eons just because they weren't priority-high.
replies(6): >>46004967 #>>46005031 #>>46005096 #>>46005360 #>>46005498 #>>46005626 #
Avamander ◴[] No.46005031[source]
I don't this makes business sense in general.

I do however think that there are quite a few bugs that might be triaged as "easy" but if worked on would reveal much more serious problems. Which is why some random selection of "easy" issues should make it to work queues.

replies(2): >>46005941 #>>46009526 #
1. ozim ◴[] No.46005941{3}[source]
Makes business sense if you want to fill in developers down time - instead of waiting for CR or QA feedback pick up small bug.

Working on two or more big features at the same time is not possible. But throwing in some pebbles and dev can take on it.