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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1417165270641045505 | 33521530 | 2021-07-19T16:51:44+00:00 | I'm excited to finally share why I've joined @temporalio as Head of Developer Experience! Here's my explainer on 3 core opinions of Temporal, why they're hard to do well, and the business opportunities it presents: https://www.swyx.io/why-temporal/ | 295366d0fb34352a1961af2413827f072adefdb9 | 0 | [0, 240] | 0 | 30 | 396 | 0 | 0 | 0 | en | ||||||||||
1417165280522821632 | 33521530 | 2021-07-19T16:51:47+00:00 | Why Orchestration: Every time you cross service boundaries, the probability of network or system failure increases. Instead of having every team write their own retries and timeouts and provisioning infrastructure, give them "reliability on rails". https://twitter.com/swyx/status/1417165280522821632/photo/1 | 295366d0fb34352a1961af2413827f072adefdb9 | 0 | [0, 251] | 1417165272008433682 | 33521530 | swyx | 0 | 4 | 28 | 0 | 0 | 0 | en |