Visual Programming Doesn’t Suck

Re:Visual Programming Doesn’t Suck by pacala on Tuesday January 29, 2019 @10:32AM (#19027093)

Ordered <set of items> have the advantage of working well with the brain's ability to map its surroundings. "function foo is defined 5 arrow downs above function bar". When the <set of items> jump around our eyes in arbitrary order, we tend to experience disorientation.

[ Parent | on HN ]

Re:Visual Programming Doesn’t Suck by pintxo on Tuesday January 29, 2019 @10:46AM (#19027213)

Same here.

OTOH I always wonder if it would not be beneficial if our brain and the code would not rely on spacial distances in code files, but on _call_ distances.

Should our spacial map of the code not be the call graph instead of the structure in files and disk?

[ Parent | on HN ]

Re:Visual Programming Doesn’t Suck by vidarh on Tuesday January 29, 2019 @12:09PM (#19027935)

The call graph can change dramatically with relatively small code changes.

[ Parent | on HN ]

Re:Visual Programming Doesn’t Suck by wires on Tuesday January 29, 2019 @12:59PM (#19028381)

Totally! I imagine a web of types and function definitions (as diagrams)

[ Parent | on HN ]