I was reading the METR article on how LLM code passes test much more often than it is of mergeable quality. They look at the performance of LLMs doing programming when the success criterion is “passes all tests” and compare it to when the success criterion is “would get approved by the maintainer”. Unsurprisingly, LLM performance is much worse under the more stringent success criterion. Their 50 % success horizon moves from 50 minutes down to 8 minutes.

As part of this they have included figures such as this one:

(Continue reading the full article on the web.)

I read Ian Whitlock’s article on why he can’t quit Magit and it inspired me to share more about Magit from my perspective. This article will focus on rebasing.

Here I have opened the git log, by first opening Magit (which I have bound to the F3 key), and then pressing lL. The first l is the prefix key for dealing with the git log, and the second L is to to view the log for all local branches (and the remote branches they track.)

(Continue reading the full article on the web.)

Teaching an adult to ride a bike is easy. This is how:

1. You hand them a smaller bike so they can comfortably reach the ground.
2. You instruct them to not focus on going in any particular direction, but instead always steer into the fall.

That’s it. That’s the whole trick to cycling. 99 % of the time, the handlebars are only there to keep the bike under your body. 1 % of the time you use the handlebars to upset the balance to initiate a turn.

(Continue reading the full article on the web.)

TL;DR: To use a shell script as a Nix flake check, turn it into a derivation with runCommand. It must

• Create a file named as suggested in the environment variable $out.
• Print the desired “how to fix” information to stdout.
• Exit with status code 1 if the check failed, otherwise 0.

These three steps are not strictly documented anywhere, but are all needed for a shell script to work as a good flake check.

(Continue reading the full article on the web.)

The problem with Qwerty keyboards on small touchscreen devices is that they are designed for ten-finger typing, and we typically only use two thumbs to type. Surely there must be ways input can be optimised for two thumbs beyond the Qwerty keyboard. Obviously, on...