I fully agree.  I have one include file for general functions, subroutines, etc., (many of which I haven't used in anything yet), and a separate one for large code blocks related to particular forms.  I like to be able to see the code in the sequence in which I perceive it, not in the sequence in which fields happen to be laid out.  (My normal coding style is to put functions and procedures at the bottom "out of the way" and have the main program sections call those, but I can't do that with Sesame.) Also, I just find it difficult to work with element-based "random snippets", since I learned coding before that approach was used.  And (as should be obvious), I don't prepare flow charts, etc.