Albin7326@suppo.fi to Programmer Humor@lemmy.ml · 9 months agoComment Your Code Peoplesuppo.fiimagemessage-square123fedilinkarrow-up11.56Karrow-down125
arrow-up11.54Karrow-down1imageComment Your Code Peoplesuppo.fiAlbin7326@suppo.fi to Programmer Humor@lemmy.ml · 9 months agomessage-square123fedilink
minus-squaremagic_lobster_party@kbin.sociallinkfedilinkarrow-up1·9 months agoAccording to who? If I have access to the source code, which I often do, I’d rather just read the code. Chances are that if documentation exists, it’s no longer up to date.
minus-squareauchschonda@feddit.delinkfedilinkarrow-up2·9 months agoModularity. Part of it is defining a proper Interface for using the hidden complexity. Exceptions are only one example. Functions can have behavior, inner states, prior calling requirements etc… you cannot read from its mere prototype. Do you really want everyone to read the inner code to learn that? Chances are that if documentation exists, it’s no longer up to date. This risk also applies to descriptive function names. They can be poor, wrong or outdated, too.
According to who? If I have access to the source code, which I often do, I’d rather just read the code. Chances are that if documentation exists, it’s no longer up to date.
Modularity. Part of it is defining a proper Interface for using the hidden complexity.
Exceptions are only one example. Functions can have behavior, inner states, prior calling requirements etc… you cannot read from its mere prototype.
Do you really want everyone to read the inner code to learn that?
This risk also applies to descriptive function names. They can be poor, wrong or outdated, too.