Training Log Archive: iansmith

Wow, it turns out Ken wrote what amounts to an essay on his 2015 Highlander:
https://www.attackpoint.org/viewlog.jsp/user_1/per...

This week, I resubmitted our manuscript to PLoS Biology in reply to reviewer comments. We'll see how it goes, but I'm ecstatic to no longer have that work and deadline hanging over my head. Publication is onerous.

I have learned a few lessons -

1. limit the core team to as small a group as is feasible who can all work together well. Overly high maintenance and clashing personalities can be difficult to appease, especially when in principle, consensus is needed to move forward.


2. As a corollary to (1), avoid work situations where you and your boss have incompatible perspectives.


3. It's helpful - even as first author, doing the core work - to have a senior advocate who can assist with navigating the publication process


4. Structure your project in a way to maximize reproducibility; organize everything so that it could run on a new system with the code and data downloaded. Refactoring code is unpleasant.


5. Thoroughly document all your experiments, but keep this documentation separate from the final version of the analyses you implemented.


6. Done is better than perfect.