* to read is to write elsewhere ⇒ Seeing Through Transparency
It is widely accepted that software developers spend more time reading code than writing it [LVD06]. -- Parsing For Agile Modeling, p. 8
> Reading code not only promotes program comprehension, but helps developers understand the impact of their changes on the existing system. Nevertheless there are numerous questions developers ask that cannot simply be answered by reading code, such as “which code implements this feature?”, or “what is the impact of this change?”, and for which dedicated analyses are needed [SMDV06, NL12].
⇒ Moose
⇒ Rascal
* a Variable ⇒ Read a Variable
DOT FROM lambda-browsing