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.
Working in a team where the policy is "never left any tech debt behind" it is surprising the amount of tech debt we already have accumulated. In fact, you can argue that what we are cleaning is not tech debt, but cruft code, I agree.
For the shake of this conversation, we are going to assume that such code is impossible to avoid entirely. So, if we always clean it before closing a user story, how can we have any of it.
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?
Last episode of @progesunam remainded me that time when I asked someone about an offer they published on the slack of @VigoTechAllianc. In that time, I thought the best way I can help new people getting to this industry was making the questions they weren't able to make.
So, as this offer didn't include a salary range, I asked for it. The main excuses I received were these:
Pair programming is great, but only if you do it right. You can do it wrong and still get good things from this practice, but at the same it could be very frustrating. I start thinking on this after read some people complaining about it on Twitter.
Usually, the big problem to implement this kind of practices are far from the developer team. However, in those tweet seemed to be something more. After practicing it steadily during 8 months,
To create software in small batches is hard. Progress taking small steps require finding the right increment and focus on reach it with the simpler solution. Sometimes I boycott myself, including more thing than those inside the scope.
Coding, sometimes, is like land a plane in the middle of the night in an unknown airstrip without lights. You know what you want, but you are going to discover how to do it at the same time you do it. It could be must easier if at least you have a light at the end of the airstrip
A driver is something like that, something that keep you in the right track in spite of the all the other problems you find during the landing.
Context is key, but I have to admit that outside-in approach has worked better for me much of the times. Usually it associated to London approach since starting from outside requires to use some mocks to substitute the component you have not implemented yet.
However, my approach is different. Start from outside writing just enough code to make the test pass, paying attention to the API you are exposing and less on the internal implementation.