Current practice in APL programming (and in most other languages) is to use comments to describe what is intended by subsequent lines within a function. An alternative approach to commenting is described, wherein assertions (a concept borrowed from program proof techniques) are inserted into APL code, specifying the present state of relevant variables, etc. It is shown that this approach is especially appropriate for APL, as most APL design is accomplished by working from a desired end result, backwards.