Mastodon Feed
Boosted by glyph ("Glyph"):
pathunstrom@ngmx.com ("Piper Thunstrom") wrote:
Seeing talk about a +93000 line pr and reminding folks that a good rule of thumb for how long a good code review takes is 1 hour per 50 lines of diff.
Which means to have reviewed that "properly" would take ~1860 hours, assuming the rule of thumb is accurate and scales linearly.
To reduce that further, if I convert that to work weeks, that's 46 full-time work weeks doing nothing but code review.
(I could grab other stats to point out that more likely that's over two calendar years of actual knowledge work patterns, but this is already dire.)