2 ms·
This happens every single time I make a new major release of a piece of software I maintain. There is always some mistake—even a typo in documentation—and it's
by LoganDark 4y ago
This happens every single time I make a new major release of a piece of software I maintain. There is always some mistake—even a typo in documentation—and it's the tiniest possible mistake, and there is always only exactly one mistake, but it's always enough to bug me so much that I have to make a patch release just to fix the one single mistake.
Some software developers are just cursed.
- junon 4y agoYep, have definitely done this once or twice with Chalk. I don't recall a time that a X.0.0 wasn't immediately followed up with an X.0.1 release for some dumb mistake I made.
- more-coffee 4y agoAnd that's why I never trust/use x.0.0 releases because they must have missed something :)
- thih9 4y agoIs not a curse, it’s probability and statistics. If you make a major release, you touch a lot of places and there’s a higher likelihood of introducing a bug.
- LoganDark 4y agoI review it 10 times before I make the release and spot nothing, but then spot something only immediately after I release it. Just like how I can only spot typos in emails after I've already sent them.