COMP 2102 · Ship It: The Engineering of Actually Finishing

Led by Carmackian Engineering Simulacrum

Why do most software projects fail to ship? The discipline of finishing, from id Software's release cadence to the good-enough decision.

1. Module 1

   The Shipping Cadence

   Led by Carmackian Engineering Simulacrum

   The question

   id Software: one major game per year for ten years. Duke Nukem Forever: fourteen years, one release. What cultural and process differences explain this — and why is shipping velocity a distinct skill?

   Outcome

   The student can describe id's shipping culture and contrast it with teams that don't ship.

   Sub-units

   1. ○ 1.1 The id Cadence Open this unit → ✓ ↻
   2. ○ 1.2 Duke Nukem Forever Open this unit → ✓ ↻
   Begin the course → Print certificate of completion
2. Module 2

   Scope Management

   Led by Carmackian Engineering Simulacrum

   The question

   A feature not on the list does not exist. Scope management means deciding what to cut before the deadline, not after. How do you build and maintain a locked feature list in the face of constant pressure to add "just one more thing"?

   Outcome

   The student can apply scope management discipline to a project under time pressure.

   Sub-units

   1. ○ 2.1 Feature Cut Exercise Open this unit → ✓ ↻
   Open this module → Print certificate of completion
3. Module 3

   The Good Enough Decision

   Led by Carmackian Engineering Simulacrum

   The question

   "Good enough" is not "barely functional" — it is "the user gets value and shipping now beats shipping later." Three weeks from release, running at 45fps against a 60fps target: ship or delay? Apply the good-enough test.

   Outcome

   The student can articulate and apply the good-enough standard.

   Sub-units

   1. ○ 3.1 The Feature Trade-off Open this unit → ✓ ↻
   Open this module → Print certificate of completion
4. Module 4

   Open Source and the Engine Lifecycle

   Led by Carmackian Engineering Simulacrum

   The question

   id released every engine as open source after its commercial life ended. Half-Life was built on Quake. Call of Duty on Quake III. Is this philanthropy, optimal knowledge use, or both?

   Outcome

   The student can evaluate the open-source release decision for a contemporary technology.

   Sub-units

   1. ○ 4.1 The Release Decision Open this unit → ✓ ↻
   Open this module → Print certificate of completion
5. Module 5

   Ship It: The Full Picture

   Led by Carmackian Engineering Simulacrum

   The question

   What does it mean for software to be done? The engineering answer, the product answer, and the business answer often diverge. Which should govern — and what does "shipping" require culturally, psychologically, and technically?

   Outcome

   The student can take a defended position on the definition of "done."

   Sub-units

   1. ○ 5.1 Final Essay: What Does "Done" Mean? Open this unit → ✓ ↻
   Open this module → Print certificate of completion