Actually, I prefer to write a twitter thread first and then blog it. My 2c on this, - Yes the ux sucks but people are used to reading threads. - There are too

Actually, I prefer to write a twitter thread first and then blog it. My 2c on this, - Yes the ux sucks but people are used to reading threads. - There are tools like thread reader app that unroll threads and store for future reference. - tools like Dewey help manage threads. - tools like chirr.app and typefully help create threads with nice heuristics that split your post into threads. - You get distribution and get to grow an audience. - specific tweets can be thought of as “highlights” that are retweeted vs liked - it’s easier to link other peoples tweets and threads, as well as your own to build a knowledge graph of sorts - it forces you to think in small increments and build up your arguments in sequence. I’ve found it quite helpful in articulating thoughts. - lastly, by publishing it on twitter and inviting debate, your audience could get you to rethink povs and also add more of them to your thinking. when you finally write a post, not only are they more likely to retweet and get you seen wider — they’ll feel an aspect of contribution to it which helps cement your relationship with them.