Working on large projects often involves dealing with discontinuity, either because several people are involved or because a single person works on the project intermittently. It is therefore important to keep Grasshopper algorithms easy to understand regardless of whether the user is familiar with them. While good documentation of a file can go some way towards achieving this goal, it should be considered to be the last resort. Ideally, an algorithm is self-explanatory. To accomplish this, algorithms need to be both clean and small, and sadly neither property comes naturally to node-based editors such as Grasshopper. 

The entire day will be spent working on various aspects of a single, overarching project while keeping modularity, maintainability, and flexibility in mind.