Bei meinem Code kommentier ich sogar schön alles aus und ich achte auf eindeutige Variablen. Allerdings mehr für mich selbst - wenn ich mal ne Weile keinen Bock mehr auf das Projekt hab und mich dann wieder einarbeiten muss, hilft mir das. :))

najo, in der realen welt geht's ja meist nicht um ein paar zeilen, sondern um ein komplexes system an sich, das auch meist 'ne eigene API mitbringt... und 'ne API ohne doku...

Disagree. Code tells you what is done, but not why it is done.

Exactly! My statement was pur irony. I thought that'd be obvious.

well it's indeed a trend to use fewer and fewer comments these days, much goes rather into git messages etc... and if not creating a new 3D engine or something, actual code should become more and more trivial and self-explanatory these days with all the high level languages and libraries available. And if you do unexpected or unsual things at code level, it's rather that you should rethink your architecture and design (in practice, indeed most comments would then start with // hack or // workaround until...).

The difficulty nowadays rather lies in putting things together, and that doesn't happen at the code level. But this is what has to be documented, and documentation would typically be rather outside of the code then.

Well but indeed good code can explain a lot without the need to going to deep into every line (good naming, order,...)

But as you all say, it's not a replacement to docs that tell you the basic ideas and the why :)

the simplest solution is usually the most correct

good code requires less documentation than bad code :)

Good software doesn't even need code - it just works out of the box.

Yeah, damn right! And it perfectly guesses what the user was thinking.

... if it doesn't, the user didn't concentrate hard enough!