Code reviews take up 20% of a good dev's time.
If you could accomplish the same goals, while drastically reducing the time...what would you do?
For further actions, you may consider blocking this person and/or reporting abuse
Read next
Using Weak Pointers in Go
Colin Dickson -
Brain debugging. Interview with Anders Schau Knatten, author of "C++ Brain Teasers: Exercise Your Mind"
Anastasiia Vorobeva -
AI System Learns How Objects Interact in Images to Generate New Scenes with Same Relationships
Mike Young -
Must-Know Ruby on Rails Gems for Improved Productivity
Patrick Gramatowski -
Top comments (1)
Basically , it depends on prj to prj and feature to feature
Ideally , granularise the requirements to smaller task's --leads to--> smaller PR's ----leads to-> less time . Otherwise , use static analyser tools which would obviously doesn't look up the functionality.