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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1395172543565344770 | 33521530 | 2021-05-20T00:20:30+00:00 | 🆕 How to Optimize for Change My first post on the @freeCodeCamp blog in a while! 2 years ago, @dan_abramov told us *why* to optimize for change. Ever since then, I've been exploring the obvious next question: How? https://www.freecodecamp.org/news/how-to-optimize-for-change-software-development/ | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 243] | 0 | 5 | 64 | 0 | 0 | 0 | en |