Hi 👋. I'm an experienced full stack product developer looking for a new project, ~4 days a week (remote) I can build prototypes and experiments, ship production features, plan architecture and lead a tech team More info at context.co.de, and in this thread 🧵

Fable one-shotted this ENTIRE Hogwarts castle, complete with classrooms, the Great Hall, Quidditch pitch, everything

tell me you have 0 customers without telling me

The touchbar was too early and didn't deserve to die

Another major problem, this time in additive combinatorics, has fallen, this time to humans rather than AI, but using methods related to the AI solution to the unit distance conjecture.

"echo": your logged-in tab as an MCP target An agent can drive any browser tab you're already signed into, without ever holding your password. 1. install the Chrome extension 2. open a tab you're signed into (Jira, GitHub, your CRM, anything) 3. click the echo icon 4. paste the MCP URL into Claude/Cursor/etc 5. agent drives that tab via one tool: `echo​run(plan)` • no copied cookies, no API tokens, no headless browser • every step = durable workflow receipt • close the tab = session dead • MIT, deploy to your own @Cloudflare account Demo: echo.coey.dev Source: github.com/acoyfellow/echo

Gave google omni a sketched camera path and asked it to generate drone POV footage.

I think it's the same basic failure mode that lead so many people to cargo cult microservices for their 10,000 MAU products, or to terraform and/or kubernetes their pre-PMF product's architecture. It's fun to make computer go brrr, but it won't make the planes land!

Been limiting my showers to 1 minute to save more water for the data centers.

It's all trade offs of course, but like all trade offs it can be easy to take one side as gospel. I've been there having to apply weird webpack patches to storybook just to fix a bug that needs a newer version of nextjs or whatever

Cerebras is now running Kimi K2.6 – a trillion parameter model – in enterprise trials. At ~1,000 tokens/s, this is the fastest frontier model performance ever measured by Artificial Analysis @ArtificialAnlys.

This reminds me of a designer I worked with who always wanted to "Jony Ive" the ideal paradigm for each bit of UI. Users were confused, features were late, it all got replaced with UI that the users already understood

Unpopular opinion: I don’t care if most web apps look the same. All I care about is whether it does what it says and does it fast. Make it fast. Make the UX obvious. Put the right things in the right place and little to no animations.

We strongly recommend updating your applications (to remove React Server Components)

Ok, I've had enough of this. I'm relieved that I never actually adopted RSC and at this point I'm convinced I never will. I'm now firmly in the camp of "RSC was a bad idea." The problems weren't made up. But this solution is not good.

En azul: El agua fluye hacia el Atlántico, el Mar del Norte o el Báltico. En granate: El agua viaja hacia el Mediterráneo, el Mar Negro o el Caspio. Infografía: Perrin Remonté

Call for founders! Join our "Founder in Residence" program @MistralAI!

Green screen keying, solved at the pixel level. Corridor's neural keyer unmixes edges into true foreground color and linear alpha, EXR out.

This works surprisingly well: • Ask Claude Code to fix a bug • Let it work and figure it out When it finishes, use this prompt: "Knowing everything you know now, delete your fix and implement a better|concise|elegant version." Claude will use the first pass to explore and learn the problem. Sometimes, this will lead to suboptimal code. The second pass will be better because Claude already knows the problem and can write a better solution.