@pradumna_saraf
Developer Advocate | @Docker Captain | Open Source Developer | DevOps | Golang | Owner @syntaxmedia_
Posts
39
16 increase
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
6.8K
253.5% 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
153
628.6% increase
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
97
0.4% 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 |
|---|---|---|---|---|---|---|---|
| In Go switch statements, we have a feature called “fallthrough”. Its purpose is to continue execution to the next case, even if it doesn’t match. One of the hidden gems of Golang. Share two examples below, one for understanding and one real-life use cases. https://t.co/x0GJOH2k9j | 816 | 3 | 0 | 16 | 4 |
2.94%
|
|
| Being kind and empathetic costs nothing and makes everything so much better. It’s hard to find that in people nowadays. | 769 | 1 | 0 | 19 | 3 |
2.99%
|
|
| Whether you care about open source or not, you are using it in some form anyway. | 691 | 1 | 0 | 24 | 4 |
4.2%
|
|
| If you're learning Golang and looking for a project to build, try creating a CLI tool. Many great tools are written in Go, like the Docker CLI and kubectl (Kubernetes). I also wrote a blog on building an AI-powered CLI, here is the link https://t.co/8DkK8rhRKZ | 606 | 1 | 0 | 10 | 5 |
3.3%
|
|
| Received a Golang badge on @ThePracticalDev. It may sound childish, but I like these kinds of sweet badges. Of course, it's not easy to get. You have to have the best article weekly. https://t.co/NEqsHGXUbS | 565 | 0 | 0 | 22 | 3 |
4.42%
|
|
| If you maintain a GitHub repo, turn on the Automatically delete head branches feature in settings. It’s great for the sanity of your Git workflow, as stale branches can clutter things up. Also, when someone clones a repo, all the merged branches get pulled too (if not deleted). https://t.co/mWhKdZx0eI | 537 | 1 | 0 | 13 | 3 |
3.35%
|
|
| Do you know about IIFEs - Immediately Invoked Function Expression in Golang? They’re anonymous functions that run immediately when defined, great for handling quick tasks. https://t.co/7OmjR1NihV | 492 | 2 | 0 | 16 | 2 |
4.07%
|
|
| Here’s a tip: If you are learning about some tech, listen to the problems people are sharing in support/help channels. You will learn so much just by reading and understanding the pain points, and it sparks curiosity. | 383 | 0 | 0 | 12 | 0 |
3.13%
|
|
| @deno_land Done my part. Signed | 367 | 0 | 0 | 1 | 0 |
0.27%
|
|
| @eddiejaoude Haha. Feature Flags safeguard you to deploy even on Fridays. | 234 | 1 | 0 | 2 | 1 |
1.71%
|
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (3 + 0 + 16 + 4 + 1) / 816 * 100 =
For this tweet: (3 + 0 + 16 + 4 + 1) / 816 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (1 + 0 + 19 + 3 + 0) / 769 * 100 =
For this tweet: (1 + 0 + 19 + 3 + 0) / 769 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (1 + 0 + 24 + 4 + 0) / 691 * 100 =
For this tweet: (1 + 0 + 24 + 4 + 0) / 691 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (1 + 0 + 10 + 5 + 4) / 606 * 100 =
For this tweet: (1 + 0 + 10 + 5 + 4) / 606 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (0 + 0 + 22 + 3 + 0) / 565 * 100 =
For this tweet: (0 + 0 + 22 + 3 + 0) / 565 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (1 + 0 + 13 + 3 + 1) / 537 * 100 =
For this tweet: (1 + 0 + 13 + 3 + 1) / 537 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (2 + 0 + 16 + 2 + 0) / 492 * 100 =
For this tweet: (2 + 0 + 16 + 2 + 0) / 492 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (0 + 0 + 12 + 0 + 0) / 383 * 100 =
For this tweet: (0 + 0 + 12 + 0 + 0) / 383 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (0 + 0 + 1 + 0 + 0) / 367 * 100 =
For this tweet: (0 + 0 + 1 + 0 + 0) / 367 * 100 =
Engagement rate is calculated as (interactions / impressions) * 100.
For this tweet: (1 + 0 + 2 + 1 + 0) / 234 * 100 =
For this tweet: (1 + 0 + 2 + 1 + 0) / 234 * 100 =