chgaeMerge branch 'master' of https://github.com/nipunbatra/phd-bootcamp-2017

Author: nipunbatra

Readme.md

@@ -1,20 +1,20 @@
 ## Research Methods in Computer Science
 
 This repository contains the material I have used for a 2 hour bootcamp on research methods in CS. I have conducted this session twice (August 2018 at IIT Gandhinagar and July 2017 at IIIT Delhi). Here is the [video recording](https://www.youtube.com/watch?v=LoCoplWgvp4
-) for the IIT Gandhinagar instantiation.
+) for the IIT Gandhinagar instantiation. You can also find a VideoKen version of the video [here](https://videoken.com/embed/LoCoplWgvp4), which includes phrase cloud, table of contents and more.
 
 
 ### Contents
 
 I took four exercise and example driven sessions on:
 
-1. Writing better emails: I took an example driven approach of writing good emails. I showed some poor and some good emails that I have written. We discussed a few fundamental characteristics of a good email. We did three hands-on exercise for writing e-mail to: i) potential advisor, ii) reporting results to advisor, iii) seeking help on a research project from someone outside the institute.
+1. [Writing better emails](Email101.pdf): I took an example driven approach of writing good emails. I showed some poor and some good emails that I have written. We discussed a few fundamental characteristics of a good email. We did three hands-on exercise for writing e-mail to: i) potential advisor, ii) reporting results to advisor, iii) seeking help on a research project from someone outside the institute.
 
-2. Towards better paper abstracts: I discussed the general structuring of research papers. We took case study on the constitution of a good paper abstract. We looked at potential scientific flaws that can be seen from the abstract itself. We did a few hands-on exercises. 
+2. [Towards better paper abstracts](RM101.pdf): I discussed the general structuring of research papers. We took case study on the constitution of a good paper abstract. We looked at potential scientific flaws that can be seen from the abstract itself. We did a few hands-on exercises. 
 
-3. Thinking like a scientist: This session was a continuation of the previous one. We discussed the scientific method with the help of a trivial example. We did a few hands-on exercises where the students were asked to present hypothesis, observation,  and experimental design for few problems.
+3. [Thinking like a scientist](ScientificMethod101.pdf): This session was a continuation of the previous one. We discussed the scientific method with the help of a trivial example. We did a few hands-on exercises where the students were asked to present hypothesis, observation,  and experimental design for few problems.
 
-4. Debugging like a pro: This was also an example driven session. We looked at StackOverflow questions and understood the characteristics of good questions. These good questions have a much higher chance of being debugged correctly in quick time.
+4. [Debugging like a pro](Debug101.pdf): This was also an example driven session. We looked at StackOverflow questions and understood the characteristics of good questions. These good questions have a much higher chance of being debugged correctly in quick time.
 
 ### Feedback