Founder @stoplightio (acquired), now building Datanaut. Techstars Austin '15. I talk ui / ux, agentic patterns, company building, and anything coding related.
Finally. It's time. A decade after starting my first company (wow time flies), I'm working on something new!
The new company is Datanaut, and while it's too early to share specifics, I'm excited to work with @scottfaust43 and our small team to re-imagine how we as humans interface with AI, each other, and the treasure trove of data that is fragmented across the apps we use every day.
I'm not much of a sharer, but this go-around I'm committed to building more in public. Expect to see regular posts from me on things like ui / ux design, agentic patterns, running a lean company, and more in the weeds technical stuff - basically a log of the real-world challenges that we're faced with every day as we build Datanaut.
I can't wait to share more. Most importantly, I can't wait to start shipping again π.
Every time i restart my computer and BetterDisplay w this option isn't running, I wonder how folks can live without it. Should be a default option in OSX!
StreamDB - a reactive database in a Durable Stream. Designed for AI apps and agentic session state.
You give it a Standard Schema. You get type-safe, multiplexed data sync into @tan_stack DB.
Links in the π§΅
Messing around with formal Job abstraction w @EffectTS_ and @Cloudflare. Define a job like you define state - `Job.Tag`, implement a handler, then schedule from any actor. Works in memory (for tests) or on CF. Builds on https://t.co/ynfvVGD02A -
Been working on an @EffectTS_ lib to smooth over the experience working with actor patterns, with a specific focus on making it trivial to swap out backing implementation between @Cloudflare durable objects and node/bun/memory. Lot more to it than this, but it's coming along nicely!
@MichaelArnaldi@EffectTS_ hmm crazy, just because it's looking at .ts source in node_modules/effect instead of .ts source in repo cloned somewhere on disk? tbf we JUST made this change to try using node modules instead of on disk clone, so it's fresh - will def monitor to see how it does
love that @EffectTS_ ships the ts source with the npm distribution - more libraries should do this. really helps llm's out.. don't need to clone the repo and point them at it if they can just look in node_modules
ah true on the tests, maybe those could be shipped too :). yes increases size on disk but meh, might be worthwhile tradeoff. re de-optimising the model, have you found any degradation if you encourage llm to search source in node modules for specific libs? In our agents file I just instruct it to use node modules for a few key libs we use like effect, that do indeed ship source. It doesn't seem to get confused and try to use node modules for other libs that aren't mentioned. (this is w opus, haven't tried other models)
Been working on an @EffectTS_ lib to smooth over the experience working with actor patterns, with a specific focus on making it trivial to swap out backing implementation between @Cloudflare durable objects and node/bun/memory. Lot more to it than this, but it's coming along nicely!
Very excited about the @EffectTS_ v4 beta! Haven't seen much mentioned about this and curious if there's any guidance on what to expect wrt tsc type check perf, and stack traces / debuggability dx. Similar characteristics between v3 and v4, improvements, not sure yet?
@audibledata@makisuo@EffectTS_ Ah for some reason I thought the opposite and that things were being consolidated around the effect.service pattern - is there anywhere we could reason more about this? (Discord, gh issue, etc?)
For Christmas I'd like an e2e architecture that:
1. uses @EffectTS_ as much as possible AND...
2. with actor based backend that makes it easy to swap concrete impl from CF to node, with incredible DX ala @rivet_dev AND..
3. with a thin RPC layer for logic that is not owned by actors, and an incredible client<->server DX ala orpc AND..
4. an easy way to expose some of those RPC procedures over a public api ala ORPC openapi integration
Is that too much to ask? ππ
@NathanFlurry@EffectTS_@rivet_dev > the RPC lives on the stateless HTTP layer
Exactly this - although we could probably re-arrange things so that everything is backed by an actor, just not how we're setup atm.
> our native http/websocket support got a huge upgrade recently
Neat I'll check it out!