Where a screenwriting app keeps its logs

Preferences named a folder for a screenwriting app's logs, offered to open it, and described what lived inside. Eleven days later, the folder did not exist.

When something goes wrong in the app, the log file is how the writer and I find out what happened, so a log folder that cannot be created is a support problem, not a tidiness one. The app had asked the system to create the folder, and the request had quietly done nothing. The path ended in a dot, which the system reads as "create the parent folder instead", and the parent already existed. The only place it could fail was the one place nobody was looking.

Two decisions kept it invisible, and each is defensible on its own. Logging swallows its own errors, because a broken logger should not take the app down with it. And Preferences described the folder by name rather than checking it existed. A caught error plus confident prose is how you ship a feature nobody notices is missing, including the people who wrote it.

The general problem is scaffolding. Nobody watching a film sees the rig holding the camera, so nobody notices when a piece of it is gone. That is fine until something leans on it.

It is also why a bug report is much easier to answer with the log file attached, and why the same instinct runs through the checks that catch a bad release before a writer does.