tweets

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

3 rows where "created_at" is on date 2021-08-28 and is_quote_status = 1 sorted by lang

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: source

retweet_count 1 ✖

  • 0 3

created_at (date) 1 ✖

  • 2021-08-28 · 3 ✖
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
1431454424153604098 swyx 33521530 2021-08-28T03:11:44+00:00 🏃‍♀️ Time to Implement Change Anyone can build brittle systems. But great DX optimizes for 1-2 standard deviation changes in requirements: - find helpful docs fast (better: no docs needed) - low edit distance - smooth migration paths https://twitter.com/swyx/status/1395172543565344770?s=20   1395172543565344770 1395172543565344770   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 260] 1431454422886924293 33521530 swyx       1 0 7 0 0 0 en  
1431454427668434944 swyx 33521530 2021-08-28T03:11:45+00:00 ❗ Total WTFs per Year Anyone can design for the happy path. Great DX handles not only the good, but also the bad AND the ugly: - Errors that don't make me think - Billing that is predictable and boring - Proactive warning of known issues https://twitter.com/swyx/status/1294689838872981506   1294689838872981506 1294689838872981506   Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 0 [0, 264] 1431454426175352837 33521530 swyx       1 0 8 0 0 0 en  
1431715021868896259 swyx 33521530 2021-08-28T20:27:15+00:00 NEVER a bad look to acknowledge your weaknesses, flaws, and anti-goals. Better you say it upfront than have users drag it out of you (or worse, disbelieve your denials) It shows confidence that you solve an impt problem well enough you dont need to be all things to all people. https://twitter.com/kilianvalkhof/status/1431686864570826753   1431686864570826753 1431686864570826753   Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 0 [0, 278]             1 0 12 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]);