Chapter 4 — Academic writing
Lesson map
Lesson 04 published. Map, example, EX010.
flowchart TD
N0["Learning outcomes"]
N1["4.1 Purpose"]
N2["4.2 Structure"]
N3["4.3 Citing"]
N4["4.4 Precision"]
N5["4.5 Overstatement"]
N6["4.6 Revising"]
N7["4.7 Feedback"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7
N7 --> EX["Worked example"]
EX --> Q["Exercise EX010"]
Logical drawing
flowchart LR
N0["Learning outcomes"]
N1["4.1 Purpose"]
N2["4.2 Structure"]
N3["4.3 Citing"]
N4["4.4 Precision"]
N5["4.5 Overstatement"]
N6["4.6 Revising"]
N7["4.7 Feedback"]
N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> N6 --> N7 --> Q["EX010"]
[Learning outcomes]
|
v
[4.1 Purpose]
|
v
[4.2 Structure]
|
v
[4.3 Citing]
|
v
[4.4 Precision]
|
v
[4.5 Overstatement]
|
v
[4.6 Revising]
|
v
[4.7 Feedback]
|
v
[Worked example] --> [Exercise EX010]
Learning outcomes
You will (1) write clear academic and technical prose about cloud security; (2) cite sources correctly; (3) structure arguments; (4) avoid overstatement.
4.1 Purpose
Samuel's thesis and reports must persuade careful readers with evidence. Academic writing states claims, supports them with sources or data, and acknowledges limits.
His project report on the registry exposure will be read by Tom, by university managers and by Dr Jensen as an assessor. Each needs to see what was found, how it was found and what remains uncertain. Academic writing's habits of stating claims and evidence serve all three readers at once. Writing for all three also forces him to explain terms such as "anonymous pull" in one plain sentence the first time they appear.
4.2 Structure
Each paragraph makes one point: a topic sentence, evidence, and a link to the argument. Sections follow a logical order from problem to conclusion.
A paragraph in Samuel's report begins: "Two of four repositories allowed anonymous pull." The evidence follows, his anonymous test and the registry settings export, and then the link: this exposed records-api and its connection string. Readers can stop after the first sentence and still know the point. His report's sections run from the finding, through causes and fixes, to what remains unknown, so each builds on the last.
4.3 Citing
Standards and papers are cited in a consistent style with links or DOIs. Samuel cites NIST SP 800-190 when discussing container image risks and the Kubernetes documentation when describing Pod Security Standards.
Citing the standard lets readers check that Samuel's description of image risks matches the source. Including a link or DOI makes that check quick. He also records the version of the Kubernetes documentation he used, since its pages are updated and an older description of a feature may no longer apply.
4.4 Precision
"Anonymous pull was enabled on two of four repositories" is better than "the registry was insecure".
The precise version gives the count, the denominator and the setting, so a reader can verify it and see its size. The vague version invites argument: insecure in what way, and how badly? Samuel goes through his draft looking for adjectives such as "insecure" or "weak" and replaces each with the finding behind it. Precision also helps when progress is reported: "zero of four" next month is clearly better than "two of four", while "less insecure" means little.
4.5 Overstatement
"No evidence of misuse was found in available logs" is accurate; "no misuse occurred" is not, since logging was missing.
The difference matters in the opening case because audit logging was off in one account. Claiming no misuse would assert something the evidence cannot show. The accurate statement tells readers exactly where the gap is, which is also why fixing logging became one of the first actions. Samuel's report puts the gap in its own sentence, near the start, so no reader can miss it or assume the logs covered the whole period.
4.6 Revising
Samuel reads drafts aloud, removes unnecessary words and checks every number against its source.
Checking numbers caught one error in his first report: he had written three repositories instead of two, copying from an early note. Reading aloud found sentences that were too long to follow. Removing unnecessary words shortened his executive summary from a page to half a page without losing any finding. He keeps the earlier draft so Dr Jensen can see what changed between versions and why each change was made.
4.7 Feedback
Dr Jensen comments on drafts within a week; Samuel keeps a list of recurring feedback to avoid repeating mistakes.
After three essays, his list included vague adjectives, missing denominators and claims stronger than the evidence. Before submitting each new draft, he checks it against the list. Dr Jensen's comments gradually moved from these basics to questions about argument and evidence, which showed the list was working. He also notes feedback he disagreed with and why, then discusses it at the next meeting, so the list records decisions rather than only instructions.
Using sources well
Samuel learns to prefer primary sources: the standard itself, not a blog summary of it. When a secondary source is useful, he checks its claims against the original. He also records the version and access date for web documents, since cloud documentation changes often. A short source log beside each essay lists each source, why it was used and where in the text it supports a claim.
Worked example
In his first essay, Samuel writes that the registry exposure "had no impact". Dr Jensen asks how he knows. He revises to "no unusual access was found in the logs that existed; the period without logs cannot be assessed", a statement the evidence supports.
Synthetic case. Essays are synthetic.
Errors and limits
Absence of evidence is not evidence of absence when logging was missing.
Exercises
- EX010 — Paragraph structure. Describe a good paragraph. Rubric: 3 = topic sentence, evidence, link; 2 = two; 1 = one; 0 = none.
- EX011 — Accurate phrasing. Why is "no misuse occurred" an overstatement? Rubric: 3 = logs missing for part of the period; 2 = partial; 1 = vague; 0 = none.
- EX012 — Revision habit. Name a revision habit. Rubric: 3 = read aloud, cut words, check numbers; 2 = one; 1 = vague; 0 = none.
Synthesis
Clear, sourced and modest writing persuades careful readers.
Continue studying — chapter 04 of 40
← Chapter 03 (draft) · Course chapter index · Chapter 05 (draft) →