←back to thread

The Claude Code Framework Wars

(shmck.substack.com)
125 points ShMcK | 3 comments | 07 Sep 25 04:05 UTC | HN request time: 0.001s | source
Show context
troupo ◴[07 Sep 25 09:00 UTC] No.45156574[source]▶
> a set of rules, roles, and workflows that make its output predictable and valuable.

Let me stop you right there. Are you seriously talking about predictable when talking about a non-deterministic black box over which you have no control?

replies(6): >>45156592 #>>45156630 #>>45156764 #>>45156773 #>>45158223 #>>45159030 #
dist-epoch ◴[07 Sep 25 09:42 UTC] No.45156773[source]▶
Non-deterministic does not mean not-predictable.

Quantum mechanics is non-deterministic, yet you can predict the motion of objects with exquisite precision.

All these "non-deterministic boxes" will give the same answer to the question "What is the capital of France"

replies(1): >>45156811 #
1. sublinear ◴[07 Sep 25 09:51 UTC] No.45156811[source]▶
Yes, but the "exquisite precision" comes from the deterministic parts of physics.
replies(1): >>45157258 #
2. baq ◴[07 Sep 25 11:28 UTC] No.45157258[source]▶
Nah. The only thing we can establish precisely at the lowest levels is probability. We can and do engineer systems to maximize probabilities of desired outcomes and minimize probabilities of undesirable ones.

Frankly I don’t understand how software engineers (not coders mind you) can have issues with non deterministic tools while browsing the web on a network which can stop working anytime for any reason.

replies(1): >>45158144 #
3. lbreakjai ◴[07 Sep 25 13:51 UTC] No.45158144[source]▶
Because the failure modes are deterministic. An API can be down, which you can easily plan for, but if it's up and returning a 200, you can reasonably expect it to return what it's supposed to.