code reviews...

[juan_gandhi]

they improve reliability and kill creativity

Comments

[sorhed.livejournal.com]

Like all other social activity, it depends on who you review your code with and on if this voluntary.

[trurle.livejournal.com]

Я бы сказал что настоящая креативность - это выразить сложные идеи просто.
А писать сложный код, с трудом проходящий ревью означает планировать ад в процессе отладки и сопровождения.

[agathpher.livejournal.com]

"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." – Brian W. Kernighan

[sab123.livejournal.com]

Это вы их готовить не умеете.

[vit-r.livejournal.com]

Красота - слишком хрупкая штука. Не выдержит вмешательства умелых ручек. Так что лучше всегда попроще и подубовее.

[archaicos.livejournal.com]

I'd rather have fewer creative WTFs in code in the first place than having to become creative in debugging and fixing them some time later.

[nine_k]

Some code reviews made me throw away clever and creative code and replace it with something simple.
Other code reviews made me throw away clumsy code and be quite creative to express the same thing clearly and simply. (And shorter!)
Also, defending one's decisions in review comments is sometimes fun :)

[dennisgorelik]

Unit tests detect ~25% of bugs.
Integration tests detect ~35% of bugs.
Code review detects ~60% of bugs.

+ code review helps to share experience between team members, including creative experience.