tweets: 1425624206524379136
This data as json
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1425624206524379136 | 33521530 | 2021-08-12T01:04:32+00:00 | @temporalio something we debated at work that @martinfowler's Event Sourcing article leaves unclear: does Event Sourcing require you to fully reapply each function, or is it enough to just "dedupe" and restore state? https://news.ycombinator.com/item?id=28140598 | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [12, 242] | 1422424339589189633 | 33521530 | swyx | 0 | 0 | 2 | 0 | 0 | 0 | en |