title | author | date | output | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Your Thesis is Software |
Simon Goring |
23/10/2020 |
|
ideas + data + text + formatting
IDEAS + data + text + formatting
- We have expectations and hypotheses that we aim to test
- Our project design is based on assumptions
ideas + DATA + text + formatting
- Data is the product of experimental design and has constraints
- Data collection and processing is part of a workflow
ideas + data + TEXT + formatting
- Text depends on results from analysis
- Text is structured, ordered and order has meaning
ideas + data + text + FORMATTING
- Formatting transforms text and gives meaning
- Formatting makes it all look pretty
- Your thesis office will not accept a thesis with the wrong formatting
- ideas (usually sus)
- data (data)
- text (code)
- formatting (styling)
- Working on Features
- Testing Assumptions
- Building Workflows
-
Working on Features
- Thesis elements are "units" (a chapter, a statistical test, a graph, a table)
- A unit can be its own file
- A unit has expected inputs & outputs
- A unit can have versions
-
Testing Assumptions
- We know things about our data (n = ??, all values are positive)
- We write things about our results (p < 0.5)
- Results and data might change as features change
-
Building Workflows
- The final thesis is the sum of units
- Writing units that "just work" takes planning
- Writing units that "just work" makes changing them easier
- Writing units that "just work" makes fixing them easier
- An introduction to software tools & concepts
- A resource & community for your ongoing work
- A tool to help you re-think your work going forward
- An introduction to
git
as a tool for version control - An introduction to markdown (and RMarkdown)
- Data access and processing tricks in documents
- A collection of tips & tricks