Longer functions contain more code, and the more code developers write the more mistakes they are likely to make.
But wait, the evidence shows that most reported faults occur in short functions.
This is true, at least in Java. It is also true that most of a Java program’s code appears in short methods (in C 50% of the code is contained in functions containing 114 or fewer lines, while in Java 50% of code is contained in methods containing 4 or fewer lines). It is to be expected that most reported faults appear in short functions. — Impact of function size on number of reported faults

TIL that Helm development is now stalled (via Bastien Guerry). I’m using Ivy from a while ago now, but my heart goes out to helm’s advanced users, like Manuel Uberti. #emacs

From Rust to TypeScript. #rust

fastmac: Get a MacOS or Linux shell, for free, in around 2 minutes.

Asynchronously Opening and Closing Files in Asyncio. #clang #python

  Gary Peacock, Jack DeJohnette & Keith Jarrett, My Foolish Heart.

Only write necessary tests — specifically, tests whose estimated value is greater than their estimated cost. This is a hard judgement call, of course, but it does mean that at least some of the time you should be saying “it’s not worth it”. — Test smarter, not harder

Modify and aggregate dataframes in Chez Scheme. #scheme

We all know it’s tricky to have a rational discussion about a religion. Non-Lispers will be able to read this without getting their feathers ruffled. Some Lispers aren’t too far gone, so let’s assume we’re talking to them, and take a look at some of Lisp’s problems that make it flat-out unacceptable. At least for LISP, you know, the idealized one. — Lisp is Not an Acceptable Lisp

OMG! My Doom startup time just has just been reduced from 4s to less than 1.5s after I removed the only require instruction I add in my various Elisp files. #emacs

Doom loaded 298 packages across 55 modules in 1.492s.