Have been baking this in as well, as my agents run into problems executing goals against my MCP server
I'm now building an "improvements" feature into all of my personal vibecoded applications: a freeform text input that's hooked up to an agent that yolo implements whatever is submitted.
It's an interesting experience -- the activation energy barrier to sanding any rough edge or implementing any new feature becomes extremely low. Someone else who uses one of the applications I created has already implemented 150 improvements over the course of a few days. This pattern feels like a new kind of tool -- liquid software? -- and every application that doesn't have this feature now has a slightly rigid and anachronistic flavor. Why can't I just tell it how I want it to be different?
Now, it's not obvious to me how this pattern can or should scale. Does it become unmaintainable after a while? (Maybe model intelligence improvement outstrips my feature appetite such that it's fine?) How does collaborative software work in this model? Can software designed this way be secure and reliable?
Whatever the larger questions about broader deployment, it definitely works great in a personal context. It reminds me a little of the visions of Lisp/Lisp machines, Smalltalk, and HyperCard -- systems that the user can take control of and modify. Those visions never quite worked, though: the vast majority of software today is not end-user modifiable in any useful way. So, while this "liquid" affordance is a very small touch, the way it changes one's relation to the software feels a bit transgressive and empowering in a Lickliderian and Engelbartian way.
Michael? retweeted
For everyone reinventing the factory, @AMRwelding is reinventing the industrial robots that go in them
important for all to note:
1 - venture returns are predicated on speed + scale
2 - reinventing a factory for speed + scale IS NOT "i need a factory to make x"
3 - venture equity is the only thing you can use to reinvent a factory
4 - reinvent it, then scale it with equity + debt
5 - scaling laws here far surpass most software companies especially on longer timelines, enormous cash flows and growth potential
Thinking about getting metal legs… it’s a risky operation but I think it’ll be worth it.
a couple weeks ago I posted about how bone grows into titanium implants because cells can't find the boundary
turns out there's a catch engineers have been trying to solve for years:
titanium is too stiff (~110 GPa vs spongy bone's 0.02–3.7 GPa)
so the metal takes all the load, and the real bone around it actually weakens because physics says "why maintain structure that isn't carrying stress?" (stress shielding)
enter selective laser melted Zn-1Mg-0.1Sr gyroid scaffolds:
→ mathematically generated TPMS gyroid lattice (70% porous, 550 μm pores)
→ elastic modulus tuned right down to 2.3 GPa so it flexes like real cancellous bone
→ alloying zinc with 1% Mg + 0.1% Sr precipitates Mg2Zn11 & SrZn13 intermetallics, more than doubling strength over pure zinc (33.7 MPa)
→ degrades at 0.36 mm/year with zero hydrogen gas pockets
and the wildest part
as it dissolves, it turns its own surface into calcium-phosphate & zinc-phosphate minerals while feeding Zn2+ and Sr2+ ions that make bone-forming cells grow faster
titanium tricks the skeleton into adopting permanent metal
this thing holds the load, feeds the bone to rebuild itself, and vanishes when the job is done.
radical engineering.
We’re gonna need to account for people who are more output productive able to put their community on their backs, legislatively.
Michael? retweeted
I don't want flying cars.
I want clean water.
I want a stable climate.
I want bees to survive.
Damn I’ve stopped building UIs in favor of MCP tools.
Still probably need some UIs though, but maybe only in dynamic forms and data displays via agent chat.
Might just be something the core harness will handle by default based on the situation though.
Ask your agents to render large data set charts using canvas instead of SVG.
Instant performance boost.
