@khinsen Thanks for your encouragement! Whereas I'd at first thought of Maslow's hierarchy as just a basic pattern to follow, I now think there may be a kind of 'isomorphism' here:

Physiologic Needs: any part of the analytic pipeline (from data to results) that isn't fully scripted à la #reproducibleresearch is effectively DEAD.

Safety Needs: scripts not under source control, unstructured analysis data sets (spreadsheets≈crime), and indeed all unnecessarily imperative pipeline elements (e.g., shell scripts instead of makefiles) create an UNSTABLE and UNSAFE environment for analytic work. (Where applicable, safeguarding sensitive data also belongs in this tier.)

Love & Belonging: code reviews, documentation [incl. tests, pace Dijkstra], preregistration, conference presentations, preprints, and peer review at all stages of the work; using and crediting community-contributed software.

Esteem: contributing reusable code, bug reports, bug fixes, etc. to a community of scientific software users; contributing thoroughly reproducible and criticizable analyses in peer review.

Self-Actualization: At this stage, the values achieved have to be one's own, I think. Examples might be achieving technical transcendence by doing the whole project in #CommonLisp, #Guix or (for me) ISO #Prolog 🧘, or formally proving correctness of algorithms. Another example would be that others extend & improve upon your work. Finally, #scicomm could be regarded as a true pinnacle.