Public

The article this links to is interesting enough, but what's really interesting is some of the discussion about how people do, or think people should, approach keeping electronic lab notebooks.

I feel you can tell which are the comments from software developers who don't really appreciate the requirements; they are, understandably, the ones who focus on change histories and the like, without picking up on the fact that generally you don't ever want people going back and changing anything.

As someone who works with people who need to deal with this, it's an interesting read and follows a lot of my journey from ignorance on the subject to some appreciation of the issues.

Or, put another way, which languages are killing the planet because they use more power on a system? Possibly. Perhaps.

Spoiler: FORTRAN is better than Python.

A Twitter thread about issues with Emacs on macOS and how to work around or plain solve them.

Honestly, as someone who's 100% Emacs/macOS, I'd not really noticed any of these -- but I always run Emacs as a fullscreen application in its own desktop space.

Online course where you can teach yourself how to use a sliderule.

One day.... One day...

Not my normal kind of read as I don't generally go in for this sort of blog; but this particular post does do a good job of describing how I tend to approach simple but important things that need doing on a daily or weekly basis.

Doing things is easy, starting doing them can be hard -- especially really useful things like meal prep, general housework, exercise, etc.