A work tool built and released by a practitioner who can't code

This lays out the whole process by which an editor with 10 years on the job, who knew nothing about coding, used a coding agent to build an extension for their own work and release it for free. The starting point was the stretch of going back and forth through searching, downloading, sorting folders and importing just to bring in one asset, and the conditions set before building were only two lines: don't switch to another window, and keep things tidy. Everything else in the design derives from there; what stands out in particular is that removing installation barriers was written into the functional requirements, that it states explicitly that credentials are kept on the user's computer rather than a server, and that audio loudness, which varies from source to source, is automatically normalized to a set standard with only that reference value broken out as a setting. Admitting that there is an operating system it could not be tested on, and adding environment-info collection and a path back to the previous version, amounts to the minimum operating safeguards for a release that no one is on hand to support. However, the making of it is covered only in a few minutes of retrospective at the end, so there is no knowing how many times it had to be re-asked or where it got stuck.

This is a note: my own write-up after reading several sources. It has no source link; events checked against a source are kept as records.