> Try speccing out a flux capacitor. I'll wait.
One way to spec that is presumably something like "X% more efficient than current best-in-class", "made of Y,Z with no exotic materials", "takes no longer than T days to create" and so on.
Anyway, being "anti" spec isn't even wrong because it's just a completely incoherent position. There's always a spec.. including any informal prompt you kick off your agents with. Call it a "structured prompt" if that soothes you and your agents, then let's move on to the interesting part where we decide how much structure is optimal
That seems barely related and settles nothing? Bottom line is simple, saying "you can't spec out something you have no clue how to build" is saying you cannot desire coldness unless you understand how to build a refrigerator. It's just the difference between what and how. If you don't know the difference between implementation and specifications, just try a whole day of answering "what" and "why" questions with "how" answers and see how it goes.
Not an expert, and not sure how but lazy BDD's fit in specifically, but I thought BDD's are already the gold-standard data structures in most model checkers and assumed they were at the limit of possibilities for performance. Can anyone comment whether that's true, whether it means this kind of implementation is already standard in other programming languages for sets/bools? What about infrastructure with fast set operations like redis?
A few hops away, the non-mathematical part of this story is interesting[0] and Conway's related weird world of audio-active decay is another recurring favorite[1]. Both are even more fun with esolangs[2]. I'm sure I've heard audio-encodings of Kolakoski before, but couldn't find any with a quick search
[0] https://en.wikipedia.org/wiki/William_Kolakoski#Personal_sig... [1] https://en.wikipedia.org/wiki/Look-and-say_sequence [2] https://esolangs.org/wiki/Kolakoski_sequence