Earlier quoted context omitted.
Huh what? Do you assume that code just works? Something's always breaking and there's always new features that people want. Editing tweets just barely became a thing. Which, btw, is the exact sort of feature that would be easy peg as trivial, but likely is not when you're running at Twitter scale. Before, a tweet had two states: created or deleted. Now it can have arbitrarily many states and possibly even interleaved…
I’m sorry I just don’t find the ability to edit tweets a groundbreaking new feature that is difficult to implement in 2022.
ex: You could store every tweet compressed in S3 with a bitmap for which are deleted (a bit that can be cached forever). That assumes you aren't going to ever have to update the object in S3. Once you have to update it that entire design is horrible, you'll need something completely different.
Consider that there are thousands of tweets per second with significant fan out for reads. There's search, relationship data (did you @ someone? did your edit remove that @?), business analytics, and more.