You can put Durable Objects behind your Tailscale tailnet.
It gets its own 100.x address, dial into private machines and also act as an exit node or subnet router.
https://t.co/wuEzjYKQhZ
Will be shipping a computer use for iphones very soon on MIT licence. 2.1ms on typing without any extra hardware, iphone mirroring, airplay, crap. Cant wait to share ;)
One tip to improve your grilling
Instead of talking about the 'what', try explaining more of the 'why'.
BAD: "I want to build an analytics panel for admins with graphs and filters"
GOOD: "Admins can't currently see an overview of the important data in the app"
If you start by explaining your proposed solution, the agent will stick to it. It'll assume all the important stuff is settled, and just grill you on implementation.
But if you describe the problem, you'll give the agent license to be more creative.
You'll end up with a much deeper, better conversation.
@kitlangton Hahah yes, I spend a lot of time designing a pi-durable plugin for my personal t3 Code competitor and getting this stable and fast is a nightmare π
Iβm making a programming language called blood.
Faster than rust, a powerful type system, all the power of effect systems, metaprogramming, zero-cost worktrees, semantic merging, sqlite-stored content-addressable code.
Psychosis? Hopefully not.
https://t.co/PZf55rf8uZ
@kentcdodds Ohhhh, the tagline is something I wanted to build for months now but struggled with the exact shape and feature amount ! π I'm interested now!
We need to reconsider our priors on code readability.
Humans, compared to agents, are pretty slow at understanding large quantities of text. So in the old days, readability was important so the human could efficiently grok what was going on.
So readability now comes down to:
1. Can a human, if needed, jump in and understand the code
2. Does the code use the same domain language as the human describing the code?
1 helps with observability and the occasional spot checks you need to do on important PR's. 2 helps the agent translate the words you use into code changes.
In other words, readability is now a nicety, not a necessity.
The way agents 'read' code is different - good agents are all about gathering data about how the code works. They'll prod around with it, execute parts of it.
So 'readability' to agents really means 'verifiability'. How easy it is to mess about with that code to see it working.
Let's take this scenario:
- You have a huge module in your codebase that uses all sorts of complex performance tricks
- It has 100% test coverage
A talented human would need an hour or two to get comfortable working in that module.
An agent needs zero time. They verify it with the tests, poke about a bit, and they're good to go.
The takeaways:
- When judging a module (or a codebase), don't think about how easy the code is to read
- Instead, think about how easy it is to verify
- Design your codebase so modules can be tested and verified independently
- Feel free to sacrifice a bit of readability for performance
- Cyclomatic complexity and function size don't matter to agents
the /statechart skill in pstack v0.15.36 is now stable and ready for use! it's best combined with /create-formal-verification-skill to abstractly model state machines and distributed systems to find bugs.
the skill contains a mini tlc compiler that parses, lowers to a small IR, and has a backend that outputs mmd syntax. if you want you can also ask your agent to create charts in whatever style you like, the skills tells it to use https://t.co/bbZicR5ePc which is very themeable so you can make blueprints, hand drawn encyclopedia illustrations or whatever you like
here's a chart of the /statechart skill and 2 real bugs i just found. try it out and let me know what you think!
people of pi (durable). i did a round of performance optimizations in pi-durable.
quick primer. every step of an agent run is saved to a db before the agent moves on. 1 save = 1 commit. thats what makes it durable, crash mid run, resume from the last commit. ~12 commits per run
This is Pele, my new rendering library for diagrams and charts, compatible with the latest Mermaid syntax.
- 100-500Γ faster than mermaid.js
- 6Γ smaller bundle
- No dependencies
- Easy to theme
- Responsive to device width
In pursuit of making Obsidian insanely fast and cohesively designed, I always found the Mermaid library to be too big, too slow, and too hard to theme. Pele will be the new renderer in the next version of Obsidian, but you can start using it now.
Pele [ΛpΙlΙ] is named after the goddess of volcanoes and fire. It's open source under the MIT license. Try the playground!
@theo@FrancoE114696@davis7 I also thought about forking and implementing iroh for connections, but this is even more annoying to maintain at the speed of t3code