Chapter 40 — Teaching Notes

One-line purpose. Send the reader off well: show them, honestly, where Fortran work is, what the roles are called, why the skill is scarce and therefore valuable, and how to package what they built so the world can see it. This is the book's coda — the emotional and practical close, not a new-content chapter.

Key ideas to emphasize

  • The loop back to Chapter 1 is the spine of the chapter (Overview + What's Next). The reader sealed a one-sentence answer to "why learn Fortran?" in Exercise 1.28. This chapter asks them to break the seal and measure the gap. Make this explicit in class — it is the single most motivating beat in the whole book.
  • Honesty about the shortage (§40.3, the threshold concept "scarcity is leverage"). The "more jobs than people" claim is widely reported, not a statistic. Teach it exactly as Ch 1 taught the TOP500 claim: state the real, encouraging pattern precisely, and refuse to quote a number. The intellectual honesty is itself the lesson — and it is what makes the encouraging part credible.
  • Framing beats content on a résumé (§40.4). The identical experience reads as "legacy maintainer" or "HPC engineer" depending on framing. Modern Fortran + Python (f2py) + the HPC toolchain is the marketable profile; Fortran alone is not. This is theme 2 and theme 6 turned into a career skill.
  • The portfolio is an argument, not a pile of files (Project Checkpoint + CS-02). Every piece — repo, README, figure, abstract, résumé, application — must say the same true thing, consistently. The most common failure is invisible or inconsistent work, not weak work.
  • A first contribution is small (CS-01). Maintainers value small, correct, tested changes. Kill the myth that contributing means a heroic rewrite; the reader already has every skill the loop needs.

Misconceptions to preempt

  • "Fortran on a résumé is embarrassing." (No — in these sectors it is a credential; the mistake is framing it as legacy-only. §40.4.)
  • "The shortage means Fortran alone gets me a job." (No — it is a differentiator, not a guarantee; you also need domain + Python/C + HPC + SE. §40.3 pitfall.)
  • "Fortran runs the supercomputers' operating systems." (No — the OS is Linux/C; the science is often Fortran. Ch 1 honesty, restated.)
  • "Contributing to a famous code requires a brilliant big change." (No — small/correct/tested is the gift. CS-01.)
  • "I can put a benchmark I didn't run on my résumé." (No — in these sectors the reader can tell; one unsupportable claim discredits the honest ones. §40.4.)
  • "Code with no license is fine to share." (No — it is legally unusable by others. Checkpoint / CS-02.)

A live demonstration (10 minutes)

Compile and run code/example-01-skills-inventory.f90 in front of the class (all flags .true. → 8 of 8, 100.0%). Then edit two flags to .false. live and rerun (→ 6 of 8, 75.0%) — the readiness is just count over a component array, a one-line synthesis of Ch 5 + Ch 9 + Ch 7. Then open code/project-checkpoint.f90, point at the header abstract block, and run it to show the same validated 5×5 result they hand-computed back in Ch 24 — the whole book, closing on the number it opened the project with. Three minutes of "this is you" followed by "this is the thing you built" lands the chapter.

Class-time budget (~40 min; this is a short, discussion-heavy closer)

  • 5 min: Overview — the loop back to Ex 1.28; ask who still has their sealed sentence.
  • 8 min: §40.1 — who employs Fortran programmers (the sector table); honesty about "runs everything."
  • 8 min: §40.2 — the role spectrum (domain scientist → computational scientist → HPC engineer → RSE).
  • 6 min: §40.3 — the shortage as reported pattern; "scarcity is leverage."
  • 6 min: §40.4 — résumé framing; the legacy-vs-HPC reframe live.
  • 5 min: §40.5 + Checkpoint — packaging the portfolio; the four artifacts.
  • 2 min: the send-off (What's Next) — read the last paragraph aloud.

Prerequisites to review

Chapter 1 (the "not dead" argument + Ex 1.28 — reread the sealed-answer prompt). Chapter 15 (f2py / the Fortran+Python pairing — the résumé keystone). Chapter 36 (navigating a big code — for CS-01). Chapter 38 (the capstone — the portfolio piece being packaged). No new Fortran features; the coding is deliberately light and synthetic.

Connections

Back: essentially the whole book — this is the synthesis chapter. Load-bearing: Ch 1 (loop closed), Ch 15 (Python pairing), Ch 36 (read a big code), Ch 37 (test it), Ch 38 (the artifact). Forward: none — this is the last chapter. Point students at the appendices (reference) and the fortran-lang community (Ch 39) as where to go from here.