Get fresh prompts and ideas whenever you write - with examples of popular tweets.
The best writing experience, with powerful scheduling
Create your content without distractions - where it's easier to write and organize threads.
Cross-post to LinkedIn
Automatically add LinkedIn versions to your posts.
Discover what works with powerful analytics
Easily track your engagement analytics to improve your content and grow faster.
Love it 🔥
Collaborate on drafts and leave comments
Write with your teammates and get feedback with comments.
Rewrite as thread start
Make it Punchier
Improve your content with AI suggestions and rewrites
Get suggestions, tweet ideas, and rewrites powered by AI.
And much more:
Auto-Split Text in Tweets
Connect Multiple Accounts
Top tweeters love Typefully
100,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.
You know when a code is a bad code, you have a gut feeling, so you feel the necessity to critics that code and propose changes. Ok before doing that, let's do an exercise, why do those changes make the code any better?
Is it because you like it more and somehow that does it make better? Do you have any measurable argument that justify such a change? After a code review, the code is simpler because it is better or because you have more context?
I think we need a collection of properties we can use to express how good is a code.
I would say one thing that make a code better is understandability. Easier to understand, better the code. One property we can use is cognitive load,
if the cognitive load of a piece of code is under a threshold chances are that that code is easier to understand that one that surpass the limit. Does the code use language and team idioms? More idiomatic, the code is easier for the team to understand it.
The same happens with domain concepts, is the design influenced by domain concepts?
Another thing that could make a code better is how easy is to change that code. Here we can talk about coupling, and we can use connascence to compare one solution with another, removing subjectivity and personal preferences.
Dependencies are easy to count as well, fewer dependencies the better. I think we have some good tools to argue in a less dogmatic way, we only need to start using them. Which other do you think we can use?