@AdamRackis
Senior Web Engineer. Prev, Riot. Next, React, Svelte, C++ when I'm feeling nasty. Beer, whiskey, coffee snob. Book lover. Jr Developer for life.
Posts
148
45 decrease
This section shows tweet / post counts for the last 7 days compared to the previous 7 days. If you have less than 14 days of data, we will show the available data.
Impressions
411.6K
4.2% increase
This is the total number of impressions your posts have made in the last 7 days compared to the previous 7 days. If you have less than 14 days of data, we will show the available data.
Likes
2.8K
16.1% decrease
This is the total number of likes you've received in the last 7 days compared to the previous 7 days. If you have less than 14 days of data, we will show the available data.
Followers
19
0.3% increase
This is the total number of followers you have acquired in the last 7 days compared to the previous 7 days. If you have less than 14 days of data, we will show the available data.
Impressions
Impressions
We collect new impression data each day if your graph isn't showing enough data yet, it's because we are waiting for more data to be available.
Followers
Followers
We collect new follower counts each day if your graph isn't showing enough data yet, it's because we are waiting for more data to be available.
Engagement
Engagement
We collect new engagement data each day if your graph isn't showing enough data yet, it's because we are waiting for more data to be available.
Top Posts
Top Posts
We show the top posts from the last 7 days.
| Post | Impressions | Retweets | Quotes | Likes | Replies | Engagement Rate | Actions |
|---|---|---|---|---|---|---|---|
| The V8 team is attempting to restrict / forbid syntax level evolution of JavaScript out of purported concerns for performance and end-users I am so unbelievably tired of Google having a disproportionate influence on the evolution of the web, and using it in the worst possible way First they rammed in dozens of web component specs that a) are still laughably incomplete, and b) cause framework authors no small amount of extra / useless work. And now this I'd also love someone to explain to me how, if perf is the overriding concern, how languages like C++, Rust, Swift, and certainly others continue to evolve. More context linked below 👇 | 115.5K | 29 | 4 | 401 | 27 |
0.51%
|
|
| In all seriousness what can they even add? Vite: handles TS & JSX, has great esm / cjs interop, has a test runner that's actually good, even has proxying, and probably a bunch of other stuff And it's so fast you could double the perf and I wouldn't notice. What else is there? | 59.7K | 8 | 2 | 214 | 35 |
0.49%
|
|
| Public service announcement: I am a software engineer at Spotify. But I am not in any way affiliated with Shopify. So if anyone needs help with Shopify SDKs or API's, I'm afraid I can't help you | 27.4K | 3 | 5 | 207 | 17 |
0.87%
|
|
| I just got saved from breaking prod in a section of the app I never, ever touch thanks to an automated test. It feels *so good* to work in a mature codebase. All you startup kiddies bragging about having no tests - have fun I guess 😘 | 26.9K | 14 | 3 | 488 | 22 |
2.02%
|
|
| Mastodon people talking about us https://t.co/bD55P7XJMv | 23.4K | 1 | 3 | 114 | 11 |
0.59%
|
|
| “But but but but you agreed not to call me out when I lie 😤” | 15.6K | 7 | 0 | 194 | 7 |
1.39%
|
|
| Rich Harris when he starts shitting on web components https://t.co/03N0hyLQWg | 9.8K | 0 | 0 | 178 | 3 |
1.9%
|
|
| The fact that 159 people, or 8% of the company took the buyout, in this egregious job market tells you how bad things are over there https://t.co/eXIsJmdWD2 | 8.8K | 3 | 0 | 105 | 7 |
1.33%
|
|
| Turns out web components aren’t just irrelevant noise. They actually create obnoxious work for framework authors | 8.3K | 1 | 0 | 73 | 4 |
1.03%
|
|
| Ok the jokes (and marketing) are dumb and by all accounts this is a legit feature. But can someone explain in plain terms what “concurrent execution” means for a Lambda? One Lambda instance executed concurrently by multiple callers? Does that mean for IO-bound work, the lambda will accept new calls while waiting? Like a regular JS event loop, but inside of a Lambda? If so, is the point to reduce the need to spin up new Lambda instances (saving money and cold start costs)? | 8.2K | 0 | 0 | 22 | 11 |
0.45%
|
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (29 + 4 + 401 + 27 + 132) / 115515 * 100 =
For this tweet: (29 + 4 + 401 + 27 + 132) / 115515 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (8 + 2 + 214 + 35 + 31) / 59678 * 100 =
For this tweet: (8 + 2 + 214 + 35 + 31) / 59678 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (3 + 5 + 207 + 17 + 7) / 27383 * 100 =
For this tweet: (3 + 5 + 207 + 17 + 7) / 27383 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (14 + 3 + 488 + 22 + 16) / 26919 * 100 =
For this tweet: (14 + 3 + 488 + 22 + 16) / 26919 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (1 + 3 + 114 + 11 + 9) / 23385 * 100 =
For this tweet: (1 + 3 + 114 + 11 + 9) / 23385 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (7 + 0 + 194 + 7 + 9) / 15649 * 100 =
For this tweet: (7 + 0 + 194 + 7 + 9) / 15649 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (0 + 0 + 178 + 3 + 4) / 9756 * 100 =
For this tweet: (0 + 0 + 178 + 3 + 4) / 9756 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (3 + 0 + 105 + 7 + 2) / 8768 * 100 =
For this tweet: (3 + 0 + 105 + 7 + 2) / 8768 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (1 + 0 + 73 + 4 + 7) / 8262 * 100 =
For this tweet: (1 + 0 + 73 + 4 + 7) / 8262 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (0 + 0 + 22 + 11 + 4) / 8221 * 100 =
For this tweet: (0 + 0 + 22 + 11 + 4) / 8221 * 100 =