2 ms·
Exactly. For us who worked on the big software projects, it's something we think of all the time, with the extremes: - blindly making all class members private
by acqq 11y ago
Exactly. For us who worked on the big software projects, it's something we think of all the time, with the extremes:
- blindly making all class members private, most of the code is the burocracy and a little or even wrong job being done.
- allow everybody access to everything, a mess for the other aspects of brittleness.
Actively maintaining the balance is the hard problem which has to be done all the time as the requirements change all the time, but the task worth doing.