id,user,user_label,created_at,full_text,retweeted_status,retweeted_status_label,quoted_status,quoted_status_label,place,place_label,source,source_label,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
1442610193846603777,33521530,swyx,2021-09-27T22:00:47+00:00,"""Let user group by business logic instead of force them to fit to your lifecycle method"" is still the single most important lesson in API design I've ever learned.

Used this exact diagram today in the design of @temporalio's JS SDK and so happy with the result. https://twitter.com/threepointone/status/1056594421079261185",,,1056594421079261185,1056594421079261185,,,1f89d6a41b1505a3071169f8d0d028ba9ad6f952,Twitter Web App,0,"[0, 262]",,,,,,,1,6,77,0,0,0,en,