cooper corbett

Building @mobiuslegal the AI platform for legal work | Co-founder & CTO @tiltlegal

[Cory House @housecor]

Controversial opinion in my talk yesterday:

Editor doesn't matter anymore.

It's just a diff viewer.

[cooper corbett @flooperflorbett]

@schickling @MichaelArnaldi @devinjameson please do this 🙏

[cooper corbett @flooperflorbett]

@RhysSullivan how’s your hot honey game

[cooper corbett @flooperflorbett]

@MichaelArnaldi @samgoodwin89 is there a michael arnaldi lint rule I can install ???

[cooper corbett @flooperflorbett]

painful mistake adopting @EffectTS_ that we've finally unpicked

always start with a managed runtime and build up from there

avoids odd runtime bugs, layer duplication, easier flushing and simpler interop with vanilla ts code

@SandroMaglione was right
https://t.co/tGjEx6TB64

[cooper corbett @flooperflorbett]

@levelsio this is a niche joke

east malvern vs malvern east

its also very affluent and protective over the boundary of what can be considered 'malvern' against other suburbs

[cooper corbett @flooperflorbett]

@n_haberkamp @0xblacklight this is the way

it interops nicely with existing ts code, so you can start with a single function, feature or service and build out from there

starting with services > utils imo because that's where effect really shines and you get a taste of typed errors + dependency injection

[cooper corbett @flooperflorbett]

@0xblacklight @MichaelArnaldi FYI for those out there: @RhysSullivan’s effect client wrapper skill is really handy for wrapping vendor api’s

https://t.co/D5v2DJ3yu5

[cooper corbett @flooperflorbett]

@RhysSullivan interested in your findings with MCP elicitation support

who does it the best currently?

[cooper corbett @flooperflorbett]

@RhysSullivan @dillon_mulroy @kr0der I pass a runtime.client.ts and runtime.server.ts through the loader context so Tanstack can code split

server runtime swaps the fetch layer to skip the network hop and call the http api handlers directly

not super clean tho and still needs lots of decoding on the edges

[cooper corbett @flooperflorbett]

@RhysSullivan @dillon_mulroy @kr0der it looks like you’re doing all the data fetching client side in the atoms right?

the difficulties I’ve found are when you want to use the route’s loader or beforeLoad functions, and then need to manage client/server and effect/tanstack boundaries

[cooper corbett @flooperflorbett]

@RhysSullivan @dillon_mulroy @kr0der what’s been your approach for bridging client and server with tanstack start + effect ??

I’ve settled on mounting a rpc/api catchall with an isomorphic effect client

but there’s not much prior art online so I worry I’m missing a trick

[cooper corbett @flooperflorbett]

@RhysSullivan effect v4 migration

was very much a rinse and repeat operation where codex could pick the next failing package in the monorepo and migrate, type check, test and repeat for 9 hrs

[cooper corbett @flooperflorbett]

@samgoodwin89 speedrunning my effect v4 migration so I can start using this

so many ideas

IaC not just for trad infra but for posthog, notion, attio, workos, featurebase, resend etc

you can standup whole product / gtm stacks alongside app infra

[cooper corbett @flooperflorbett]

@samgoodwin89 @yacinehmito @turborepo useful here too to cache test outputs across surfaces and handle re-running when deps change

so if the tests are run locally, in codex, in CI their cached results are re-used everywhere else

it operates at the package-level though so maybe too coarse-grained

[cooper corbett @flooperflorbett]

@EffectTS_ not bad

[cooper corbett @flooperflorbett]

codex /goal migrate to @EffectTS_ v4

across a >100 package monorepo here's hoping its that easy

[cooper corbett @flooperflorbett]

@EffectTS_ progress update

[cooper corbett @flooperflorbett]

@zachtratar @Replit maybe replit can do this as well with the mcp

it’s just very convenient in codex

[cooper corbett @flooperflorbett]

@zachtratar @Replit both the codex native Notion plugin and raw via the Notion API for trickier updates

so the loop is: codex builds new feature, then takes screenshots and writes content, then pushes this into a Notion marketing db and help docs db (via plugin + api)