Data source: swyx's twitter data
id | user | created_at | full_text | retweeted_status | quoted_status | place | source | truncated | display_text_range | in_reply_to_status_id | in_reply_to_user_id | in_reply_to_screen_name | geo | coordinates | contributors | is_quote_status | retweet_count | favorite_count | favorited | retweeted | possibly_sensitive | lang | scopes |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1447312313426460672 | 33521530 | 2021-10-10T21:25:19+00:00 | Obsessed by how turning sync into async processes improves UX. Imagine an API call w/ 5 requirements fails bc 2 inputs were invalid. Instead of keeping state on client or duplicating validation, the API call starts a session and you “talk” with it to resolve the invalid inputs. https://twitter.com/swyx/status/1445299225974095877 | 1445299225974095877 | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 279] | 1 | 4 | 82 | 0 | 0 | 0 | en |