Back

@clacke I've got it working semi-automatically on my local machine, but I've had problems getting it to work on the 'bot.

I'll put it on my queue of things to look at sooner rather than later.

Do you have a specific discussion I can use for local testing?

I'm guessing this one:

https://mathstodon.xyz/statuses/111124890888971530

@clacke (And no, I don't have any unit tests ... it's still all an experimental hack.)

"Beware of bugs in the above code; I have only proved it correct, not tried it."

-- Donald Knuth, 1977 memo "Notes on the van Emde Boas construction of priority deques: An instructive use of recursion"

www-cs-faculty.stanford.edu/~k…

@clacke I used to work in soft-realtime safety-critical software, so this was a well-known and well-worn clip.

We had to balance formal reasoning, semi-formal reasoning, loose arguments, and careful testing, and it was surprisingly interesting and satisfying.

But in those cases we knew in advance what we were trying to achieve, and specifying that formally, or semi-formally, was part of the job.

In this case I've hacked together something to see if it might be useful, and it's grown into a thing that people use.

Software, eh?

(Also, I'm interacting with reverse engineered interfaces to software I neither understand nor control. So ... yeah. Fun.)

@clacke I think that should go in my toot rotation. I have a script which every day takes the next item off a list, toots it, then puts it back on the bottom.

I'll add that. Do you want to be credited? If so, how?

Example:

"My number one advice to my younger self: Your prototype *will* be put into production"
-- Paraphrased from https://mathstodon.xyz/@clacke@libranet.de/111131868536836880

@clacke Cheers!

@clacke Thank you.

After a few weeks of trying it randomly I'll announce it properly.

Thanks for the motivation to get it done. It wasn't so bad ... the other options will be harder.