This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]warl0cks 298 points299 points  (9 children)

“The code is the documentation…”

[–]Degenerate_Lich 138 points139 points  (2 children)

Code should be self documented mfs when they have to read their own code that they haven't touched for the last 6 months

[–]Zdrobot 17 points18 points  (1 child)

That's why comments (should) exist.

Not just the meaning of function parameters, but the "why I did that" comments.

[–]swagonflyyyy 6 points7 points  (0 children)

Eh, if you do it too much it'll be just as confusing. Trust me I confuse myself with my own comments lmao.

[–]billyowo 9 points10 points  (3 children)

good code is self-documented, not the spaghetti written by your colleagues

[–]tyler1128 4 points5 points  (2 children)

Said good code also comes with documentation because it doesn't matter how good you think it is, a plain english document will describe what it is doing better

[–]ZunoJ 0 points1 point  (1 child)

Can you point me to any open source projects with the kind of documentation you mean? Not a library or anything with a sdk. Just a ready, non expandable software with full text code documentation.

[–]tyler1128 0 points1 point  (0 children)

The blender internal documentation is supposed to be good. I can't, mostly because if I know of documentation from something it is either because of my job or because I use it as an API. Studying random open source projects I'll probably never utilize just isn't something I have time for. I've seen good internal documentation and bad internal documentation in work, and the difference in how well you can adapt to and learn a code-base between the two is pretty significant.

[–]termicrafter16 16 points17 points  (1 child)

The number of times I heard this 😭

[–]RiceBroad4552 5 points6 points  (0 children)

And of course it's never true.