Trusted by 70,000+ creators
Have multiple Twitter accounts? SelectΒ theΒ correct one first.
Share a recent learning with your followers.
Pose a thought-provoking question.
Get fresh prompts and ideas whenever you write - with examples of popular tweets.
Create your content without distractions - where it's easier to write and organize threads.
Your drafts are automatically synced, so you can edit and schedule them later.
+14
FollowersEasily track your engagement analytics to improve your content and grow faster.
@frankdilo
Feedback?
@albigiu
Love it π₯
Write with your teammates and get feedback with comments.
π§΅
Rewrite as thread start
π₯
Make it Punchier
β
Fix Grammar
Get suggestions, tweet ideas, and rewrites powered by AI.
And much more:
Auto-Split Text in Tweets
Thread Finisher
Tweet Numbering
Pin Drafts
Connect Multiple Accounts
Automatic Backups
Dark Mode
Keyboard Shortcuts
Queue your tweet with a single click - or pick a time manually.
Time each tweet to perfection with Typefully's performance analytics.
Retweet and plug your tweets for automated engagement.
Enjoy daily prompts and ideas to inspire your writing.
Get inspiration from tweets that used these prompts and ideas.
Or skim through curated collections of trending tweets for each topic.
Brainstorm and bounce ideas with your teammates.
@frankdilo
Feedback?
@albigiu
Love it π₯
Get feedback from coworkers before you hit publish.
Read, Write, Publish
Decide who can view, edit, or publish your drafts.
Share new drafts in Slack channel
New draft from RSS feed item content
New scheduled draft from Google Doc
New spreadsheet row from published tweet
Create new template draft every Monday
Send an email for every published thread
Create draft for new items in feeds folder
Thank new followers with a tweet
Share new drafts in Slack channel
New draft from RSS feed item content
New scheduled draft from Google Doc
New spreadsheet row from published tweet
Create new template draft every Monday
Send an email for every published thread
Create draft for new items in feeds folder
Thank new followers with a tweet
Vlad Ionescu (he/him)
@iamvlaaaaaaad
"Professional mistake avoider" AKA Independent Consultant. I help companies become super-high-performing! AWS Container Hero. π³οΈβπ he/him π³οΈβπ
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 https://pipelines.devops.aws.dev
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! https://office-hours.vladionescu.me
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!
The thoughts in the quoted thread ruffled some feathers, so let's do a quick observability 101. Alternative title: "how to not get abused by your logging/ monitoring/ o11y vendor" A 30-tweet thread cause I am trying to micro-blog π https://twitter.com/iamvlaaaaaaad/status/1543892406969442304
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!
TL;DR: 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"π
What's the fastest way to scale containers on AWS in 2022? Is EKS faster than ECS? What's faster: serverless workers (Fargate) or to serverful workers (EC2)? What about App Runner and Lambda? Now we know: https://www.vladionescu.me/posts/scaling-containers-on-aws-in-2022