Matt
308 posts


@cursor_ai coding with composer is uncomparable to any other model, super excited to give it another shot
English

@nicoalbanese10 Building itself in the sense of creating features autonomously or following a PRD-like doc ?
English

@jarredsumner wow very curious about this since setting up windows tasks is still a mess
English

This is the main point why Elysia exists
Not performance, not fancy stuffs
This problem is very real and I learnt it a hard way
Type signature from your actual code IS the documentation not the other way around
We spent ~3 years to perfect this
boris@boristane
docs have no business being the contract between services that's what types are for do this and your coding agent will love you new blog: ship types, not docs shiptypes.com
English

Just ecountered the trickiest "bug" on @tan_stack table + react compiler where console log were the reason why my table was working and removing them was the reason it would break down lol
English

@mattpocockuk how to handle errors gracefully would be nice, but maybe out of scope for typescript
English

Everyone's been asking me to make some kind of TypeScript skill.
It won't be a "TypeScript Best Practices" skill, because I think skills are best used for a purpose, like:
- Migrating from JS to TS
- Fixing spaghetti types
- Improving TS perf
- Extracting types from libraries
What else would you want from this skill/set of skills?
English

@gao_jude I feel like we need to decouple the "what to load in context" with the model that does the job itself
True it may get expensive to actually know what to load, but imo a model like composer can do this in 5 seconds quite accurately, and then you feed to opus the right context
English










