Data source: swyx's twitter data
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1442926717635477504 | 3246815913 | 2021-09-28T18:58:32+00:00 | Incredibly excited to announce I've joined @vercel as a Developer Advocate! 🎉 I've been so impressed with Vercel as a company and their focus on great developer experience. Can't wait to contribute and help grow the Next.js and Vercel communities! | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 250] | 0 | 11 | 489 | 0 | 0 | en | |||||||||||
| 1446276421882581011 | 3246815913 | 2021-10-08T00:49:04+00:00 | I'm using a technique called "Following the Graph" (coined by @swyx) to better understand the Next.js ecosystem. This means exploring old Next.js talks, changelogs, and RFCs to rewind to the start and understand: • What's important • Who built it & why • What influenced it | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 279] | 0 | 4 | 88 | 0 | 1 | en | |||||||||||
| 1459765327047315460 | 3246815913 | 2021-11-14T06:09:09+00:00 | Been getting a lot of questions on what developer advocates do. Here's a useful framework for thinking about it (h/t @swyx). DevRel can be broken down into: • Content • Community • Product https://twitter.com/Nutlope/status/1459765327047315460/photo/1 | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 190] | 0 | 26 | 167 | 1 | 1 | 0 | en | ||||||||||
| 1465524682376069129 | 3246815913 | 2021-11-30T03:34:47+00:00 | @swyx I honestly think the highest ROI thing I ever did on Twitter was following you a year and a half ago | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [6, 106] | 1465524651719897089 | 3246815913 | Nutlope | 0 | 0 | 8 | 0 | 0 | en |