Of possible interest: * https://dave.autonoma.ca/blog/2022/01/08/logging-code-smell/ https://dave.autonoma.ca/blog/2022/01/08/logging-code-smell/ * https://da

Of possible interest: * https://dave.autonoma.ca/blog/2022/01/08/logging-code-smell/ https://dave.autonoma.ca/blog/2022/01/08/logging-code-smell/ * https://dave.autonoma.ca/blog/2026/02/03/lloopy-loops/ https://dave.autonoma.ca/blog/2026/02/03/lloopy-loops/ Both of these posts discuss using event-based frameworks to eliminate duplicative (cross-cutting) logging statements throughout a code base. My desktop Markdown editor[1], uses this approach to output log messages to a dialog box, a status bar, and standard error, effectively "for free". [1]: https://repo.autonoma.ca/repo/keenwrite/tree/HEAD/src/main/java/com/keenwrite/events https://repo.autonoma.ca/repo/keenwrite/tree/HEAD/src/main/j...