I am an interdisciplinary researcher investigating how technology can be used to monitor biodiversity, in particular using bioacoustic and ecoacoustic approaches.
GitHub Profile | CV | Media
Good practice guidelines for long-term ecoacoustic monitoring in the UK
08/11/2024 - Digital Dimensions of Nature Recovery
04/10/2024 - Soundings: The River
11/07/2024 - Ecoacoustic Congress
Some thoughts on:
The default behaviour of functions, APIs, applications, etc is often specified or designed to be ‘sane’ - but does this actually mean? Use the SANE default acronym.
The default options should give usable and useful output for the majority of use cases. Little-used functionality is for non-default behaviours.
Align default values both internally and externally. All functions in a package should have consistent and compatible default values. If there is consistency in prevailing usage externally, follow it.
The default options should be neat and tidy. This applies whether the goal is a visualisation, data, a composition of functions, etc.
Many disciplines have expected norms. If your code reflects these disciplines then use the expected norms. Follow the principle of least surprise.