Chapter 4 — Academic writing

Chapter 4 — Academic writing

Lesson map

Lesson 04 published. Map, example, EX010.

flowchart TD
  N0["Learning outcomes"]
  N1["4.1 Structuring an argument"]
  N2["4.2 Citing sources accurately"]
  N3["4.3 Writing for mixed audiences"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4
  N4 --> EX["Worked example"]
  EX --> Q["Exercise EX010"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["4.1 Structuring an argument"]
  N2["4.2 Citing sources accurately"]
  N3["4.3 Writing for mixed audiences"]
  N4["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> Q["EX010"]

[Learning outcomes]
    |
    v
[4.1 Structuring an argument]
    |
    v
[4.2 Citing sources accurately]
    |
    v
[4.3 Writing for mixed audiences]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX010]

Learning outcomes

You will (1) structure an argument; (2) cite sources accurately; (3) write clearly for mixed audiences.

4.1 Structuring an argument

Sofia's first essay asks whether a small cooperative should use a blockchain for vouchers at all. Dr Asante teaches a simple structure: state the claim, give reasons, support each reason with evidence, address the strongest objection, and conclude. Her claim is cautious: a permissioned ledger may help if members want shared, tamper-evident records, but a normal database might be enough. She lists reasons on both sides before writing a word. Structure keeps an argument honest, because a missing objection becomes visible as an empty section, and readers can see exactly which evidence supports each step of the reasoning.

4.2 Citing sources accurately

Sofia cites Nakamoto's 2008 paper for the idea of a public, append-only chain of blocks and NIST IR 8202 for an overview of blockchain types and their trade-offs. She records author, title, year and where the source can be found, and she checks each citation against the original rather than a summary. Dr Asante warns that inaccurate citations are a form of error that readers cannot easily detect. In security writing, a wrong citation can lead someone to rely on a claim no source actually makes. Accurate citation is therefore part of being trustworthy, not just a formatting rule.

4.3 Writing for mixed audiences

The cooperative's board includes a baker, a retired teacher and a nurse, none of them technical. Sofia rewrites her essay's summary in plain language: what the voucher system does, what could go wrong, and what decision the board needs to make. She replaces jargon with short explanations, such as calling a private key the secret that proves who may spend vouchers. Each technical term she keeps is defined once. The board's questions after reading show that they understood the trade-off. Writing for the people who decide is a security skill, because unclear advice leads to poor decisions.

Worked example

Sofia argues cautiously for a permissioned ledger, cites Nakamoto and NIST IR 8202 from the originals, and writes a plain summary the board understands.

Synthetic case. The essay and board are synthetic; Nakamoto (2008) and NIST IR 8202 are real sources.

Errors and limits

Citing a summary instead of the original source risks repeating claims the source never made.

Exercises

• EX010 — Essay claim. What is Sofia's cautious claim? Rubric: 3 = a ledger may help if members want shared tamper-evident records;; 2 = maybe;; 1 = always use blockchain;; 0 = none.
• EX011 — Sources used. Which two sources does she cite? Rubric: 3 = Nakamoto 2008 and NIST IR 8202;; 2 = one of them;; 1 = a blog;; 0 = none.
• EX012 — Plain term. How does she explain a private key to the board? Rubric: 3 = the secret that proves who may spend vouchers;; 2 = a secret;; 1 = a password reset;; 0 = none.

Synthesis

Clear structure, accurate citation and plain language make security advice usable.

Continue studying — chapter 04 of 40

← Chapter 03 (draft) · Course chapter index · Chapter 05 (draft) →