I'm going to make a prediction that I will reveal on or before the Ides of March 2028, regardless of how it turns out:
sha256(prediction)=31514b7a01f2e239a78aca83d20e6ef32752308342415233fbd0df18c4a58d9e
The TanStack team is on fire lately and I’m just so excited about the energy. What can I and the rest of the team do this week to make your software and you more effective? More confident? Faster? Lighter?
We need an adapted version of Doherty's Threshold:
How long is a user willing to wait for marginally-extra intelligence?
Or
At what balance of (speed,power) is productivity maximized?
@pathlessknown@X I like it. I can see I steer it with my attention and I can always go “no interested in this post” to steer hard back or just not engage which steers lightly back
If your company takes 32mb and hundreds of requests just to load the login page, you're doing it wrong. Yes, already reported last week, but still shocked that nobody cared enough to fix it. Putting this here as a test to see how long it takes BigCo to fix.
The algo at @X is super responsive: as soon as I engage with some kind of content, it steers For You timeline for that. All I see now are ducks and golden retrievers.