- one minute read - 33 words

One of those afternoons where I’m auditing someone’s analysis code, but it’s an analysis of 4M rows of data, so I’m also doing spurts of grading while I wait for code to execute.

similar posts:

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.

When I taught keyboarding, students complained about HTML lessons, asking what it had to do with typing. I explained that if you mistype things, you break things… I’m sure they laugh now every time I bork my website w/ a misplaced line break.

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.

Looks like it’s “I’m going to need some banana bread and chocolate chips to make it through the rest of this response to reviewers letter” o’clock.

The stress I feel when assigning final grades is compelling evidence that I would never make it as a judge.

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.