Fast-tracking the PhD Experience
Can I just humorously preface this by saying that the email from the journal saying that they had received the manuscript addressed me as Dr Strydom and can’t say that I hate it - although maybe a bit premature 😉 Oh and maybe as another add on - working in different timezones may be annoying in terms of scheduling meetings but it is pretty great when you wake up in the mornings to ‘good job’ messages from your supervisor 😁
I’m not going to talk about the actual theory/content of the manuscript (because that I’m saving for the actual project page) but rather just talk about how being thrown into the deep end by your supervisor (but having him also throw you a very effective form of floatation device) results in quickly learning things in a driven manner, especially some handy collaborative workflow things that are also very Open Science and FAIR aligned.
Publishing so soon?
Look I’m not saying that all graduate students need to publish something right of the bat - and its a case of student readiness and opportunity that needs to be taken into consideration. However, that being said it makes for a fun way to help and encourage the student to get up to speed with literature and have it be in a rewarding manner (in a sense) as the student has a short-term goal to achieve. I also felt like it took away some of the daunting feeling of ‘where do we even start?’ after starting. It’s also a really great confidence boost and makes you feel like a ‘scientist’. Ultimately it also means that I have something ‘to show’ when I take my candidacy exam in a few months time - hopefully impressing the advisory board 😉
New coding language - sure why not?
So I knew going into this that learning how to work in
Julia was going to be inevitable - ‘it’s the way’ of the Poisot Lab after all. However, that being said learning, and
struggling pottering along with a new coding language when the submission deadline is seemingly in the distance is all fun and games, when its two days before d-day - not so fun. But overall its nice to work on a small, manageable chunk of the Julia-verse and a lot of the functions I was writing were simple arithmetic so it was a nice to work in a ‘low stakes’ situation with regards to getting to grips with how to write function and the ‘types’ that you can specify in
Julia. It also helps that after my toddler like attempt at writing a function my supervisor steps in and directs/shows me where I erred or what is a more ‘grammatically correct’ way of approaching the problem. Essentially I had a small and ‘contained’ crash course in a new programming language that will hopefully set me up for success further down the line.
Are you not entertained?
You know what’s the best part of my fast-tracked experience? It’s really helped build back some of the excitement and enjoyment for research and science-ing that I felt my masters had ‘taken’ from me. It also helps that my supervisor is very excited about everything we’ve done and I can’t help but feed off of that! It’s also very entertaining collaborating over GitHub with someone for both coding and writing and let me tell you its getting even more exciting regarding GitHub collaborating for our next project (The predicting ecological networks one if you’re wondering). I think (hopefully one day) I’ll write up a quick primer on collaborative writing over GitHub.
- SVD entropy reveals the high complexity of ecological networks
- These are not the Boundaries You're Looking for
- Next-generation field courses: integrating Open Science and online learning
- Why RStudio is a great tool for ecologists
- Taking FAIR and open science to the field - The evolution of the PFTC field course