tweets
5 rows where user = 30192824 sorted by lang
This data as json, CSV (advanced)
Suggested facets: source, retweeted
created_at (date) 5 ✖
- 2020-07-27 1
- 2021-08-09 1
- 2021-09-27 1
- 2021-10-02 1
- 2021-10-18 1
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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1287798586651049985 | Gergely Orosz 30192824 | 2020-07-27T17:14:43+00:00 | Mind blown on how well-read @swyx is in the Coding Career Handbook (https://www.learninpublic.org/?a=uguka). He mentions almost all sources I would - like @Lethain on systems thinking or @mipsytipsy on tech risk profiles. I'm also learning tons of new dev stories (e.g. the "MooTools mafia"). https://twitter.com/GergelyOrosz/status/1287798586651049985/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 277] | 0 | 10 | 111 | 0 | 0 | 0 | en | ||||||||||
1424751510995406850 | Gergely Orosz 30192824 | 2021-08-09T15:16:45+00:00 | While EU companies are pondering if €80K/year for a senior engineer is too much or not, more (US) VC-funded ones are starting to offer €120K ($140-150K) and up *plus* equity for seniors in Europe. Here’s an example with @RevenueCat, who pay location independent. https://twitter.com/GergelyOrosz/status/1424751510995406850/photo/1 | Twitter for iPhone 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 263] | 0 | 75 | 588 | 0 | 0 | 0 | en | ||||||||||
1442537833495990278 | Gergely Orosz 30192824 | 2021-09-27T17:13:15+00:00 | A month into a paid newsletter for eng managers/engineers, it's taking off faster than I ever hoped: ~ 500 paid subscribers (thank you!) ~ 15,000 free subscribers ~ $62K ARR - A top 10 @SubstackInc technology newsletter Here's what I learned and advice on writing/newsletters 👇 https://twitter.com/GergelyOrosz/status/1442537833495990278/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 279] | 0 | 33 | 582 | 0 | 1 | 0 | en | ||||||||||
1444208430454034433 | Gergely Orosz 30192824 | 2021-10-02T07:51:36+00:00 | There is so little information written about equity for tech employees, and even less by software engineers who benefitted from it. Uber and Square engineer @mcdickenson wrote the book Equity Compensation for Tech Employees, which fills this gap. Here's the table of contents: https://twitter.com/GergelyOrosz/status/1444208430454034433/photo/1 | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 278] | 0 | 31 | 244 | 0 | 0 | 0 | en | ||||||||||
1449977842004074500 | Gergely Orosz 30192824 | 2021-10-18T05:57:11+00:00 | The sensible approach is not to delete one or the other. To maximize your "luck surface area" so opportunities find you, use both. They are very different networks. And one more on creating luck from @swyx: https://www.swyx.io/create-luck/ | Twitter Web App 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 231] | 1449976861967147011 | 30192824 | GergelyOrosz | 0 | 10 | 71 | 0 | 1 | 0 | en |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);