Profile avatar
subtlegradient.bsky.social
Maker of things that do stuff since the 90’s. Mostly frontend. Previously @coinbase @godaddy @facebook @mootools
63 posts 77 followers 236 following
Regular Contributor
Active Commenter

got so much wacky tech shenanigans waiting in the wings to dump on ya all soon, OSS style it’ll be grand

Shipped the world’s first(?) realtime streaming subscription based react server rerenderer infra for native mobile It’s like next.js app router, but for realtime streaming live views instead of a single fire and forget server render pass dramatically pushing the state of the art forward

expo/fetch doesn’t seem to be able to let go of connections when the server just keeps streaming stuff forever 😰 I’ll try again with react-native-fetch-api

Defensive programming, pit of success style I’m playing with seriously dangerous tech. One screw up and the memory leaks will melt your phone Let’s just assume that we’re going to screw this up somehow So I’m inverting the failure case

low expectations are ALSO all stick and no carrot. When people expect something to be slow, they get confused and upset when it’s too fast. It’s like a video game controller that’s too light, feels cheap and broken. Gotta add a little bit of fake weight to important stuff so that it feels right

high expectations are all stick, zero carrot Nobody is delighted when an app opens fast. We tolerate slow starting apps we love. We loathe slow starting apps we need. Making an app start fast is not a moment to celebrate (as a user). But it is a huge moment to celebrate as a dev team.

crazy how much modern react code looks like the quick and dirty one file prototypes I used to make back in 2006 I miss `with` 🥺

threading the needle between control freaking and a chaos freaking

finally realizing that I’m not really an inventor. I’m an applicator As a super double observer, I can learn and understand anything. Then once I know and understand, there’s rarely anything left to invent. I see the implications and applications. Then do the obvious

published @double-observer/react-client to npm It’s react-client from the react repo with minor tweaks to support React 18 & React 19 + exhaustive TS types

Log debugging for finding the problem. Debugger debugging for solving the problem. Breadth first. Then depth

@egghead.io please let me buy stickers of all your graphics. I love them so much. SO MUCH cc @joelhooks.com

yeah. I’m going to just do it Sometimes ya just gotta do the thing you like to do

Ok, I admit it. I’m building a js framework again It’s RSC for RN with manual bundling of client components Generative native ui in production! I’m probably not going to open source it this time, or maybe 🤔 Only goal is ludicrous product perf. Like 27 out of 10. 11 ain’t enough

Blocking someone should instantly hide their posts

What’s the abstract corollary to the concept of “attention to detail”? Details are sensory. But that’s just half of observation. The other half is indirect abstract implications and relationships If someone is good at that, what is it called?

getting some totally random layout bugs on The New Architecture 😰 Going to have to pause it and focus on real product development for a bit. I’ll try The New Architecture after 77 lands 🥺

I’ve been thinking about building some kind of AI tool kit that works the way my brain works. But @zed.dev is already just so convenient that I’m not feeling that pain anymore.

The biggest problem with generative AI is the generative part. They talk way too much. But I find that I excel in collaboration with them when I spend the majority of my time iterating on a very detailed prompt and regenerating their response over and over again, instead of having a conversation

Most of my hand coding these days is essentially imposing my own aesthetics on code that was generated based on Ludacrisly verbose specs that I wrote up

I used to do most of my programming at runtime. I would do the absolute minimum necessary to “close the loop “that would get something running in an environment where I could interact with it at runtime in a de bugger, and then through design the system interactively in a real environment

I like to start off with Ludacrisly verbose syntax that is impossible to misunderstand We can always get cute and clever with it later or even better never

I love using data structures and interfaces that make it simple and easy and elegant to make random changes later on in such a way that invalid states are unpresentable

the best diffs are red