Web & AI Product Engineer

Joined December 2017
68 Photos and videos
Well deserved!, loving this
VoidZero is joining Cloudflare. Our mission stays the same: to make JavaScript developers more productive than ever before. Vite, Vitest, Rolldown, Oxc, and Vite remain MIT-licensed. Evan and the VoidZero team will continue leading them. Cloudflare shares our commitment to open source. Together, we can keep investing in the tooling developers rely on every day, while bringing the Vite ecosystem and Cloudflare’s platform even closer together.
50
devdave retweeted
Send help.
221
51
2,181
404,905
I'd like to opt out please
Out with the old, in with the bold ✨ We gave the Google Workspace icons a sleeker look to meet this new era of helpfulness. Check them out! goo.gle/4diuCsz
1
127
devdave retweeted
New in TanStack Router: more control over dynamic route params. Use params.parse to accept or skip a candidate, with priority for overlapping dynamic params.
19
46
798
118,185
Found myself rethinking products interface last few weeks. 'Agent Accessibility' is a recurring theme, more will come to realize this quickly
Building a product today only testing it via the browser & not via an agent is like developing only for desktop and not checking on a phone during the mobile revolution I’m guilty of this also, it’s a really easy trap to fall into but agents are how people use products now
26
generators in Js never went mainstream Effect going mainstream is changing that Generators are insanely powerful
<LoadingButton /> No `isLoading`. No `useState` in parents. yield your `onClick` handler. stackblitz.com/edit/ericclem…
74
Have mine archived away in google drive
you're never opening this again but you're not deleting it either
74
React is not the Final Framework I repeat, React is not the Final Framework!!! @EffectTS_ @foldkit there has to be a better way, there is a better way, and it will come. AI accelerated poliferation of React wont stop it
been trying out foldkit.dev today, it's really interesting. initial thoughts: - agent really liked it. cursor w/ 5.5 one-shot a bunch of stuff that was super annoying before that i was trying to (keep a persistent music player playing across different pages, share state, load state back from local storage, etc). - it's all effect, which i like. dunno how well it integrates further down, gotta try some more httpapi integration stuff but should be fine w/ httpapi client - seems to handle a bunch of stuff that normally felt really finnicky with getting right with effect, schema stuff, state thing,s blah blah - the dev mode is insanely cool, can replay mesages and everything, super sweet idk probably more to think of later but been enjoying it a lot ty @devinjameson love the direction
2
4
51
7,124
devdave retweeted
/grill-me is my most popular skill ever. I get 5-10 messages a day about how it’s changed people’s workflows for the better But… I’ve stopped using it for code. Here’s the improved version:
94
178
3,157
276,903
Alchemy Effect !!
Generating SDKs from APIs is better done by coding agents now than with tools like Stainless. In the real world, every spec is wrong, incomplete and inconsistent. Someone has to go and patch the spec before you can get good results with a rigid code generator. And Stainless APIs still don't give you the errors! They produce nice looking SDKs, but lack the most critical aspect of APIs - the "unhappy paths", which are usually far more in number than happy paths, and are what makes the difference between a great and a terrible UX. Stainless support many targets, but ask anyone who's used Cloudflare's terraform provider and you'll quickly realize that it's not magic. If the spec sucks, the provider sucks. And most specs suck. Distilled and Alchemy address this with AI. We use coding agents for 100%, so each new SDK we onboard is effectively "hand crafted". AI adapts "manually" to the nuances and weirdness of the spec and API. We share some code, but we don't try and squeeze specs into one code generator. Every time we make one, it becomes useful context for the next one and drives the flywheel. Since we are targeting Effect, we value errors more than the happy path. None of the APIs we've worked with except for AWS have documented their errors in the spec. And AWS still hasn't documented 100% (maybe 80-90% at best). AI patches these missing errors (and categorizes them as retryable, etc.) by interacting with the service and observing its actual behavior. This then feeds into Alchemy which uses AI to generate hand-crafted IaC resources and our Effect abstraction on top. This generation process reverse engineers the API's actual behavior and produces: 1) Effect-native SDKs for every cloud, and 2) IaC Resources for every cloud, 3) Alchemy Bindings for every cloud API.
6
447
Effect ts goldmine
What are some good large open source Effect codebases with established patterns in them? I've got two: - github.com/AnswerOverflow/An… effect v3 - github.com/rhyssullivan/exec… effect v4 They're both decent but wanting to improve the amount of references I can give my agent
1
4
73
13,413
devdave retweeted
What are some good large open source Effect codebases with established patterns in them? I've got two: - github.com/AnswerOverflow/An… effect v3 - github.com/rhyssullivan/exec… effect v4 They're both decent but wanting to improve the amount of references I can give my agent
34
15
438
41,602
"typescript guy" they said, now he's the skill and effect_ts guy huh love what you do man
1. I wanted to create an automatic chapter creator for my videos 2. I did /grill-with-docs with the agent to figure out what I wanted 3. I said 'let's prototype the prompt passed to the agent' not really knowing what to expect 4. It built an entire TUI (in @EffectTS_) for me, pointing at my live data 5. I iterated on the system prompt until it was awesome 6. AFK agent one-shotted it
2
114
Effect pilled, there's no saving me @EffectTS_
2
2
76
3,869
Hottest new stack, agents choice
effect tanstack start cloudflare drizzle has been nice
45
devdave retweeted
I'm now building Executor full time as a startup! The state of tool calling is a mess: - Everyone is using different agents - You have no idea what actions are going to run - Destructive actions are treated the same as normal Executor lets you set up everything once & use it with any agent. You're able to control what tools can be called, require approval on destructive actions, and invite your team to all use them. Under the hood, it's built on codemode to let you add thousands of tools with 0 context bloat. I've been using it for a month so far and it has completely changed how I interact with agents. There's so much to be built here, immediately next up on the roadmap is workspaces, skills, workflows, and generative ui. Everything is being built open source over at github.com/RhysSullivan/exec…, there's a lot more coming on an SDK to embed it into your own agents, a self hostable cloud app, and plugins There's an early beta version over at executor.sh. It's very early on - if you hit any bugs let me know and I'll get them fixed up, excited to share more as I build it!
151
78
1,514
216,100
md mermaid!!!
i am on team markdown
45
And the root of all evil is irrational, checks out
If the number 666 is considered evil , then 25.80697 is the root of all evil!
27
devdave retweeted
progress.34 / 自由に伸びるテキストフィールド
16
38
555
46,580