A short comment but the one I was looking for in this thread. People often forget the "People over Process" part of agile which implies no Methodology is going to be the answer. All you can hope for is to create the correct process (methodology) for the people you have at the time.
Trying to fit the people to the process is why software methodologies fail.
字学 is the kind of confusion you run into only when you learn simplified Chinese. If I have to interpret 学, it looks more to me like a person sitting in a house on fire; whereas the traditional form 學 is a man holding 爻 in his hands in order to learn his fate, hence "learn". Similarly, 覺 is one who sees (見) his fate. Chinese characters are created with all sorts of clues for you to pick up. It is unfortunate that some of these clues got taken away with the simplification of the language. 學 is not only more distinguishable than 学, but takes the same amount of effort to type.
Well put; I share the same sentiment. I feel that one of the strongest arguments for traditional characters is that it retains the original meanings behind the characters themselves. Simplifying the characters just throws information away. It's a lossy compression!
