The author shares insights from developing a reporting application that generates daily reports. Early in the project, they implemented a –dry-run option, inspired by similar features in Subversion and other Linux commands. This option allows users to preview the actions the application would take without executing them, providing a clear overview of which reports would be generated, files zipped, and uploads made. The author found this feature beneficial, using it frequently to check configurations and ensure everything was functioning correctly. During testing, the –dry-run option proved especially valuable. For instance, if the author modified a report's date in the state file, they could quickly verify whether the report would generate without the time-consuming process of actually creating it. This method allowed for rapid feedback and efficient debugging. While the implementation of the –dry-run option did complicate the code slightly by requiring checks at various stages, the impact was minimal, as it did not interfere with the report generation process directly. The author concludes that the application type suited the –dry-run feature well, as it operates on command execution rather than event-driven logic. Despite the minor code clutter, the early addition of this option enhanced the development experience significantly. The author emphasizes that while not universally applicable, the –dry-run feature can be immensely helpful in the right context.