creative pronounce poseur @ Frincle Co.

Joined November 2020
77 Photos and videos
Pinned Tweet
just open-sourced verrex. my take on a frontend framework built on @EffectTS_. the view tree carries Effect's E/R channels to the root, so forgetting to provide a service Layer is a compile-time error that names the missing service. jsx syntax fine-grained reactivity. demo → m9tdev.github.io/verrex source → github.com/m9tdev/verrex
7
1
75
7,255
Mathieu retweeted
Jun 11
or choose to only handle _some_ errors and pass the residual up the tree
1
4
121
just open-sourced verrex. my take on a frontend framework built on @EffectTS_. the view tree carries Effect's E/R channels to the root, so forgetting to provide a service Layer is a compile-time error that names the missing service. jsx syntax fine-grained reactivity. demo → m9tdev.github.io/verrex source → github.com/m9tdev/verrex
7
1
75
7,255
Jun 11
also Async can now delegate the Error channel to the parent component, but you have to handle it _somewhere_ in the tree
1
1
1
122
Jun 11
or choose to only handle _some_ errors and pass the residual up the tree
1
4
121
Mathieu retweeted
Jun 11
also Async can now delegate the Error channel to the parent component, but you have to handle it _somewhere_ in the tree
1
1
1
122
Mathieu retweeted
Jun 11
added some sugar to reduce boiler plate
1
1
2
129
Mathieu retweeted
Jun 11
just added an error boundary based on Effect.catchCause and Effect.catchTags
2
1
1
392
claude fable saying "the codebase is in unusually good shape" about the codebase i've generated with claude opus managing sub agents:
41
Mathieu retweeted
As an EU citizen, I watched the entire #WWDC2026 keynote just to find out in the last 2 minutes that most of it isn't coming to the EU.
110
115
2,925
135,725
Mathieu retweeted
twitter's best worst quality is that it forces all takes into an extreme you're either a tokenmaxxing inferencel looping your agents or you're a promptchud the truth lies somewhere in between you absolutely should have agents that can reproduce problems in your products, look for optimizations, automatically open PRs on issues software has never been perfect, even before AI bugs still made it to production, the more of these you can catch and can fix automatically the better at the same time, the underlying engineering still does matter - i just spent 3 days fixing some bad product design and architecture that i originally tried to defer to agents to implement if i wasn't looking at the code, or i was just trusting loops to fix it, my product would be stunted in quality because i would've just kept digging myself into a worse path anyways, setup your loops but prompting your agents is also fine - get the balance
Here’s your monthly reminder that you shouldn’t be prompting coding agents anymore. You should be designing loops that prompt your agents.
51
32
699
58,076
May 22
last year i tried to build an @EffectTS_ native frontend framework but failed. after watching @devinjameson's FoldKit yesterday i wanted to try again! code example below
4
18
1,194
May 26

May 26
added a ts plugin based on volar to my @EffectTS_ native frontend framework. now i have correct types, go-to-definition/list-references and highlighting!
51
May 26
added a ts plugin based on volar to my @EffectTS_ native frontend framework. now i have correct types, go-to-definition/list-references and highlighting!
103
May 22
not much experience with effect-atom yet, so no idea if i'm doing it right 😀
1
73
May 22
still have to create typescript language server support, so the typed _do_ work, but you can't see them in my editor's typehint yet
68
May 20
first time i see him and think wow he’s old
May 20
.@JeffBezos on doomers and AI-related layoffs: “The reason people think that is because all these smart people keep saying that.” “Those people are wrong.” “It’s going to elevate all of these people.”
56
May 20
let’s see how far we come
1
23