Get fresh prompts and ideas whenever you write - with examples of popular tweets.
Write better tweets with a focused composer
Create your content without distractions - where it's easier to write and organize threads.
Save and schedule threads — on any device
Your drafts are automatically synced, so you can edit and schedule them later.
Discover what works with powerful analytics
Easily track your engagement analytics to improve your content and grow faster.
Love it 🔥
Write with your teammates and get feedback with comments.
Rewrite as thread start
Make it Punchier
AI is built-in
Get suggestions, tweet ideas, and rewrites powered by AI.
And much more:
Auto-Split Text in Tweets
Connect Multiple Accounts
Top tweeters love Typefully
70,000+ creators and teams chose Typefully to curate their Twitter presence. Join them.
For 24 months, I tried almost a dozen Twitter scheduling tools.
Then I found @typefully, and I've been using it for seven months straight.
When it comes down to the experience of scheduling and long-form content writing, Typefully is in a league of its own.
I forgot about Twitter for 10 years. Now I'm remembering why I liked it in the first place.
Huge part of my new love for it: @typefully. It makes writing threads easy and oddly fun.
This is my new go-to writing environment for Twitter threads.
They've built something wonderfully simple and distraction free with Typefully.
Such a huge fan of what @typefully has brought to the writing + publishing experience for Twitter.
Easy, elegant and almost effortless threads - and a beautiful UX that feels intuitive for the task - and inviting to use.
Luca Rossi ꩜@lucaronin
After trying literally all the major Twitter scheduling tools, I settled with @typefully.
Kudos to @frankdilo and @linuz90 for building such a delightful experience.
Killer feature to me is the native image editor — unique and super useful 🙏
Queue your content in seconds
Write, schedule and boost your tweets - with no need for extra apps.
Schedule with one click
Queue your tweet with a single click - or pick a time manually.
Pick the perfect time
Time each tweet to perfection with Typefully's performance analytics.
Boost your content
Retweet and plug your tweets for automated engagement.
Start creating a content queue.
Tweet with daily inspiration
Break through writer's block with great ideas and suggestions.
Start with a fresh idea
Enjoy daily prompts and ideas to inspire your writing.
Check examples out
Get inspiration from tweets that used these prompts and ideas.
Flick through topics
Or skim through curated collections of trending tweets for each topic.
Check the analytics that matter
Build your audience with insights that make sense.
Write, edit, and track tweets together
Write and publish with your teammates and friends.
Share your drafts
Brainstorm and bounce ideas with your teammates.
Love it 🔥
Get feedback from coworkers before you hit publish.
Read, Write, Publish
Control user access
Decide who can view, edit, or publish your drafts.
AWS: releases a 4-seat SUV.
Tech thought leaders:
1️⃣ "Dammit AWS, this is too big for the 1 me to use to cross the street. Followers, this is shit, do not use!"
2️⃣ "Dammit AWS, this does not have the 56 seats I need to transport people. Audience, this is shit, do not use!"
AWS: releases a fun convertible car, good mileage, $50k price, super-comfortable.
Shitfluencers: dammit AWS, the trunk of this is so small. How can I carry 5 tons of fertilizer with this!?! Dear followers, this is a shit service, do not use.
After watching 289 talks, I can now confidently share my re:Invent 2022 recap 🕵️♂️
Verdict: I am whelmed. Not underwhelmed or overwhelmed, just whelmed.
Since there were a bunch of other "unboxing" recaps already, here's a thread with an ✨actionable✨ recap.
Beware #1: I am a dum-dum working with partial information here. There's a fair chance this thread will have at least a couple mistakes or bad takes. Always hedge your bets!
Beware #2: I am only *only* talking about re:Invent launches. No pre-invent releases!
Another "so close and yet so far away" release from AWS
AWS needs to realize that:
1️⃣there's a world outside AWS
2️⃣not everybody has AWS' reliability requirements & profit margins
This could've been awesome, but no, AWS keeps repeating the same mistakes
To be fair, the Deployment Pipeline Reference Architecture (DPRA) gets *A LOT* of things right. Good job on that!
Seriously 👏 I especially like all the examples!
And there's a big need for something like this. I applaud AWS tackling this!
But then problems starts to appear...
Announcing the return of office hours — now in a paid, 1-hour format!
For 1000€, you can get my thoughts on any problem and actionable solutions for your company. No more strategic blunders!
I used to do this a lot in the past: folks reached out to get my thoughts over DMs/email and we'd schedule something.
Due to a bunch of abuse I was forced to stop 😞
I missed them A LOT, so paid office hours is my attempt at bringing this back! We'll see how it goes 🤞
As an ECS on Fargate fan, I got a lot of questions about the recent incident / outage.
Let's talk about it... 🧵 1/43
TL;DR: meh. Incidents happen and this one did not teach us anything new about building on AWS. I expect more profound drama during these roaring 20s!
Disclaimer: everything fails all the time! I view incidents as "normal" and this thread reflects that.
Yes, AWS had incidents. Yes, us-east-1 is HUGE so it gets interesting incidents. Yes, AWS is bad at communication.
This is the default and well-known state!
If you speak Romanian, I already gave a talk on this topic at Bucharest's Cloud Native Meetup in September 2021! See this video, starting at 51:05: https://youtu.be/XFP1-45ZL08?t=3065
Watch that instead, as this thread is an English re-cap of that talk!
Let's see how Amazon CodeWhisperer and GitHub Copilot compare!
CodeWhisperer: in preview, just announced. Python, Java, JS
Copilot: generally available, just graduated from preview. Dozens of languages(?)
I'll compare a couple scenarios, but let me know if you have test ideas👇
Rant: can we please stop pretending that serverless in 2022 is the same thing as serverless in 2016?
We're intellectually masturbating about what "serverless" means and we're confusing people, all while we're like on serverless v3!
Of course v3 products don't fit in v1 boxes!
Serverless v1 came in with a bang but failed to capture most of the market.
Serverless v2 is an effort to apply serverless practices to things most people already know and do, but "it's nOt TruE sERvErLeSs".
At the same time, Serverless v3 is exploring what's next.
Brave: you're hiring and your process includes a coding quiz/take-home exercise
Really brave: you're doing the above and assuming everybody has a dev env with 15 specific tools and DBs already installed, configured, and working perfectly
"SWE candidates are so bad these days"🙄