I don’t know if you’re the right kind of engineer or not, but in pseudocode (hope pre works …):

Here's what the one-line split-test looks like in pseudocode:

In pseudocode, they wanted to build the following construct:

In pseudocode, they wanted to build the following construct:

Sometimes pseudocode is the best way to get something across.

For now, I'm calling it pseudo-story by analogy with pseudocode.

But algorithms not in code or pseudocode but described are more valuable.

I see that the current implementation probably uses TODOLIST.id_task_pk INT11 for ordering, so I'd imagine the least amount of effort would be something like the following pseudocode:

Algorithms can be expressed in many kinds of notation, including natural languages, pseudocode, flowcharts, and programming languages.

Algorithms not in code or pseudocode but described are more valuable, so we're not giving McIntyre tꦿhe ✤code.