|
|
|
|
|
by basil-rash
874 days ago
|
|
How can you claim your knowledge of the field is actually deep, if you’ve never even done anything with it? Knowledge without application is nothing, imo. True “depth” comes from the know-how acquired in digging through all the minutia nobody else though to document, on your way to producing a new creation nobody else thought to build. |
|
The trope that software projects are poorly documented is so pervasive as to be saying nothing at this point. Despite extremely useful and celebrated documentation projects (MDN and Python off the top of my head) that dramatically accelerate other peoples' learning and productivity.
But when the topic is raised, the response is always "But we don't have time for documentation".
And when that time is given it becomes "It will be useless or out of date soon anyway, just go read the code" (As if there is nothing between non-practical high-level docs and per-line code comments.)
And when forced it becomes "Fine, but it won't be any good" or "Other people won't read/benefit from it anyway".
And when it's done, often as little effort as possible is put into it.
All of which smell to me like cover stories for: "I just don't want to do it."