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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1420987461799317504 | 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 | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 183] | 1420635902032846852 | 33521530 | swyx | 0 | 0 | 1 | 0 | 0 | 0 | en | |||||||
1420987668754681856 | 33521530 | 2021-07-30T06:00:35+00:00 | @Brandwagon @code @stolinski https://overreacted.io/goodbye-clean-code/ | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [29, 52] | 1420959691690188808 | 16722308 | Brandwagon | 0 | 0 | 1 | 0 | 0 | 0 | und | |||||||
1420988748121079810 | 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. | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [41, 312] | 1420959553160634370 | 135176266 | NoriSte | 0 | 0 | 1 | 0 | 0 | en | ||||||||
1421138057940529156 | 33521530 | 2021-07-30T15:58:11+00:00 | @txase can i enquire more about what the lambda triggers? is this for a “work loop”? have you explored Step Functions? | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [7, 118] | 1421122672054788101 | 112043917 | txase | 0 | 0 | 2 | 0 | 0 | en | ||||||||
1421140683021164558 | 33521530 | 2021-07-30T16:08:37+00:00 | I think this was the second last React talk I ever gave. Still pretty happy with it, check it out if you’re interested in how “linguistics” and developer experience cross paths (and explain the trends in our evolving tooling) https://twitter.com/iBakasura/status/1421095739195756549 | 1421095739195756549 | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 226] | 1 | 0 | 2 | 0 | 0 | 0 | en | |||||||||
1421144382283993089 | 33521530 | 2021-07-30T16:23:18+00:00 | @dalmaer but was it cheeky | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [9, 26] | 1420982293498269696 | 4216361 | dalmaer | 0 | 0 | 0 | 0 | 0 | en | ||||||||
1421180194384084995 | 33521530 | 2021-07-30T18:45:37+00:00 | Non obvious thing I picked up from @reactjs — keep a set of fixtures to help you repro bugs! Instead of starting from a blank file or deleting from a real project, fixtures are the middle way — a starting point that implements all the APIs or pushes them to known limits. https://twitter.com/b0rk/status/1421141801407291398 | 1421141801407291398 | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 272] | 1 | 0 | 42 | 0 | 0 | 0 | en | |||||||||
1421205257325924353 | 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/ | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [17, 179] | 1420772267772968960 | 33521530 | swyx | 0 | 0 | 7 | 0 | 0 | 0 | en | |||||||
1421220603197939713 | 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 | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [15, 289] | 1421209766236405763 | 6603532 | b0rk | 0 | 0 | 9 | 0 | 0 | 0 | en | |||||||
1421220644662824965 | 33521530 | 2021-07-30T21:26:21+00:00 | @gusfune @code @stolinski didnt know! thats cool! | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [26, 49] | 1421206169708810244 | 15359622 | gusfune | 0 | 0 | 0 | 0 | 0 | en | ||||||||
1421225521178763266 | 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! | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [18, 298] | 1421224201181143040 | 21782915 | acdlite | 0 | 0 | 4 | 0 | 0 | en | ||||||||
1421229372581634048 | 33521530 | 2021-07-30T22:01:02+00:00 | @threepointone thank u next | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [15, 27] | 1421133866446827530 | 1593171 | threepointone | 0 | 0 | 3 | 0 | 0 | en | ||||||||
1421229828636774400 | 33521530 | 2021-07-30T22:02:50+00:00 | @acdlite @reactjs gotcha, ok will not emphasize their relationship to testing going forward, thank you | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [18, 102] | 1421226595994456065 | 21782915 | acdlite | 0 | 0 | 1 | 0 | 0 | en | ||||||||
1421234899181215751 | 33521530 | 2021-07-30T22:22:59+00:00 | @acdlite @reactjs yes this does make sense! fixtures that don’t work bc they are out of date are just dead weight. continuous e2e on them is a great principle. and no i totally get that you just want to offer the right perspective since, well, you work on the team 😂 so it is hugely appreciated | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [18, 295] | 1421234029983059972 | 21782915 | acdlite | 0 | 0 | 0 | 0 | 0 | en | ||||||||
1421235379533877248 | 33521530 | 2021-07-30T22:24:54+00:00 | @acdlite @reactjs my main agenda is I think more OSS projects should adopt/offer fixtures to improve the quality of bug reports, since minimal repros always help (and was the main thing @b0rk was asking in the original thread) so just offered up React the best known example I knew | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [18, 282] | 1421234899181215751 | 33521530 | swyx | 0 | 0 | 4 | 0 | 0 | en | ||||||||
1421236750903435264 | 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 | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [29, 296] | 1421235679560933378 | 411011229 | maxibanki | 0 | 0 | 2 | 0 | 0 | en | ||||||||
1421221582031056897 | 33521530 | 2021-07-30T21:30:04+00:00 | @reactjs I don't mean "working with React", I mean "contributing TO React" - you can see how much React relies on fixtures to help ourselves manually reproduce all the things we can't in tests (and there are many!) See links below: https://twitter.com/swyx/status/1421220603197939713?s=20 | 1421220603197939713 | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [9, 257] | 1421180194384084995 | 33521530 | swyx | 1 | 1 | 6 | 0 | 0 | 0 | en | ||||||
1421190477571710978 | 33521530 | 2021-07-30T19:26:28+00:00 | this is incredible to watch. I thought that Flippa/Empire Flippers had cornered this sleepy market, but Andrew is shaking it up with his infectious energy and focus. Building a credible “Zestimate for SaaS” is going to set this thing on 🔥 https://twitter.com/agazdecki/status/1421069160973434880 | 1421069160973434880 | 95f3aaaddaa45937ac94765e0ddb68ba2be92d20 | 0 | [0, 239] | 1 | 2 | 31 | 0 | 0 | 0 | en | |||||||||
1421069160973434880 | 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 | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 240] | 0 | 36 | 569 | 0 | 0 | 0 | en | ||||||||||
1421141801407291398 | 6603532 | 2021-07-30T16:13:03+00:00 | I'm thinking about this debugging advice today -- I explained *why* to make a minimal reproduction but not *how* to make one https://twitter.com/b0rk/status/1405900088195661831 if you learned how to minimally reproduce a bug recently -- what helped you learn? | 1f89d6a41b1505a3071169f8d0d028ba9ad6f952 | 0 | [0, 232] | 1 | 64 | 295 | 0 | 0 | 0 | en |