What's the best way to get code reviews pushed through? Assigning them to the most-familiar dev, assigning them to the quickest dev, or less familiar devs?
If they are to minimize the bus factor, are we asking the right question?
I am the founder at SourceField - I'm on a mission to solve the code review problem - to make code reviews suck less.
No comments yet. Be the first to comment.
We've noticed interesting trends...Tuesdays have the most code reviews. Wednesdays have the most PRs created. If we are supposed to get code reviewed fast, why is there such a large gap? (Note that not everyone is opening PRs right when they start wo...
Is it: a) poor syntax/styling b) too many bugs c) something else I'm curious what your views are.
If LLMs are probabilistic - do you trust the code output to chance, thoroughly inspect it, or look at it as part of the story? Most engineers will thoroughly inspect it due to its probabilistic nature. But inspection doesn't yield good knowledge shar...
Yesterday we released the first public version (v0.4.0) of our FREE Chrome Extension (see https://sourcefield.io or https://lnkd.in/gf-KesJu)! We've been testing it internally for a week & are excited!! We have v0.5.0 on-deck to improve code reviews ...
For years we've been told code reviews are the best place to prevent bugs. But code inspection doesn't scale. Given these conflicts - what is the purpose - reducing the bus factor, sharing knowledge, adopting standards, catching bugs, or ___? If they...