
co-founder @herd_eco, Solana/NEAR eco veteran, prev @Dune @Clutter @Video_Amp
🇺🇸
Joined December 2008
- Tweets8.3K
- Following2.3K
- Followers1.2K
- Likes30.8K
Our years of background in crypto data informed the design of Trails
Bottom up, from contract primitives (functions, events, constants, etc) to our Explorer (search, understand) to Trails (app layer)
So bullish on @andrewhong5297 and @herd_eco.
Starting from an LLM, without building the primitives / structures to understand where the LLM is failing, is futile.
@herd_eco trails solve for this gap as do @glider__'s building blocks
Ahead of the curve. There's a reason we're both building this way.
3
16
3,670
Replying to @armaniferrante @Backpack
Congrats man, it's awesome to have seen you grind this product out over half a decade now. Wow
1
41
Ya imagine fading @bunjavascript when this is one of the devs
1
99
Replying to @devinjameson
Congrats, for what it's worth the next project my company is building will be using Foldkit! Great to see you go full time 🙂
1
1
49
Edward retweeted
signal is a great word for it. Recently I encouraged folks to stop thinking in terms of "loops" and more in terms of:
"forward pressure" - what causes work to start (crashes, bugs reports, performance issues, +100 things)
and
"backpressure" - how does an agent hill climb against an outcome (linters, tests, ai review/risk judge, canaries, feature flags, +100 things)
looping these toward a desired state rather than an outcome / artifact is a powerful mental model - forward pressure increases autonomy in what gets attention, backpressure increases autonomy in getting to a super high-quality solution
9 months ago, loops like ralph were primarily used to go from point A to point B in terms of functionality, but this is just one degenerate case of a more generic control loop:
- read desired state (e.g. no open bugs, or DB perf above X metric, OR "feature Y shipped", OR "all linter warnings resolved or explicity ignored")
- read state of the world (query systems, run linters, etc)
- decide if anything needs to be done (compare to policy / desired state)
(optional: approve decision)
- do the thing (code change, infra change, docs change, process change)
(optional: approval action)
- repeat
shouts out @0xblacklight for the original framing here at AIE back in june. same logic works for evolving the control loop itself
Replying to @joelhooks
Does Ratstack work with Alchemy Domains? I have been meaning to try pointing this at a codebase I have been working on
1
183




