![]() ![]() ![]() This includes comments on how things are working, notes from meetings with my supervisors, To Do lists and so on. I have a large ‘logbook’ for my main PhD work (it’s even got the logo of my University on it, and some pages at the back with information on Intellectual Property law), which I try and use as much as possible. Instead, I tend to make do with a few different systems for different parts of my work. I often wish for a system like the prototype that Philip developed as part of his PhD (see here), but that wasn’t suitable for use in production. These are probably the most important questions on the list, but it’s something that I’ve often struggled to do well. Do you have reliable to-do lists for your projects? So, starting with the first few questions:ġ. Do you have reliable ways of taking, organizing, and reflecting on notes as you’re working?Ģ. Questions include things like: Do you use source control? and Can you make a build in one step? Philip came up with a similar set of questions for research programmers (that is, people who program as part of their research work – which includes researchers in a very wide range of fields these days). Philip Guo, who writes a wonderful blog on his views and experiences of academia – including a lot of interesting programming stuff – came up with a research programming version of The Joel Test last summer, and since then I’ve been thinking of writing a series commenting on how well I fulfil each of the items on the test.įor those of you who haven’t come across The Joel Test – it’s a list of simple Yes/No questions you can answer to measure the quality of your software team. Robin's Blog How effective is my research programming workflow? The Philip Test – Part 1 March 10, 2014 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |