3 ms·
I can think of two cases, either : 1) the code had no external review, was written by one person. In this case, the solution to boilerplate is code review. or
by antpls 7y ago
I can think of two cases, either :
1) the code had no external review, was written by one person. In this case, the solution to boilerplate is code review.
or 2) if even with code review there is boilerplate, it means someone somewhere has an incentive to make the code as difficult to understand as possible (for example, to justify salaries of an entire team, or to justify more maintenances, etc)
- JackFr 7y agoIn particular I know one code base of consultant written Java where part of their contract was 100% Javadoc coverage and 100% test coverage, so you would see tests of getters and setters and Javadoc for getFoo(): "Gets the value of foo" The code worked, but 80% of it added no value.
- vincnetas 7y agoDon't blame consultants for such requirements.