16. Operational Best Practices

  1. Always keep the source project, output project, and converter workspace separate.
  1. Use clean output folders for serious test cycles.
  1. Back up milestone converter states before risky changes. Backups are extremely important to save accomplished work.
  1. Keep zipped milestone backups out of the live converter workspace so later workspace backups do not recurse and grow uncontrollably. Make sure they are off the development computer in another location, like a cloud service like DropBox, Google Drive, etc.
  1. Treat real compiler output as the authority over IDE-only hints or stale parse errors.
  1. Record what was fixed globally so later projects benefit immediately.
  2. Do not burn time on tiny visual tweaks until the application builds and runs
ContentsPreviousNext