Day 137: Axe Sharpening...
Lately I've been really struggling to get to get round to adding anything to my blog, I put this down to the fact that I've been really busy getting things into some form of order as I start out in my new career as an academic. But whilst I feel that I've been working quite hard preparing for my PhD, developing new skills and getting my workflow set, I've not really got a great deal to show for it.
Certainly not when compared to the levels of productivity that I've been used to whilst out in industry, where cranking out high quality 20,000 word design reports complete with analysis and drawings happens in a week.
The more that I thought about this the more perturbed I became about what I wasn't achieving and it set me thinking... "What on earth have I been doing with my time?"...
Whilst I've not perhaps been hammering out the words in my thesis, I have been axe sharpening. Now this doesn't mean that I've lost all sense of reality and decided to become a lumberjack.
But instead it's more in the context of a tweet from one of my twitter contacts PigOnWheels from a few weeks ago, the quotation goes along the lines of:-
“Give me six hours to chop down a tree and I will spend the first four sharpening the axe.” -Abraham Lincoln.
Now I've no idea if this quote is legitimate or not and it is a close second to another quote that made me smile a lot lately:-
"The greatest thing about the internet, is that you can quote something and totally make up the source." - George Washington.
To some extent I don't particularly care if the axe sharpening quote is historically accurate, what interests me the most about it was that it sounds very much like my typical way of approaching things and helped me to take a step back and think about what I've really been doing the past few weeks.
Whilst I'm occasionally a very impulsive kind of person and quite often this gets me in trouble with the wife or ends up with me wondering what on earth possessed me to head out for a 12 mile walk in knee deep snow, when it comes to things that are work related I normally approach problem solving in a fairly logical and disciplined manner.
As a new academic, with no real experience of writing academic journals or papers, but with over 15 years of experience working as a chartered structural engineer, initially I thought (rather niaively) that I could turn my hand to writing academic papers quite easily, after all I've been designing and writing reports about £200m skyscrapers quite happily for years with no great difficulty.
What I hadn't anticipated was that academic writing is a very different process from writing design reports and that finding the most economic and quickest solution is not necessarily the same key driver as trying to solve a problem to which no-one has really drilled into in the same level of detail that you as the PhD student are about to.
After a brief "oh shit!" moment where it dawned upon me that I was going to have to develop a whole new set of skills and pronto, I did what every self respecting engineer would do and I turned to the oracle that is Google searching for topics linked to referencing systems, writing and tutorials and in amongst the results I came across lots of useful bits of information on the Harvard system and APA 6 and also a a few links to a piece of software called Scrivener that seemed to facilitate writing, but also allowed creative sorts to just get words down on a page, assemble them into some form of semblance and move, edit and redefine the structure of their documents almost on a whim.
Now ordinarily I create a roadmap for any sizeable document that I'm about to write and rarely depart from this plan and simply start to populate each section with ideas, then start to flesh out the bones. It's a system that I've used for years and I've taught my engineers that I've mentored to help construct ideas and encourage structured thinking.
However, one thing that I've come to grips with is that the idea/direction that you start out with when beginning a PhD is not necessarily the same idea that you end with and there are likely to be many changes in thinking and departures into new areas that perhaps you weren't even originally aware of along the way. This radical departure and tweaking of what can only be described as a sizeable piece of work can at best be described as daunting and certainly isn't that well sorted to Word, which has a pretty good reputation for falling over and dying when you least need it to.
The ability that Scrivener gives you to just throw in new chapters, shuffle and restructure sections of text to help concisely get over your argument really appealed to me, especially with the ability to shuffle about ideas on the corkboard, but I also wanted to integrate it with a bibliographic management software system somehow and whilst I know that EndNote has a dedicated toolbar within Word I had no idea how to do this within Scrivener.... again I turned to the oracle and came across this great video by Michael Axelsen.
This video, really unlocked a whole new way of working for me and suddenly I realised that I could work in a way in which allowed me to be highly chaotic and free thinking, but with the supporting rigid structure that a well defined bibliographic database such as EndNote provides.
The more that I looked into the process, the more I realised that actually I could save my PDF journals, fully annotated into my EndNote library and actually I could have this connected between the 3 computers that I use regularly via dropbox... in fact, now that there is a windows version of Scrivener more or less complete I could have my thesis share across multiple machines using dropbox and also backed up all in one spot for the innevitable accidental deletion simply by saving my files straight into my designated dropbox folder on my hard drive. It really didn't take me long to get this up and running and sure enough, EndNote files appear to be transferable between Macs and PC's as do Scrivener files with no real compatibility problems that I could identify and so, after a few initial tests I had the system up and running quite happily. But being an engineer, my brain wondered if it would be possible to improve upon or expand upon this arrangement in anyway. Again good old Michael Axelsen came to my rescue once again with a slightly longer video where he shares his workflow between EndNote, Scrivener and a piece of software that I'd not come across before called Evernote.
This opened up another dimension to my current arsenal of integration of information and how to build this into the structuring of my thesis, the only nagging little voice at the back of my head though was that whilst the workflow outlined was clearly highly efficient for Michael, it didn't quite feel natural to how I wanted to do things.
But having been educated that there were various bits of software out there that could manage citations, document management, group discussions and the writing process I took myself off to see what else lies out there. Quite a few of the pieces of software that I managed to come across seemed to be quite well understood by the students out there and from what I've been able to work out I'm more than a little late to the party on this.
I've been following some of the discussions on #phdchat on twitter and this has been a great source of ideas and has provided several little branches of ideas that I can run away with and try out for myself. One of the topics discussed was a survey of documentation management systems... some of these included Mendeley, Zotero and Papers... each of which have various merits and shortcomings and indeed there was a great article in Wired magazine lately where the directors of Mendeley were interviewed and their long term plans for chargeable content was discussed.
Having had a dabble with each of these bits of software I suddenly found that the ability to search for key phrases and content with Papers2 really seemed to fit with my workflow.
The fact that all my PDF's are in one spot and I can keyword search them to filter in subgroups, then create notes in them whilst I read, that I then copy and paste over into EndNote within the "research notes" field means that everything is knitted together, when I can't find a particular quote I've used in 2 years time, the ability to find it quickly from either my research notes or Papers2 will be a massive boon and will ultimately put time in my pocket. I still use EverNote, but I use it to capture blogs and links to specific tweets to archive by copying links direct from tweetdeck.
I am under no illusion that my workflow is far from perfect, but ultimately I think I've got something that works for me, it's a development of the system that Michael Axelsen was kind enough to share and because his videos saved me a massive amount of time wandering through the workflow wilderness I thought I'd create a (somewhat rambling) post for my blog sharing how I've taken on board his ideas incase there's anyone else out there who perhaps thinks this structure will work for them.
So what have I been doing the past 2 months? I've been axe sharpening.... I've got Papers2 up and running with nearly 700 PDF's which have been indexed from my previous document store, I've got EndNote configured to run across 3 different operating systems whilst maintaining integrity and within that system I've over 200 entries, most of which have been reviewed and have an initial set of research notes attached, I've got about 12,000 words down in Scrivener, most of which are structured notes, with ideas, questions, reminders plus jumbled panicked diagrams.... in amongst this chaotic activity has evolved something approaching structured thinking, I'm developing a workflow that allows me to become more rigourous in my thinking and should in the long run save me quite a lot of time over the coming years.
Is the axe as sharp as it can be then? No, not by a long way, I'm a great believer that every day is a school day and so I've been ploughing through various preparatory texts with the intention of improving my academic writing, improving thesis structure and critical reading/writing skills.... but that's a post for another day I think...






























































