diff options
| author | Mohit Agarwal <mohit.agarwal@sky.com> | 2025-05-15 21:32:33 +0100 |
|---|---|---|
| committer | Mohit Agarwal <mohit.agarwal@sky.com> | 2025-05-15 21:32:33 +0100 |
| commit | f9f8e9323144f87d95407b29a9f185cfc4c7bc8a (patch) | |
| tree | e3b2153e1e45b21d066391bef957bd89f066e80b | |
| parent | 3d984961f713dccfc64c9be317dfc2719e2a21da (diff) | |
Writing
| -rw-r--r-- | Makefile | 17 | ||||
| -rw-r--r-- | navbar.html | 3 | ||||
| -rw-r--r-- | studies/exams.md | 29 | ||||
| -rw-r--r-- | studies/subjects/computer-science.md | 2 |
4 files changed, 49 insertions, 2 deletions
diff --git a/Makefile b/Makefile new file mode 100644 index 0000000..be61a52 --- /dev/null +++ b/Makefile @@ -0,0 +1,17 @@ +TARGETS=studies/exams.html\ + studies/subjects/computer-science.html +TARGETS_PDF=$(TARGETS:%html=%pdf) + +default: $(TARGETS) +pdf: $(TARGETS_PDF) + +%.html: %.md + pandoc "$^" -o "$@"\ + -s\ + --css="https://mohit.uk/document.css"\ + -B "navbar.html" +%.pdf: %.md + pandoc "$^" -o "$@"\ + --pdf-engine=pdfroff +clean: + rm -rf $(TARGETS) diff --git a/navbar.html b/navbar.html index 7536591..8ae216d 100644 --- a/navbar.html +++ b/navbar.html @@ -1,6 +1,7 @@ <a href="/how-to-st-andrews"> - <h1> How to St Andrews</h1> + <h2> How to St Andrews</h2> </a> <p> A guide to getting by for the university student. </p> +<hr> diff --git a/studies/exams.md b/studies/exams.md new file mode 100644 index 0000000..9e3ef48 --- /dev/null +++ b/studies/exams.md @@ -0,0 +1,29 @@ +--- +title: Exams +date: May 2025 +--- +``` +Written by Mohit Agarwal Class of 2025 +``` + +Exams are easily one of the most daunting endeavours a student faces +at St Andrews. Yet, with some straightforward preparation, they are +not as difficult as they might first seem. Exams can be categorized by +two metrics: + +* In-person _v._ take-home exams +* Technical answers _v._ written answers + +## In-person exams + +In-person exams require you to _memorize_ information, so that you can +recall it in the exam and answer on the basis of this knowledge. You +might be required to memorize course content (e.g., theorems, +processes, or different case studies) or be required be familiar with +a reading list, which questions might be asked about. + +## Take home exams + +## Technical answers (Maths, Physics, etc.) + +## Written answers (Philosophy, Art History, etc.) diff --git a/studies/subjects/computer-science.md b/studies/subjects/computer-science.md index d49568a..2d7409f 100644 --- a/studies/subjects/computer-science.md +++ b/studies/subjects/computer-science.md @@ -28,7 +28,7 @@ _every single_ word on the page is not crossed out. ## Doing exams -Exams are daunting. See (general exam advice)[../exams.html] for +Exams are daunting. See [general exam advice](../exams.html) for broader advice. For computer science in particular, focus on getting very familiar with the sorts of questions that might be asked. Always attend lecturers' exam revision sessions to ask specific questions: |