My first rule as a low-budget Twitter researcher is to collect interesting data first, ask (research) questions later. I have a lot of data I’ve never used, but I’d rather deal with that than a missed opportunity.
Similar Posts:
I got a reminder today that I do the kind of research where something as hilariously unintuitive as telling a program to treat long numbers as “words made up of 0-9” is actually a critical step to making sure you get the right results.
I love that I do the kind of research where I have to define terms like “hashtag” and “meme,” but I hate trying to figure out how much of a 1,000-word conference proposal to dedicate to those definitions.
Today’s manuscript revision fun is detangling the results of a coding error that left out 3 hours and 56 minutes worth of tweets from my analysis. Just enough to make some very small differences in reported results.
Just had a paper rejected from a special issue, but the journal has been such a pain to work with over the last 8(!) months that I’m frankly just glad it’s over.
Returning proofs for an accepted article is always fun!
Comments:
You can click on the < button in the top-right of your browser window to read and write comments on this post with Hypothesis. You can read more about how I use this software here.
Any Webmentions from Micro.blog will also be displayed below: