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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1370513317379280897 | 33521530 | 2021-03-12T23:13:32+00:00 | 🆕 Preemptive Pluralization is (Probably) Not Evil https://www.swyx.io/preemptive-pluralization/ Fully-baking a theory by @r00k on the @artofproductpod, I make the case for a "Premature" Optimization you should consider. TL;DR - Pluralized code is robust to @hillelogram's requirement perturbations! | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 279] | 0 | 50 | 202 | 0 | 0 | 0 | en |