Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Don't get me wrong. I don't say you never need documentation. But wherever you can replace documentation with code, do it. If it works it will never outdate.
For instance write a Docker file instead of server requirements. That's code that documents it while in use.
Tests are often great documentation. Unit tests tell you how a function is supposed to behave down to the corner cases.
And when something changes, you actually update it nothing is worse than relying on outdated documentation
mgarg2616dAt least tests are there so you know if the methods are working as they should.. what should you do if all you have is functional documents and no details on how they are implemented. You go about writing a class and find out 3 weeks later that the five methods you wrote in that class actually already exist scattered around in classes having drastic naming distinctions.
j2k418215d@TheCommoner282 yeah I agree completely. This came about when there was some weird logic happening within the space of a few lines. I asked why the code seemingly repeated itself and the response was "oh, it gets rid of onboarding screens...". At a certain point, code comments should be considered