WM code is exceptionally well commented, don't you think wiki would be an overkill..?
It is probably true ... personally when I look at a project larger than 20 lines
I build a sort of
guide, because very often I resume on a project after some time. frequently restart and have
an overview of the current situation of the project can take her time.
Never mind, in the absence of other documentation, I will take longer time, and several
more tests to understand how and where to act ..
the only problem with the source code is people are lazy. also people can get lost (like i did)
looking at 1 things and expecting that to be it, but it never is ,there's always something else
you haven't looked at yet that adds an extra twist to what you wanted to do.
True, but almost all the programmers are "lazy" (1) ... although I am only a practiser.
And yes it is easy to get lost in the code and maybe miss the nuances or make treasury of
functions or procedures that are already present in the code, written by competent
programmers, but that you may ignore its existence.
(1) "lazy" in the exception of people who do not like to write more code than they need, and
like to reuse their work (already tried and tested).
