4 ms·
If you want to blame someone, you can always say that he didn't document his stuff enough. The problem is, that there is no standard, what's "enough", so it is
by vetinari 8y ago
If you want to blame someone, you can always say that he didn't document his stuff enough.
The problem is, that there is no standard, what's "enough", so it is easy to move the goal posts. Combine that with fast paced environment and putting out fires constantly, and you have a recipe for disaster.
- lawlessone 8y ago>If you want to blame someone, you can always say that he didn't document his stuff enough. This, he could have documented it perfectly well in a time when everyone knew COBOL. But that documentation would all be useless to me today with my knowledge of Java and Kotlin, but understandable to someone else from is generation that works with COBOL.