"Everyone can reply" opens it up to the world
"People you follow" ensures that people you've selected are only able to reply
"People you've mentioned" means just that - specfically.
/2
If you post something to twitter, a social media platform by which ideas are shared, and you don't want people to comment on it or provide their opinions, you can use many tools on twitter (locking account, changing who can reply).
Calling disagreement "disrespectful" is bizarre
"Everyone can reply" opens it up to the world
"People you follow" ensures that people you've selected are only able to reply
"People you've mentioned" means just that - specfically.
/2
/3
Note: people will see "the author has hidden this, would you like to see?"
/4
/5
mute the conversation - "i'm done with this and don't wanna hear about it anymore"
mute the person - "i never wanna see their tweets"
block the person - "they can't see mine and i can't see theirs."
/6
/7
/8
/9
/10
More from Twitter
After hearing about @JanelSGM from @csallen, I spent the past few hours digging into her Twitter feed to see how she has been building Newsletter OS in public, from ideation to launch.
Here are some highlights in chronological order and what you can learn from the process:
1/ August 5 2020: Janel digs into '50+ newsletters' (note the number to build credibility) and creates a thread to discuss the lessons learnt. She also mentions that this is for a side project, which raises awareness of something she may be working
2/ August 5 2020 (cont): Each tweet in the thread is focused on a key message, with clear pointers for newsletter writers to
3/ September 1 2020: Janel tweeted about #buildinginpublic (note the hashtag) with @pabloheredia24 for @makerpad's challenge. While the project is https://t.co/tMb1qCnxVY and not NewsletterOS, Janel is getting in the reps on how to build in
4/ October 18 2020: Janel hints at building her new product using @NotionHQ and @gumroad. But instead of telling the audience directly what the product is, she invites her audience to take a guess.
Here are some highlights in chronological order and what you can learn from the process:
1/ August 5 2020: Janel digs into '50+ newsletters' (note the number to build credibility) and creates a thread to discuss the lessons learnt. She also mentions that this is for a side project, which raises awareness of something she may be working
Just subscribed to 50+ newsletters in the past hour
— Janel (@JanelSGM) August 4, 2020
(for a side project)
Here are some lessons I've learned
Thread \U0001f447
2/ August 5 2020 (cont): Each tweet in the thread is focused on a key message, with clear pointers for newsletter writers to
1/ Clear Value Proposition
— Janel (@JanelSGM) August 4, 2020
Do you articulate clearly the following?
- What content you write about
- Who your newsletter is for
- How your audience will benefit from your newsletter?
3/ September 1 2020: Janel tweeted about #buildinginpublic (note the hashtag) with @pabloheredia24 for @makerpad's challenge. While the project is https://t.co/tMb1qCnxVY and not NewsletterOS, Janel is getting in the reps on how to build in
4/ October 18 2020: Janel hints at building her new product using @NotionHQ and @gumroad. But instead of telling the audience directly what the product is, she invites her audience to take a guess.
I've been launching a product a month, with the aim of launching 12 in 12 months (w/ @LaunchMBA)
— Janel (@JanelSGM) October 18, 2020
This month, I'll be launching an actionable info product.
Core Tools: @NotionHQ @gumroad
Want to guess what I'll launch?
Free copy for the first person who guesses right.
1/
Thinking about this tweetstorm, one of the issues I’ve run into as an engineering leader is what to call the software engineering stuff that’s “agile” given that the Agile Community(tm) has killed the brand.
2/
And by & large, I’ve taken to call it “DevOps”, because the DevOps community have taken up much of the mantle @KentBeck & the XP community started with. & Kent has independently focused on safe small changes deployed to production. Which is DevOps.
3/
Much of the art here is making changes safe enough to deploy to production continuously. And to do that, we need to design incrementally, test obsessively, take architecture seriously so we decompose dependencies. & we need to automate everything & do it all the time.
4/
It turns out that this is what Kent & @RonJeffries @GeePawHill & many other folks have been nattering on about & being broadly misunderstood. @KentBeck has some brilliant essays (scattered across FB & his site alas) & @GeePawHill has amazing twitter threads on the topic
5/
When you look at *what it takes* to get to the DORA measures that @nicolefv & team write about in Accelerate, the input metrics for the DORA outputs, it’s making small changes safe.
Thinking about this tweetstorm, one of the issues I’ve run into as an engineering leader is what to call the software engineering stuff that’s “agile” given that the Agile Community(tm) has killed the brand.
I might do an \u201cagile\u201d tweet storm to the effect that all the attention is to the least leveraged portions of the value stream. Interest?
— Arien Malec (@amalec) October 26, 2019
2/
And by & large, I’ve taken to call it “DevOps”, because the DevOps community have taken up much of the mantle @KentBeck & the XP community started with. & Kent has independently focused on safe small changes deployed to production. Which is DevOps.
3/
Much of the art here is making changes safe enough to deploy to production continuously. And to do that, we need to design incrementally, test obsessively, take architecture seriously so we decompose dependencies. & we need to automate everything & do it all the time.
4/
It turns out that this is what Kent & @RonJeffries @GeePawHill & many other folks have been nattering on about & being broadly misunderstood. @KentBeck has some brilliant essays (scattered across FB & his site alas) & @GeePawHill has amazing twitter threads on the topic
5/
When you look at *what it takes* to get to the DORA measures that @nicolefv & team write about in Accelerate, the input metrics for the DORA outputs, it’s making small changes safe.
