tweets

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

6 rows where in_reply_to_screen_name = "buildsghost", is_quote_status = 0 and source = "1f89d6a41b1505a3071169f8d0d028ba9ad6f952" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

created_at (date) 5 ✖

source 1 ✖

  • Twitter Web App · 6 ✖

retweeted 1 ✖

  • 0 6

is_quote_status 1 ✖

in_reply_to_screen_name 1 ✖

  • buildsghost · 6 ✖
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
1432864758869356546 swyx 33521530 2021-09-01T00:35:54+00:00 @buildsghost @paulbiggar @darklang from what i heard, he already cut back a lot on his original vision 😂 i think Dark was even supposed to handle the frontend originally! but honestly, the sheer ambition is refreshing. too much incrementalism in tech. as i'm sure you no doubt feel.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [35, 282] 1432855994766217218 1175464650395111424 buildsghost       0 0 3 0 0   en  
1433616749694373893 swyx 33521530 2021-09-03T02:24:03+00:00 @buildsghost petition to use 👆 as topic variable       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [13, 48] 1433487820132270081 1175464650395111424 buildsghost       0 0 21 0 0   en  
1436410434211483648 swyx 33521530 2021-09-10T19:25:09+00:00 @buildsghost Smaller than 50 devs? sure. I'd honestly maybe draw the line at 20 devs but just splitting hairs at that point. I notice you left out "prod -> dev" productivity. Observability, monitoring, alerting. worthwhile category even at small sizes?       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [13, 256] 1436404964541145091 1175464650395111424 buildsghost       0 0 9 0 0   en  
1457460664230834176 swyx 33521530 2021-11-07T21:31:15+00:00 @buildsghost @floydophone @sebmck even the thing about checked-in source is controversial - i saw a thoughtleader™ on here a month or so ago passionately arguing for only publishing dist (not src) files because something something size of node modules       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [34, 251] 1457448799928926212 1175464650395111424 buildsghost       0 0 1 0 0   en  
1473024862721802240 swyx 33521530 2021-12-20T20:17:49+00:00 @buildsghost @tmcw its the most often used coded gatekeeping i see from people who would normally despite gatekeeping. ironic, but to be hypocritical is human i guess.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [19, 167] 1473023692221206530 1175464650395111424 buildsghost       0 0 4 0 0   en  
1473026573792325632 swyx 33521530 2021-12-20T20:24:37+00:00 @buildsghost @tmcw i think my framing of it couldve been better but i made an attempt at visualizing this in my book https://twitter.com/swyx/status/1473026573792325632/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [19, 116] 1473026068206403584 1175464650395111424 buildsghost       0 0 7 0 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]);