tweets

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

9 rows where "created_at" is on date 2021-07-30, is_quote_status = 0, retweeted = 0 and source = "1f89d6a41b1505a3071169f8d0d028ba9ad6f952" sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: in_reply_to_user_id, in_reply_to_screen_name, retweet_count, lang

user 2 ✖

source 1 ✖

  • Twitter Web App · 9 ✖

retweeted 1 ✖

is_quote_status 1 ✖

created_at (date) 1 ✖

  • 2021-07-30 · 9 ✖
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
1420987461799317504 swyx 33521530 2021-07-30T05:59:46+00:00 Part 2 of my 1984 vs Brave New World debate clips from @IQ2US: A masterful pacing-and-leading of the Orwellites, in favor of Aldous Huxley's Brave New World! https://swyx.transistor.fm/episodes/1984-vs-brave-new-world-pt-2-intelligence-squared       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 183] 1420635902032846852 33521530 swyx       0 0 1 0 0 0 en  
1420988748121079810 swyx 33521530 2021-07-30T06:04:52+00:00 @NoriSte @CharlesStover @code @stolinski i understand this rule but altogether the long list of rules feel overwhelming. I always recommend limiting the ruleset to just the few things you really care about (new joiner should be able to recall them from memory) and the stuff you can automate. Let go of the rest.       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [41, 312] 1420959553160634370 135176266 NoriSte       0 0 1 0 0   en  
1421069160973434880 Andrew Gazdecki 1511333035 2021-07-30T11:24:24+00:00 July update for @microacquire! - $700,000 in ARR - 16% MoM growth - $400m combined revenue - $82m combined revenue in July - 34% company size increase YTD - 4x'ed registered buyers in 2021 - 250+ startups listed More micro-details below 👇 https://twitter.com/agazdecki/status/1421069160973434880/photo/1       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 240]             0 36 569 0 0 0 en  
1421205257325924353 swyx 33521530 2021-07-30T20:25:12+00:00 @code @stolinski Here is me using Easy Snippet in our daily work at @temporalio What other little tips and tricks help boost your productivity like this? https://docs.temporal.io/blog/temporal-tips-tricks-1/       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [17, 179] 1420772267772968960 33521530 swyx       0 0 7 0 0 0 en  
1421220603197939713 swyx 33521530 2021-07-30T21:26:11+00:00 @b0rk @reactjs oh yay I get to introduce you to this idea! React uses fixtures heavily to reproduce browser bugs and offer starting points for some APIs that require a lot of setup: https://github.com/facebook/react/tree/main/fixtures @stevekinney and I are stealing this idea for @temporalio https://github.com/temporalio/samples-go/tree/master/temporal-fixtures       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [15, 289] 1421209766236405763 6603532 b0rk       0 0 9 0 0 0 en  
1421220644662824965 swyx 33521530 2021-07-30T21:26:21+00:00 @gusfune @code @stolinski didnt know! thats cool!       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [26, 49] 1421206169708810244 15359622 gusfune       0 0 0 0 0   en  
1421225521178763266 swyx 33521530 2021-07-30T21:45:43+00:00 @acdlite @reactjs ya i see fixtures as "manual tests" that complement e2e/unit/integration testing. By all means automate everything if you can, but there's a lot of stuff that can't be automated, particularly bugs we don't know about yet. Fixtures help reduce the activation energy to repro bugs!       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [18, 298] 1421224201181143040 21782915 acdlite       0 0 4 0 0   en  
1421236750903435264 swyx 33521530 2021-07-30T22:30:21+00:00 @maxibanki @jsjoeio @reactjs conceptually we mean the same thing - known good starting points - but it seems that most people including FB primarily use them for automated testing I guess my weird angle/insight is that we should have a crap ton more of them for MANUAL testing and bug repros too       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [29, 296] 1421235679560933378 411011229 maxibanki       0 0 2 0 0   en  
1420987668754681856 swyx 33521530 2021-07-30T06:00:35+00:00 @Brandwagon @code @stolinski https://overreacted.io/goodbye-clean-code/       Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [29, 52] 1420959691690188808 16722308 Brandwagon       0 0 1 0 0 0 und  

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]);