I’m definitely in the MOIST camp apparently 
. I’m struggling to understand the point of the composition. If the point is to count down from 3 to 0, then sum the countdown, I’d just do as in the attached composition (but would probably not comment it that much if it wasn’t for the task). It does pretty much the same thing, and is by the looks of it a tad bit faster at it. I got <.03333 seconds for the attached comp repeatedly at ideal conditions VS <.050000… seconds in the original. These are based on frame times though, and can be impacted quite a bit by other open windows and overlays so a couple grains of salt is needed for that timer. I did get outliers at .16 and .18 respectively sometimes for both of them.
I use node naming a lot when building my own stuff rather than comments. Trying to make it easily readable/understandable from the nodes and structure itself is less time consuming than excessive commenting. When noodling intensifies, focus on commenting quickly looses its importance. I look at it as a tradeoff between getting things done and getting things done correctly. That can depend on who is paying the bill. If it’s a one-off exported app, it doesn’t matter much. If it’s a repeated task, a commented subcomp is usually better (to then drop into small exports). If I’m the only one that looks under the hood, and I can understand what’s going on from node names and colors, I wouldn’t care much about comments. If it’s for others to see, use and modify - comments are very necessary.
Refactored.vuo (3.68 KB)