drmajormccheese

There is a body of knowledge in unit testing, integration testing, static analysis, model checking, formal methods, fuzz testing, … (what other techniques for building assurance in our code have I forgotten). And LLMs can be put to use towards all of these methods. But sure, we just need to think harder to solve all our problems. Velocity of code goes up. Velocity of testing can also go up. It’s just not as fun or glamorous.

And there’s the smoking gun.

I “vibe coded” an iOS app that lets you guess the next number from a curated list of OEIS sequences. The app is called Infinite Numbers. It’s free. No ads. No tracking.

What if you gave the AIs a subscription to Suno to generate the content for their shows.

There are techniques for improving our confidence in our software: unit testing, integration testing, fuzz testing, property-based testing, static analysis, model checking, theorem proving, formal methods, etc. The LLM is not only a tool for generating lines of code. It can also generate lines of testing. The goal is that the tests are easier to audit by the humans than the code.

This is not a database of bunnies

Yes

Fortress didn’t have a total order of operators. Also IIRC operators could be tightly bound or loosely bound based on whitespace.

Yeah. Recently (past half year) GitHub enabled a feature where duplicate comments are automatically edited to be hidden comments. I think it's a continuation of the GitHub feature that allows repository owners to hide a comment. Two caveats: (1) you can't hide a comment using the GitHub API; (2) I haven't tested whether duplicate comments trigger an email notification. Ideally they would not trigger notification.

Type checked state is known as "typestate". A Google search will bring up the typestate paper.

There have been some GPU implementations of the Barnes-Hut algorithm [O(nlogn) n-body problem].