Execution Timelines and Attainable Milestones

Metadata

Field	Value
source	../Assembly-Fortran-Comparison.md
document	Comparative Strategic Analysis of Assembly and Modern Fortran: Pedagogical Yield, Toolchain Friction, and Industry Trajectories
kind	section-lead
parent
lines	5-15
findings	D01-C3 D01-M5

The three-month acquisition trajectory differs substantially between Assembly and Modern Fortran due to variations in cognitive load, scope, and execution feedback loops. A dedicated learner committing consistent weekly effort must navigate distinct developmental phases, transitioning from fundamental syntax or instruction semantics to real-world structural fluency.

Week Interval	Assembly Language Pathway (x86-64 / RISC-V)	Modern Fortran Pathway (Fortran 2008–2023)
Weeks 1–4	Binary representations; CPU register sets; basic arithmetic and logical operations; stack pointer manipulation; AMD64 System V calling conventions2.	Free-form syntax; strong typing; dynamic array allocations; intrinsic mathematical functions; modular code organization; file I/O4.
Weeks 5–8	Memory addressing modes; control-flow recovery; stack frame preservation; pointer indirection; direct linking of compiled C routines to assembly subroutines7.	User-defined derived types; procedure interfaces; pure functions; OpenMP multithreading pragmas; integration of BLAS and LAPACK linear algebra libraries3.
Weeks 9–12	Disassembly inspection in Ghidra; binary patching; tracking SIMD vector registers; profiling branch mispredictions and microarchitectural pipeline stalls11.	Native distributed memory scaling via coarrays; do concurrent multi-core execution; build orchestration using the Fortran Package Manager (fpm)3.
Attainable Milestone	Reading and auditing decompiled binaries, mapping disassembled blocks to high-level code, and identifying micro-optimization bottlenecks11.	Architecting and running an end-to-end, parallelized partial differential equation solver or matrix simulation engine from scratch4.

Review findings for this part

The findings come from ../../findings/ (pass 1). The script matches them to this part by source line.

ID	Severity	Evidence	Status	Location	Problem
D01-C3	critical	DOC	open	L14, L21–24, L183–187	Claim: 90-day milestones. Problem: The comparison is not like-for-like. The Fortran milestone is authoring a parallel PDE (partial differential equation) solver “from scratch”, “production-ready”. The Assembly milestone is only reading disassembly. That framing builds the conclusion (“Fortran ships software”) into the premise. Assembly learners often author working programs in 90 days, for example with [1], “OS in 1,000 Lines”. The document itself cites [1].
D01-M5	major	KNOW VERIFY	verify	L24, L59, L13	Claim: Coarrays give SPMD “without relying on third-party message-passing”. Problem: In practice this is false. GFortran coarrays need OpenCoarrays, built on MPI (a third-party message-passing library). The Intel implementation uses Intel MPI. MPI+OpenMP dominates production HPC (high-performance computing), so coarrays are niche. The plan puts “distributed memory scaling via coarrays” in weeks 9 to 12, and that goal is aspirational.

Review worksheet

1. Goal of this part

What does this part try to show, or help the reader decide?

2. Key claims to test

#	Claim	Evidence given (citation / data)	Verifiable?
1

3. Adversarial review

Strongest counter-argument:
Unsupported, overstated, or outdated claims:
Source quality (primary vs. blog/forum/marketing):
Omissions / what a skeptic would ask:
Internal consistency with other segments:

4. Evaluation

Does the segment achieve its goal? (Yes / Partly / No)
Confidence: (High / Medium / Low)
Required fixes: