tweets

This is data scraped from swyx's timeline! See blog post

6 rows where display_text_range = "[0, 266]", lang = "en" and user = 33521530

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: retweet_count, created_at (date)

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
1420215212699840519 swyx 33521530 2021-07-28T02:51:07+00:00 Running communities is an incredible advantage for hiring. When both sides are playing infinite games and share values, it can be such an accelerant to the process. Makes you realize how much of the hiring process is just super lossy derisking of total strangers.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 266]             0 4 81 0 0   en  
1424172141289689090 swyx 33521530 2021-08-08T00:54:32+00:00 "How do you cut a monolith in half?" LOTS of gold in @tef_ebooks's exploration of why msg brokers don't replace load balancers or databases. The long-lived section is very relevant to @temporalio (lock manager + db + scheduler + protocol). https://programmingisterrible.com/post/162346490883/how-do-you-cut-a-monolith-in-half https://twitter.com/swyx/status/1424172141289689090/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 266] 1417315435892985856 33521530 swyx       0 1 10 0 0 0 en  
1425529550377684996 swyx 33521530 2021-08-11T18:48:24+00:00 This move by @GitHub is bold and inspiring. https://github.blog/2021-08-11-githubs-engineering-team-moved-codespaces/ With GitHub aggressively dogfooding Codespaces, cloud dev environments just went from "haha cute toy" to "OK this has serious enterprise investment". You're also now using Azure without knowing it.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 266]             0 62 368 0 0 0 en  
1438164876975751178 swyx 33521530 2021-09-15T15:36:41+00:00 It's a live demo too, not some aspirational animation. Go here and hit play: https://app.replay.io/recording/aae188fb-57d2-46af-a23a-0adba3ed0687 Switch to devtools, *RETROACTIVELY ADD LOGGING* and drill down to the exact state of any variable at any point in time. These folks killed console.log debugging. https://twitter.com/swyx/status/1438164876975751178/video/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 266] 1438161819927859210 33521530 swyx       0 3 23 0 0 0 en  
1448027262121496578 swyx 33521530 2021-10-12T20:46:16+00:00 To put Temporal inside of Netflix's "paved road", they needed every part of the stack to adapt to their needs, from Fast Properties (config store) to Chaos Monkey (fault injection) to Metatron (certs) to Wall-E (authn) to Gandalf (authz) to their own flavor of gRPC. https://twitter.com/swyx/status/1448027262121496578/video/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 266] 1448024109389008896 33521530 swyx       0 0 9 0 0 0 en  
1453165564445163520 swyx 33521530 2021-10-27T01:04:03+00:00 Possibly unpopular opinion: blanket bans on metasyntactic variables ("foo, bar, baz") are unwarranted. When you are designing APIs and documenting them for truly general usecases, using descriptive variable names gets in the way, and can even limit the imagination.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 266]             0 1 41 0 0   en  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [tweets] (
   [id] INTEGER PRIMARY KEY,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [full_text] TEXT,
   [retweeted_status] INTEGER,
   [quoted_status] INTEGER,
   [place] TEXT REFERENCES [places]([id]),
   [source] TEXT REFERENCES [sources]([id]), [truncated] INTEGER, [display_text_range] TEXT, [in_reply_to_status_id] INTEGER, [in_reply_to_user_id] INTEGER, [in_reply_to_screen_name] TEXT, [geo] TEXT, [coordinates] TEXT, [contributors] TEXT, [is_quote_status] INTEGER, [retweet_count] INTEGER, [favorite_count] INTEGER, [favorited] INTEGER, [retweeted] INTEGER, [possibly_sensitive] INTEGER, [lang] TEXT, [scopes] TEXT,
   FOREIGN KEY([retweeted_status]) REFERENCES [tweets]([id]),
   FOREIGN KEY([quoted_status]) REFERENCES [tweets]([id])
);
CREATE INDEX [idx_tweets_source]
    ON [tweets] ([source]);