Ch40 Discussion

Discussion Guide

Warm-up (think–pair–share, 5 min). "Find the one-sentence answer to 'why learn Fortran?' you sealed in Exercise 1.28. Read it to your partner. What would you say now, and how is it different?" This is the chapter's core beat; give it real time. Surfaces how far the class has come and motivates everything else.

Main discussion (15–20 min). 1. Honest scarcity. Present the shortage claim and ask: why does this book refuse to put a number on it, and why is that refusal more persuasive than a statistic would be? Connect to the Ch 1 discipline about TOP500. Then: "scarcity is leverage" — over what, exactly? (Which jobs, what pay, how much your judgment is trusted.) Push students to distinguish "differentiator" from "guarantee." 2. The framing experiment. Put "Maintained Fortran code" and the HPC-reframed bullet (§40.4, Modern-vs-Legacy callout) side by side. Same experience — why does the second get an interview and the first get filed? Have the class reframe a weak bullet of their own live. Ties theme 2 (modern language) to a concrete skill. 3. Consistency of the portfolio (CS-02). "Give me two parts of a portfolio that could contradict each other." (Résumé says MPI; repo has none. Abstract claims validation; no test exists.) Why does an inconsistency cost more trust than a modest-but-true claim? This is citation honesty (Ch 1, Ch 7 of the style bible) applied to the reader's own self-presentation.

Group activity (10 min). In pairs, students draft the README metadata card and the one-paragraph abstract for their heat solver (Exercises 40.7, 40.9), then swap and "review" as a maintainer would: is every clause true of the code? Is there a Validation section? Is there a LICENSE? Peer review of a portfolio against the reality of the code is the exact skill CS-02 teaches — and a transferable, real-world one.

Exit ticket. "Name the two career roles this chapter defined, and give the one framing rule for putting Fortran on a résumé." (Computational scientist / research software engineer; frame it as modern HPC paired with Python + the HPC toolchain, never alone. Anything capturing role-pair + pairing-rule is a pass.)

A closing note for the instructor. This is the last thing the class reads. However you run the session, end by reading the final paragraph of §40 aloud — "Fortran is not dead — and neither, it turns out, is the future of the people who take the trouble to learn it well." Let them leave on it. The point of forty chapters was never the syntax; it was to make them one of the few who can do this work. Tell them so.