4 ms·
Overall, for bigger and more complicated systems you would have an architecture that is peer reviewed and communicated internally. Afterwards you have individu
by whazor 5y ago
Overall, for bigger and more complicated systems you would have an architecture that is peer reviewed and communicated internally.
Afterwards you have individual components that have their code reviews and still need to follow industry best practices. I think external code reviews is great idea as it could allow the team to focus more on conceptual reviews and consequences to other systems.
- noduerme 5y agoI've yet to see a company ask for feedback once they were done pushing out a half baked API. And if anyone uses it, they do get plenty of feedback. As far as whether the code is internally badly written... if the guy writing the code can understand the suggestion, he's probably already done it or decided why not to do it. If he can't understand the suggestion, then it's a waste of money.