Code Review: It's Bad, Expensive, and Ineffective [in most cases]by@sharovatov
1,514 reads

Code Review: It's Bad, Expensive, and Ineffective [in most cases]

tldt arrow
Read on Terminal Reader
Read this story w/o Javascript

Too Long; Didn't Read

In this post, I will try to investigate the rationality of “blocking mode CR” — a CR where code is not deployed until reviewed. CR used to find defects is usually stated as “find defects’ find-and-fix cycle’s find and fix cycle was extremely long and expensive. My hypothesis is that this using a tool that is not effective was due to the unprecedented growth the industry witnessed: companies grew fast, developers got promoted to managerial roles with almost no training so that rational sociotechnical systems and processes design was almost a “no-clue”

People Mentioned

Mention Thumbnail

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - Code Review: It's Bad, Expensive, and Ineffective [in most cases]
Vitaly Sharovatov HackerNoon profile picture

@sharovatov

Vitaly Sharovatov

Pragmatic humanist. 13 years of JS development, 7 years being a teamlead and consultant. Love sports and cats.


Receive Stories from @sharovatov

react to story with heart
Vitaly Sharovatov HackerNoon profile picture
by Vitaly Sharovatov @sharovatov.Pragmatic humanist. 13 years of JS development, 7 years being a teamlead and consultant. Love sports and cats.
Qase TMS

RELATED STORIES

L O A D I N G
. . . comments & more!