@dan
бессмертная сестра хо
🌉 bridged from 🦋 danabra.mov, follow @bsky.brid.gy to interact
Relays (1)
- wss://relay.ditto.pub – read & write
Recent Notes
"but where are all the bluesky instances?"
i've heard this so many times that i wrote an explainer
There Are No Instances in atpr...
i've heard this so many times that i wrote an explainer
There Are No Instances in atpr...
1
i think the distinction is between treating it like a genie vs treating it like a horse
uh yeah though if we have to have a new term, i’d prefer it to be short
i think to use llms well today, you kind of have to “navigate” them. eg if you see them going by default route, you can throw in a reference, ask a more pointed question, connect something unexpected. it doesn’t always work but sometimes this can shift it into being a lot more useful
things like claude let you navigate word spaces, but you never see where in the space you are. not that it’s possible to visualize anyway. but i think it’s a problem because you don’t know what other word spaces are out there, and what words let you shift out to them
claude conversation trick i like: tell it to take a step back, think a bit harder, and both be more specific and to zoom out a bit.
it kind of shakes it out of the “middle” conversation, and the new edges give more ground to riff on
it kind of shakes it out of the “middle” conversation, and the new edges give more ground to riff on
when i use it i dont think in terms of who wrote a component etc (on solo projects it’s just me). its more that im free to either wear a developer hat (add new data access anywhere) or a designer hat (want to make loading states more granular or more coarse) and they dont influence each other
like the actual api you’re arguing against is
<loading fallback=…>
…
</loading>
it’s like… a perfect api for this. if this was in html we’d treat it as obvious. but because it’s react we have to fight about it
<loading fallback=…>
…
</loading>
it’s like… a perfect api for this. if this was in html we’d treat it as obvious. but because it’s react we have to fight about it
suspense is a thing that lets me say: here’s the loading state for everything inside this box. i don’t care what we’re waiting for (code, css, data access, etc), just show this skeleton if something within is blocking
isn’t it a meme that everyone has adhd these days. but somehow there’s zero representation in system settings. this should be a systems thing and not rely on third party apps. or going modal like alerts should be available to apps (but maybe that’s too much power so again has to be system?)
i’ve kind of given up hoping but it would be nice if apple did some kind of neurodiversity-friendly options for ios, similar to other accessibility settings. turning every calendar into a literal alarm you have to dismiss or snooze would be near the top of my list
like yeah sure you hate it because it won and then a generation grew up who never wrote imperative view model syncing manually. and yes sure it’s weirdly fp. and yes biggest sin of all, it’s effortlessly composable which unleashed a proliferation of componentized junk. components were still worth it