ЁЯУ▒ Over the past 2-3 years, I screenshotted a ton of random tweets about social/product that made me think
Here they are, in chronological order, w highlights from @nikitabier, @BrianNorgard, @rsg, @Mazzeo, @prestonattebery, + many more
(sry for weird twtr cropping + threading)
literally have a folder of dozens of my fav screenshotted tweets on consumer social product stuff...and @nikitabier is well represented
— Adam O'Kane \U0001f4ad (@adamokane) February 13, 2021
Takeaways from this: I should pay @nikitabier and the rest of you for your tweets. Can't believe this website is free!
More from Twitter
Here are some of the best threads I've ever read on Twitter,
All related to
- Startups
- Entrepreneurship
- Indiehacker
- Wealth
- Health
- Life nd philosophy
I'll keep updating them regularly
Read below ЁЯСЗ
1. Getting reach without being luck, best tweet ever by
2. On meditation by
3. On college and eduction by
4. "Deep Year" concept by
All related to
- Startups
- Entrepreneurship
- Indiehacker
- Wealth
- Health
- Life nd philosophy
I'll keep updating them regularly
Read below ЁЯСЗ
1. Getting reach without being luck, best tweet ever by
How to Get Rich (without getting lucky):
— Naval (@naval) May 31, 2018
2. On meditation by
Meditation - The Art of Doing Nothing:
— Naval (@naval) May 16, 2020
3. On college and eduction by
I\u2019ve gotten a lot of bad advice in my career and I see even more of it here on Twitter.
— Nick Huber (@sweatystartup) January 3, 2021
Time for a stiff drink and some truth you probably dont want to hear.
\U0001f447\U0001f447
4. "Deep Year" concept by
Obsessed with this idea:
— Jordan O'Connor (@jdnoc) July 28, 2020
Pick a niche I'm interested in.
Write/study daily about the topic.
Write 100 articles in a year.
Get SEO traffic.
Build email list.
Ask them what they want and build it.
Sell products (physical or digital).
Start fresh with a new niche next year.
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.
