At various times in my life I have released code into the wild, usually on purpose. Sometimes that code is reused by other people, often unpredictably. Case in point: the most widely-used code I have ever written appears in Appendix C to an obscure paper on the computation of first passage to absorbtion times for Weiner diffusion processes. The original manuscript is here and you need to scroll down to page 19 to find it. The code is written in MATLAB syntax and – just to make things worse – there’s a bug in code. If you take the code at face value it simply doesn’t work. Nevertheless, some versions of this code have found their way into an astonishing range of scientific software tools. This one silly little snippet, barely more than a github gist, turns out to be the most contagiously viral bit of code I’ve ever written. But it doesn’t have a github repo, it doesn’t have a website, and there’s no mechanism to invoke it directly. It just happened to be useful, and people used it. With that in mind, here is a incomplete and idiosyncratic list of some things I’ve done with code. Some of it is good, some of it isn’t. Life is like that.

sessioncheck
Simple tools for checking the state of the R session. Very early-stage package (not on CRAN), intended as a drop-in replacement for the heuristic method of using rm()
to clear the global environment at the top of a script; aimed at intermediate-level R users that may not be ready for advanced session management tools

emaxnls
Inspired by the BayesERtools and rstanemax packages I’ve worked on with Kenta Yoshida, I started thinking about what a lightweight frequentist (yes, frequentist. sue me) tool for Emax regression in R would look like. It would be an act of utter madness to use this package in its current form, but I love the idea enough that I’m listing it on this page anyway

quartose
Syntactic sugar for quarto. An early-stage package providing some tools for working with quarto programmatically. It was originally a personal-use package, but people have expressed some interest in using it so I’ve now sent it to CRAN. I like this one enough that I intend to maintain it properly, but I suspect development will be slow given life constraints.

calendario
A personal package I use to help me manage my workload. It’s quirky, horrifically buggy, and unashamedly hyperfocused on what I need. I’m going through the motions of building a proper test suite, writing real documentation, etc, but I see no need to send it to CRAN. The last thing I want is other people trying to use this one.

lsr
The first R package I ever wrote, designed to suport a statistics textbook that I’m no longer in a position to maintain. The code in this package is poorly written and I’m a little embarrassed by it, but surprisingly it still seems to work as intended. So that’s something.