Related Work and Code Tests

Thought it really didn't seem like it could take so long, I spent most of this week working on the related work section of the paper I'm writing. Since I don't really know much about the past work in any of the areas I am writing about (Automated grading, static code analysis, code smells and crowdsourcing), I felt like I was doing some really inefficient AI search, going down many trails of references before I could decide which papers are useful and should be included. I now have a general idea of the work and people in these spaces and feel like I might be getting a better handle on how to work through a related work section (though getting faster at it would definitely be beneficial!) With the related works section in paragraph form, the main sections I have left to convert from outline to draft form are the introduction, results and conclusions, which is pretty exciting, considering there are still three weeks until the deadline! In order to add something more conclusive to the results section, I've been working on converting the mentor rules to code tests using Aaron's work and almost have all 21 of the first task rules done!