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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1452046180683161609 | 33521530 | 2021-10-23T22:56:01+00:00 | it worries me that there’s an uncritical acceptance of @Reactjs conclusions without examining if those assumptions apply to you. React is verbose React is successful Must be verbose to be successful Here’s my attempt to articulate more timeless lessons than “2 way binding bad”: https://twitter.com/swyx/status/1383516418205835264 | 1383516418205835264 | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 280] | 1 | 2 | 49 | 0 | 0 | 0 | en | |||||||||
| 1470775386611011590 | 96383 | 2021-12-14T15:19:12+00:00 | Has anyone wrote a blog post detailing the history of using Utility Classes when authoring CSS? Interested in reading more about the origin story (*looks in @jay_hoffmann’s general direction*) | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 193] | 0 | 2 | 49 | 0 | 0 | en | |||||||||||
| 1475112373283598346 | 33521530 | 2021-12-26T14:32:50+00:00 | For those who understand optionality, there's also an implicit life career strategy involved here: 1. go for high luck careers first to try your luck 2. try a few high talent careers to discover if you have it 3. fall back to high hard work careers as they're available to anyone | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 280] | 1475105975518765063 | 33521530 | swyx | 0 | 2 | 49 | 0 | 0 | en |