I'm consistently surprised by the lack of depth in programming psychology work. Search Google Scholar for "program readability", see all top-cited work. Consistently, the only methodology: literally ask people whether they think code is readable, and check for agreement.
-
-
Neither of those tests measure what matters. The test needs to measure how quickly I can make changes
-
That seems like an overstatement. I can think of plenty of languages, APIs, libraries I've read to check my understanding and find bugs, not to change their source code. However, I do agree that the ability to make a change is a useful test of comprehension.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
cognitive psychology. PhD