I came across this blog on how to give good scientific talks. I’m up to the second post and I agree with almost all of it so far. Eliminating words on slides and using presenter notes is something I’ve recently started to do. It takes some more practice but I feel like people are indeed more engaged in the talk.
I came across this article on retraction watch. It offers some practical and concrete advice for setting up expectations and checks when beginning new collaborations. I’m filing it here for posterity – I’d like to implement many of the suggestions.
Some of the tips are a bit specific to bioinformatics / computer science, but one idea I really liked was to have a chronologically-organised electronic notebook for each project. This would sketch out analyses / experiments you tried, what worked, and what didn’t. You could also “transcribe notes from conversations as well as email text into the lab notebook”. This type of document makes way more sense to me than keeping a single general lab notebook for all the projects you’re doing. Perhaps that helps you too, but notes about a specific project should all be accessible within the project directory. This idea would definitely complement some others that I’ve previously detailed on this blog.
I was invited to write a guest post for the blog Political Science Replication. For those who have been reading my blog for a while there’s not much new there, but feel free to check it out.
Quick post for a useful link: here’s a guide to setting up your Github repository with a Digital Object Identifier (DOI) so that it’s statically citable!