Writing up research is a
complicated, messy process!
Data Statistical results
Data Statistical results
Fieldwork Interviews Analysis
Data Statistical results
Fieldwork Interviews Analysis
Figures Images Tables
Data Statistical results
Fieldwork Interviews Analysis
Figures Images Tables
Citations
Data Statistical results
Fieldwork Interviews Analysis
Figures Images Tables
Citations
Your actual words
Data Statistical results
Fieldwork Interviews Analysis
Figures Images Tables
Citations
Your actual words
Each of these comes from a different place!
Spending a full day of writing in the mountains or the beach with a notebook sounds cool, but it's really infeasible with any sort of academic writing - too much going on!
The Office model
Put everything in one document
The Office model
Put everything in one document
The Engineering model
Embrace the bittiness and compile it all at the end
Everything lives in
one .docx
file
Drag images in
Copy/paste stats from R or Stata
Connect Word to Zotero or Endnote
Track versions with filenames: ms.docx
, ms2_final.docx
, ms2_final_final.docx
Final output = .docx
file
Everything lives separately and is combined in the end
Type text in a plain text document
Import images automatically
Import stats automatically from
R scripts (.R
or .Rmd
) or .do
files
Store citations in reference manager
Track versions with git
Final output = whatever you want (Word, PDF, HTML)
The Office model can be clunky and you'll
inevitably forget to update figures, tables, results, etc.
The Office model can be clunky and you'll
inevitably forget to update figures, tables, results, etc.
BUT
The Office model can be clunky and you'll
inevitably forget to update figures, tables, results, etc.
BUT
The whole world runs on Word
The Office model can be clunky and you'll
inevitably forget to update figures, tables, results, etc.
BUT
The whole world runs on Word
Even if you're a strict Engineering person,
you'll still collaborate with Office people!
The Office model can be clunky and you'll
inevitably forget to update figures, tables, results, etc.
BUT
The whole world runs on Word
Even if you're a strict Engineering person,
you'll still collaborate with Office people!
Coauthors will work in Word, advisers will give comments
and track changes in Word, journals will demand final Word files
The Engineering model is definitely more fiddly
The Engineering model is definitely more fiddly
BUT
The Engineering model is definitely more fiddly
BUT
There's less cognitive load!
The Engineering model is definitely more fiddly
BUT
There's less cognitive load!
No need to copy/paste new results,
add updated figures, reformat citation, etc.
The Engineering model is definitely more fiddly
BUT
There's less cognitive load!
No need to copy/paste new results,
add updated figures, reformat citation, etc.
There's a record of everything you do!
The Engineering model is definitely more fiddly
BUT
There's less cognitive load!
No need to copy/paste new results,
add updated figures, reformat citation, etc.
There's a record of everything you do!
Your findings are reproducible by anyone (and yourself!)
Debt:GDP ratio
90%+ → −0.1% growth
Debt:GDP ratio
90%+ → −0.1% growth
Debt:GDP ratio = 90%+ → 2.2% growth (!!)
Septin 2
Membrane-Associated Ring Finger (C3HC4) 1
2310009E13
Septin 2
Membrane-Associated Ring Finger (C3HC4) 1
2310009E13
Septin 2
Membrane-Associated Ring Finger (C3HC4) 1
2310009E13
20% of genetics papers between 2005–2015 (!!!)
Don't touch the raw data
If you do, explain what you did!
Don't touch the raw data
If you do, explain what you did!
Use self-documenting, reproducible code
The whole point of this Engineering model! (R Markdown!)
Don't touch the raw data
If you do, explain what you did!
Use self-documenting, reproducible code
The whole point of this Engineering model! (R Markdown!)
Use open formats
Use .csv, not .xlsx
LATEX
LATEX
You might know LaTeX—it's a scientific typesetting language
LATEX
You might know LaTeX—it's a scientific typesetting language
Great! It's a way to do the Engineering model
LATEX
You might know LaTeX—it's a scientific typesetting language
Great! It's a way to do the Engineering model
Run latexmk
from the terminal or click the "compile" button in your TeX editor and you'll stitch together all your separate writing, tables, images, and citations
LATEX
You might know LaTeX—it's a scientific typesetting language
Great! It's a way to do the Engineering model
Run latexmk
from the terminal or click the "compile" button in your TeX editor and you'll stitch together all your separate writing, tables, images, and citations
HOWEVER, the world runs on .docx
LATEX
You might know LaTeX—it's a scientific typesetting language
Great! It's a way to do the Engineering model
Run latexmk
from the terminal or click the "compile" button in your TeX editor and you'll stitch together all your separate writing, tables, images, and citations
HOWEVER, the world runs on .docx
There are ways to convert from .tex
to .docx
, but they're a pain
If you want to be able to write in LaTeX, but also have HTML for a blog post later, and also have a Word file for a journal later, you have to learn (and write with!) all these!
If you want to be able to write in LaTeX, but also have HTML for a blog post later, and also have a Word file for a journal later, you have to learn (and write with!) all these!
Format | LaTeX | HTML | Word |
---|---|---|---|
Bold | \textbf{Something} | <b>Something</b> | Click on stuff |
Heading 2 | \subsection{Something} | <h2>Something</h2> | Click on stuff |
Link | \href{google.com}{Link} | <a href="google.com">Link</a> | Click on stuff |
Citation | \cite{Heiss2020} | lolz | lolz |
Math | y = \beta_0 + \beta_1 x_1 | lolz | Equation editor |
Solution: Use a universal syntax
Solution: Use a universal syntax
Write with one simplified syntax and
convert from that to whatever output you want.
Solution: Use a universal syntax
Write with one simplified syntax and
convert from that to whatever output you want.
Format | Markdown |
---|---|
Bold | **Something** |
Heading 2 | ## Something |
Link text | [Link](google.com) |
Citation | @Heiss2020 |
Math | y = \beta_0 + \beta_1 x_1 |
Solution: Use a universal syntax
Write with one simplified syntax and
convert from that to whatever output you want.
Format | Markdown |
---|---|
Bold | **Something** |
Heading 2 | ## Something |
Link text | [Link](google.com) |
Citation | @Heiss2020 |
Math | y = \beta_0 + \beta_1 x_1 |
The magic glue that makes this all work
The magic glue that makes this all work
# To HTMLpandoc manuscript.md -o manuscript.html# To Wordpandoc manuscript.md -o manuscript.docx# To PDF (through LaTeX)pandoc manuscript.md -o manuscript.pdf
Text editor
Text editor
(R) Markdown
Text editor
(R) Markdown
pandoc
Text editor
(R) Markdown
pandoc
(Not in this class: Automation with Makefiles)
Text editor
(R) Markdown
pandoc
(Not in this class: Automation with Makefiles)
(Not in this class: Version control with git/GitHub)
Let's play with
Markdown and pandoc!
Writing up research is a
complicated, messy process!
Keyboard shortcuts
↑, ←, Pg Up, k | Go to previous slide |
↓, →, Pg Dn, Space, j | Go to next slide |
Home | Go to first slide |
End | Go to last slide |
Number + Return | Go to specific slide |
b / m / f | Toggle blackout / mirrored / fullscreen mode |
c | Clone slideshow |
p | Toggle presenter mode |
t | Restart the presentation timer |
?, h | Toggle this help |
o | Tile View: Overview of Slides |
Esc | Back to slideshow |
Writing up research is a
complicated, messy process!
Data Statistical results
Data Statistical results
Fieldwork Interviews Analysis
Data Statistical results
Fieldwork Interviews Analysis
Figures Images Tables
Data Statistical results
Fieldwork Interviews Analysis
Figures Images Tables
Citations
Data Statistical results
Fieldwork Interviews Analysis
Figures Images Tables
Citations
Your actual words
Data Statistical results
Fieldwork Interviews Analysis
Figures Images Tables
Citations
Your actual words
Each of these comes from a different place!
Spending a full day of writing in the mountains or the beach with a notebook sounds cool, but it's really infeasible with any sort of academic writing - too much going on!
The Office model
Put everything in one document
The Office model
Put everything in one document
The Engineering model
Embrace the bittiness and compile it all at the end
Everything lives in
one .docx
file
Drag images in
Copy/paste stats from R or Stata
Connect Word to Zotero or Endnote
Track versions with filenames: ms.docx
, ms2_final.docx
, ms2_final_final.docx
Final output = .docx
file
Everything lives separately and is combined in the end
Type text in a plain text document
Import images automatically
Import stats automatically from
R scripts (.R
or .Rmd
) or .do
files
Store citations in reference manager
Track versions with git
Final output = whatever you want (Word, PDF, HTML)
The Office model can be clunky and you'll
inevitably forget to update figures, tables, results, etc.
The Office model can be clunky and you'll
inevitably forget to update figures, tables, results, etc.
BUT
The Office model can be clunky and you'll
inevitably forget to update figures, tables, results, etc.
BUT
The whole world runs on Word
The Office model can be clunky and you'll
inevitably forget to update figures, tables, results, etc.
BUT
The whole world runs on Word
Even if you're a strict Engineering person,
you'll still collaborate with Office people!
The Office model can be clunky and you'll
inevitably forget to update figures, tables, results, etc.
BUT
The whole world runs on Word
Even if you're a strict Engineering person,
you'll still collaborate with Office people!
Coauthors will work in Word, advisers will give comments
and track changes in Word, journals will demand final Word files
The Engineering model is definitely more fiddly
The Engineering model is definitely more fiddly
BUT
The Engineering model is definitely more fiddly
BUT
There's less cognitive load!
The Engineering model is definitely more fiddly
BUT
There's less cognitive load!
No need to copy/paste new results,
add updated figures, reformat citation, etc.
The Engineering model is definitely more fiddly
BUT
There's less cognitive load!
No need to copy/paste new results,
add updated figures, reformat citation, etc.
There's a record of everything you do!
The Engineering model is definitely more fiddly
BUT
There's less cognitive load!
No need to copy/paste new results,
add updated figures, reformat citation, etc.
There's a record of everything you do!
Your findings are reproducible by anyone (and yourself!)
Debt:GDP ratio
90%+ → −0.1% growth
Debt:GDP ratio
90%+ → −0.1% growth
Debt:GDP ratio = 90%+ → 2.2% growth (!!)
Septin 2
Membrane-Associated Ring Finger (C3HC4) 1
2310009E13
Septin 2
Membrane-Associated Ring Finger (C3HC4) 1
2310009E13
Septin 2
Membrane-Associated Ring Finger (C3HC4) 1
2310009E13
20% of genetics papers between 2005–2015 (!!!)
Don't touch the raw data
If you do, explain what you did!
Don't touch the raw data
If you do, explain what you did!
Use self-documenting, reproducible code
The whole point of this Engineering model! (R Markdown!)
Don't touch the raw data
If you do, explain what you did!
Use self-documenting, reproducible code
The whole point of this Engineering model! (R Markdown!)
Use open formats
Use .csv, not .xlsx
LATEX
LATEX
You might know LaTeX—it's a scientific typesetting language
LATEX
You might know LaTeX—it's a scientific typesetting language
Great! It's a way to do the Engineering model
LATEX
You might know LaTeX—it's a scientific typesetting language
Great! It's a way to do the Engineering model
Run latexmk
from the terminal or click the "compile" button in your TeX editor and you'll stitch together all your separate writing, tables, images, and citations
LATEX
You might know LaTeX—it's a scientific typesetting language
Great! It's a way to do the Engineering model
Run latexmk
from the terminal or click the "compile" button in your TeX editor and you'll stitch together all your separate writing, tables, images, and citations
HOWEVER, the world runs on .docx
LATEX
You might know LaTeX—it's a scientific typesetting language
Great! It's a way to do the Engineering model
Run latexmk
from the terminal or click the "compile" button in your TeX editor and you'll stitch together all your separate writing, tables, images, and citations
HOWEVER, the world runs on .docx
There are ways to convert from .tex
to .docx
, but they're a pain
If you want to be able to write in LaTeX, but also have HTML for a blog post later, and also have a Word file for a journal later, you have to learn (and write with!) all these!
If you want to be able to write in LaTeX, but also have HTML for a blog post later, and also have a Word file for a journal later, you have to learn (and write with!) all these!
Format | LaTeX | HTML | Word |
---|---|---|---|
Bold | \textbf{Something} | <b>Something</b> | Click on stuff |
Heading 2 | \subsection{Something} | <h2>Something</h2> | Click on stuff |
Link | \href{google.com}{Link} | <a href="google.com">Link</a> | Click on stuff |
Citation | \cite{Heiss2020} | lolz | lolz |
Math | y = \beta_0 + \beta_1 x_1 | lolz | Equation editor |
Solution: Use a universal syntax
Solution: Use a universal syntax
Write with one simplified syntax and
convert from that to whatever output you want.
Solution: Use a universal syntax
Write with one simplified syntax and
convert from that to whatever output you want.
Format | Markdown |
---|---|
Bold | **Something** |
Heading 2 | ## Something |
Link text | [Link](google.com) |
Citation | @Heiss2020 |
Math | y = \beta_0 + \beta_1 x_1 |
Solution: Use a universal syntax
Write with one simplified syntax and
convert from that to whatever output you want.
Format | Markdown |
---|---|
Bold | **Something** |
Heading 2 | ## Something |
Link text | [Link](google.com) |
Citation | @Heiss2020 |
Math | y = \beta_0 + \beta_1 x_1 |
The magic glue that makes this all work
The magic glue that makes this all work
# To HTMLpandoc manuscript.md -o manuscript.html# To Wordpandoc manuscript.md -o manuscript.docx# To PDF (through LaTeX)pandoc manuscript.md -o manuscript.pdf
Text editor
Text editor
(R) Markdown
Text editor
(R) Markdown
pandoc
Text editor
(R) Markdown
pandoc
(Not in this class: Automation with Makefiles)
Text editor
(R) Markdown
pandoc
(Not in this class: Automation with Makefiles)
(Not in this class: Version control with git/GitHub)
Let's play with
Markdown and pandoc!