rrook

3 ms·

1.
by rrook 5d ago
Totally agree with the first part of that. The second less so. LLMs are able to maintain a cohesive idea across multiple metaphors, which is basically the same as walking abstractions.
2.
by rrook 5d ago
> The tech industry has accidentally invented the initial stages a completely new kind of mind, based on completely unknown principles, using completely unknown processes that have no parallel in the biological world. This is just false?
3.
by rrook 5d ago
MCP is an incomplete abstraction. It solves things in the right direction, allowing agents to interact with some given system via a controlled ingress. It's a fancy proxy, and by itself doesn't really do much to enable autonomous
4.
by rrook 6d ago
Expressing complex emergent workflows is fairly straightforward given how the workflow engine recurses: - a workflow is a series of steps - a step is one or more tasks that can be done in parallel - a step is complete when all of its tasks
5.
by rrook 8d ago
Narrowly, I think you're spot on. The effort required to understand the machinery around formal verification is a function of the surface area of the thing being formally verified. Specifically, formally verifying the surface area of g
6.
by rrook 9d ago
I think that dissolves the "self driving" distinction, though? The mechanisms for driving the codebase must be present in the codebase itself. Otherwise its just a regular out-of-band development process.
7.
by rrook 9d ago
My bet is that we'll see a second layer of harness emerge, as self-driving codebases become the target. There will be an application facing harness, orthogonal to the agent facing harness. The app harness will represent the software fa
8.
by rrook 9d ago
I agree with you, and am all in on a solution. It has to be part of the language itself: https://hale-lang.org/docs/claims/
9.
by rrook 24d ago
Thanks for that feedback, I'll try to add some more well known examples. In the meantime, maybe the docs have more of the examples you're looking for? https://hale-lang.org/docs/tutorial/job-queue/
10.
What the Hale?(hale-lang.org)
2 points by rrook 24d ago|2 comments
11.
by rrook 1mo ago
Absolutely - it's like, the "current agreed upon version", but indeed it's a point-in-time snapshot/simplification of whatever the thing being modeled actually is.
12.
by rrook 1mo ago
I did RTFA, maybe YOU need to read my question again. I specifically asked about the outcome if the plaintiff didn't do all that petty stuff.
13.
by rrook 1mo ago
This seems like way too caustic of a reaction, OP is correct. If you actually know what you're doing in $language, and you know how $language wants to emit the assembly or whatever, there's no huge advantage to just programming di
14.
by rrook 1mo ago
Some shameless self promo - I'm working on one! https://hale-lang.org/proof/
15.
by rrook 1mo ago
Sure, the domain model isn't an artifact, but software _necessarily_ contains an artifact of the domain model.
16.
by rrook 1mo ago
The domain and delivery/ops context define the constraints, code that gets written ought reflect those constraints, not provide more.
17.
by rrook 1mo ago
I think the reality is that it has to be baked into the language. Here's my real attempt at that - if you model the system in the language, the compiler can reason about the distributed fleet: https://hale-lang.org/proo
18.
by rrook 1mo ago
Does that reading intonate that had the plaintiff chosen a more benign injection, only to prove that an LLM was involved, rather than to alter the outcome, the judge would have looked at the situation differently?
19.
by rrook 2mo ago
Not really pursuing it at this point, but it seems so intuitive that organizational harnesses will converge on like, agent personas that are constructed just-in-time from shared knowledge graphs. https://brained.dev/under-th
20.
by rrook 2mo ago
Language space is hot right now: https://agentlanguages.dev/
21.
by rrook 2mo ago
I've been working on a language that codifies a single abstract _situated_ unit of computation. It sits at the intersect of memory, process placement, callstack, lifetime, and domain graph. Because it's the only unit of structure
22.
by rrook 2mo ago
Would you say that "choreographic programming" is different from an architecturally-aware compiler? https://hale-lang.org/articles/claims-in-hale/
23.
Claim-Driven Development in Hale(hale-lang.org)
6 points by rrook 2mo ago|0 comments
24.
Effects in Hale(hale-lang.org)
3 points by rrook 2mo ago|1 comments
25.
by rrook 2mo ago
Author here! Just landed this feature, happy to answer any questions.
26.
by rrook 2mo ago
given your experience on the topic, i'm curious: do you think that the reason we haven't figured out how to make other parts of formal verification fast is that, in general, programming languages expose each individual machine ope
27.
Show HN: Hale – A Concurrent Systems Language(hale-lang.org)
4 points by rrook 2mo ago|0 comments
28.
by rrook 3mo ago
I've been working like, almost this exact idea! https://github.com/hale-lang/papers/tree/main . The same capacity allocation bound algorithm appears naturally not only in human and llm/agent congnit
29.
by rrook 3mo ago
I think that's where it goes, yes. The ability to model the world internally predates spoken language. We (and other animals) already translate what we _sense_ into that internal model. Language is just another translation; all communi
30.
by rrook 4mo ago
How would we feel about Google providing misleading search results about how to implement search algorithms?

More ›