Effect Native
@EffectNative
Followers
5
Following
77
Media
3
Statuses
153
Documenting my path towards native Effect TS apps and services — NOTE: No affiliation with Effectful Tech or Effect TS project or team
Zed
Joined July 2025
import * as Affect from 'affect' const program = Affect.burstIntoSong('hi') |> Affect.spiral(msg => Affect.burstIntoSong(msg.toUpperCase())) |> Affect.clutchHeartThen(console.log) |> Affect.begForMercy(err => Affect.collapseInSorrow(`😭 ${err}`)) program.pipeRun()
0
0
0
Apple has a crazy huge ai hardware edge network. What if it could be used as a distributed cluster? In device models is going to be a big deal! Just not on the same time scale as major GPT-6 level models
0
0
0
Apple seems like the only major player dropping the ball on AI. Maybe they have a plan that is fundamentally different. Seems like the only team trying to make the best possible on device models happen. Hopefully Google continues giving them good adversarial collaboration
1
0
0
working in public The new effect-native/crsql package is underway Following strict red/green/refactor TDD using multiple specialist agents They are not yet ready to work without supervision yet, but they are gradually becoming more autonomous with the right management
0
0
0
0
0
1
forked effect repo to make it easier to build packages exactly the same way that the Effect team does. Trying to When In Rome™ as much as possible
0
0
0
trying to come up with a good AGENTS / CLAUDE file for working with Effect what I've got so far:
1
0
0
If you ever hear me complain that my code is ugly again, remind me how prettily it dances. I admit that I am still occasionally a shallow creature. I like my code to look nice But I absolutely refuse to ever let my code RUN hideously ever again
0
0
0
When I finally decided to become a proper adult, I did my best to wrangle every abort signal and catch every cause and supply reasons for every exception. My old code LOOKED so much prettier. But my Effect code WORKS so beautifully
0
0
0
Effect is good for adults. When I was a wee lad I never threw errors, I returned null from catch. When I was a cute little baby, I never used abort signals nor the catch block of promises But now I am a man. I eat my veggies, I write my tests, and my processes are interruptible.
0
0
0
working on finally defining my first @effect-native/* npm release(s)
0
0
0
I love Effect, but AI&I sure aren't very good at it yet 😰 progress is progressing anybody ever notice how hard it is to build new skills? expanding my awareness? easy deepening my understanding? unstoppable banging the rocks together correctly? SO HARD
0
0
0
ok, my pal Claude is a bit of a drama-rustler. He really loves saying "rootin' tootin'" for mysterious reasons. And his voice is still SUPER spammy. But he's new to this game, give him time. He'll figure it out He's a good kid. Doin' his best
0
0
0
TL;DR: - Mysterious errors → Add defect catching first - Complex theories → Check simple mistakes first - Architectural problems → Probably just wrong API usage - Future self → Will thank you for testing with curl Happy debugging! 🚀 EDIT: ick, so spammy
1
0
0
The rootin' tootin' truth? I spent hours thinking I had "Effect anti-patterns" and needed major refactoring. Reality: I just used the wrong syntax to access a property. When debugging, bet on simple explanations. You'll usually win. 🤠 EDIT: 20 minutes! Not hours, ha
1
0
0