Testing code often by passing it through the cajoling process can help eliminate issues early and give developers a good idea of their project’s progress.
Developing code in a modular fashion—e.g., building encapsulated reusable blocks in standard functions—is the first step in ensuring that it can be tested in blocks. The goal to this approach is the ability to integrate function by function into the script that is being cajoled, so you can deal with errors and warnings from the cajoling process in a much more manageable way.
When migrating an existing code base to an environment that runs Caja, you can use this approach as well. Working with small blocks of code instead of attempting to debug an entire code base can help you manage the output of the cajoling process.