These values represent the average engagement across all tweets compared to the first tweet of the thread.
(Keep in mind these numbers don't come from controlled experiments, so take the results with a grain of salt.)
Lately, I've measured the quality of my threads differently.
This method is very subjective, but it aligns much better with what I want.
(And I cannot automate this, unfortunately.)
Here are the five questions I ask:
1. How good were the responses I got? 2. Did people seem confused after reading it? 3. Did I get any relevant feedback? 4. Did I learn anything new from the replies? 5. Did I attract any prominent accounts?
This helps me learn and iterate.
A simple framework that will help you succeed with your threads:
1. Experiment 2. Learn something from it 3. Repeat
Hopefully, this helps get your message further.
Feel free to use this very same thread to measure the ratio of likes between subtweets and the first tweet.
Anything over 10% is pretty decent in my book.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
I've been trying to identify the most effective trait for those building a career in software development.
If I were to give you one single recommendation, what would that be?
I think I figured it out. ↓
Here is a problem I see every day:
Most people start their careers solving the same boring exercises.
This is good in certain ways, but it also limits your experience to what everyone else is doing.
The key to getting out of this trap?
*Curiosity*
If there's a single trait that has helped me make continuous progress over the last two decades in building software, it has been a relentless curiosity.
And contrary to what many believe, you can learn to be curious.