Pinned Tweet
Replying to @danielkauppi
It's this: toast, butter substance (vegan or dairy), peanut butter, sriracha, and brown sugar. Optional side pickle.
aulneau retweeted
Software is having its Industrial Revolution and it’s changing what matters in software frameworks. Today’s frameworks were designed for the crafty carpenter, tomorrow’s are designed for mass manufacturing processes where rigor > conciseness.
Take foldkit vs react/solid, for example. You can argue that foldkit is more verbose or complicated for some use cases compared to the traditional alternatives, but everything doable in react/solid is also doable in foldkit. Everything doable in foldkit is not (or at least not easily or consistently) doable in react/solid because they lack the rigor of command+event state machines with story & scene testing. Getting that back isn’t easy and is a substantial loss for agentic coding.
Before AI, there was the valid argument of picking what humans like best. Humans kinda suck at programming because we are constrained by our skills, taste and (lack of) discipline, so frameworks that worked in this era catered to the lowest common denominator of mass market human developers. While I agree that react/solid are powerful in the hands of humans, that simply doesn’t matter anymore.
What’s best for humans does not necessarily translate to what’s best for agents. Some tasks may indeed be “a bit harder” with foldkit in human terms, but AI is capable of solving all of them in a few minutes, so who cares. Instead of bike-shedding philosophy and taste, just choose the more rigorous (and scalable) option. It costs you nothing and gains you everything.
Effect is another example of this. With AI, now everyone of all skill levels can use advanced programming techniques that are objectively safer and more scalable, but were out of reach for many human programmers. Or didn’t appeal to the stubborn tastes of a particular person.
With humans now out of the way of technology adoption - I think it’s obvious that the following techniques are going to become way more commonplace:
1. State Machines
2. Functional programming
3. Declarative infrastructure
4. Test Driven Development
5. Domain Driven Design
6. Actor Systems
7. Rigorous API schemas
8. Type Safety and Formal Verification
9. Disciplined Operations (monitoring, on-call)
Alchemy is designed to bring these techniques together into a seamless experience for building and deploying applications of massive scale. It is the “rails” and “parts” of the ai software assembly line.
aulneau retweeted
New: domain-driven design for Effect, in alchemy.run/domain.
Translate business requirements directly into working software and integrate into your alchemy infrastructure.
aulneau retweeted
here's detail write up of my pi-based always on agentic software factory centered around effect, alchemy, and celld
my current favorite piece is the "social network" we use for agent to agent comms 😍
So this is like super illegal right? Will Samsung get sued?
hey @simonsarris love the new updates with edit and develop! A few feature requests:
- grid gallery view
- copy and paste adjustments to one or many images
- please store raw images in a different folder
- I sent an email about this, but my pixel 11 no longer has 9/10x zoom
the hyperion cantos is still one of my very favorite book series. highly rec all four books! then read accelerando by charles stross
aulneau retweeted
Decision models could damage Anthropic's business.
You don't need Opus 5.5 when you can instantaneously run hundreds of natural language assertions on agent output...
... at a fraction of the cost.
This approach is being streamlined via Traits.
traits.sh/
Hey @simonsarris, I love nocta, works great on my pixel. Have you thought about making it so we can create custom presets? I want to try and make a ricoh preset 👼 people could also share presets
aulneau retweeted
Hi, I'm Felix. I'm an eng lead working on Claude. I love watching people take flight and do things they never thought possible.
We often describe that as "being more ambitious" when using AI, which is tricky advice to follow. I wrote a tutorial:
felixrieseberg.com/how-to-be…
OpenCode 2.0
anoma.ly/notes/opencode-2-0/
aulneau retweeted
Benefits of the CAFE stack (@Cloudflare + @alchemy_run + @foldkit + @EffectTS_) for building software with coding agents:
1. Agents invent less architecture. They focus on product-level execution within a well-defined architecture. You build faster, with more confidence. You focus on what makes your product unique.
2. Your codebase becomes semantically rich. Intent and meaning are explicit rather than left for future agents to infer. Each new agent spends fewer tokens reconstructing intent.
3. Tests read like executable behavioral specs. Expected behavior is easy to inspect, and both humans and agents can verify implementations against it.
4. Strong conventions result in remarkably legible AI-generated code. Agents do what you expect more often, with less steering. The codebase feels consistent and predictable.
5. Explicitness makes behavior clear. Unexpected magic has fewer places to hide. Diffs are easier to review. Yes, it’s more LoC, but who cares when you’re not writing it by hand?
we specifically avoided using quickjs as our codemode implementation
it brings in webasm complexity + forces worker threads + serialization of values back and forth
if you're involved in implementing something like this check out our codemode package it is way simpler
aulneau retweeted
the assembled lore for idiomatic effect project organization ratstack.sh/lore/structure-e…
aulneau retweeted
[email protected] brings a ton of new stuff, including broad GCP coverage, Neon becomes more than a Database, pluggable secret providers, Prisma ORM, better scheduling primitives for Durable Objects and much more.
alchemy.run/blog/2026-09-29-…
























