A 16-week project-based introduction to programming.

PROGRAMMING
IS A SPORT.

COACH

DR. MICHAEL LITMAN, Ph.D.

Master Computer Scientist

You don't get good at basketball by reading about basketball. The same is true of code. This is a 16-week training program: C++ to Java, fourteen projects, every one of them themed around a real question a thoughtful Christian student today might actually face.

START WEEK 1 SEE THE SYLLABUS COMPANION CODE ↗
16
Chapters
14
Projects
2
Languages
0
Prior coding required

The Thesis

Three moves. Every program ever written.

Pillar 1

Memory

We remember names, scores, verses, manuscripts. Computers do too — using variables.

Pillar 2

Asking Questions

"Is this true?" — and react. Programs do this with conditionals.

Pillar 3

Repetition

Do the same thing many times. Loops and functions. The same shape as practice.

The Syllabus

16 chapters · 14 projects

Phase 1 covers procedural C++ — the stick shift. Phase 2 covers object-oriented C++ and Java — the automatic. The midterm sits at the halfway mark; the final caps the back half.

Phase 1 · Procedural C++

Weeks 1–8.

Week 1
Ch 1 — The Sport of Programming
Output, input, your first variable
P1 Apologist's Card
Week 2
Ch 2 — Memory: Variables and Types
Five primitive types, the integer-division trap
P2 Fine-Tuning Stats
Week 3
Ch 3 — Asking Questions: Conditionals
if/else, boolean operators, switch
P3 The Coffee Shop Conversation
Week 4
Ch 4 — Repetition I: Loops
while, for, sentinels, nested loops
P4 Daily Practice Tracker
Week 5
Ch 5 — Repetition II: Functions
Definition, parameters, composition, references
P5 Reasoning Toolkit
Week 6
Ch 6 — Collections: Arrays and Strings
Fixed-size arrays, strings, search, sort
P6 Manuscript Database
Week 7
Ch 7 — Grouping Memory: Structs
Struct definition, struct arrays, passing structs
P7 Evidence Inventory
Week 8
Ch 8 — Midterm Review
Phase 1 cumulative — 60-min live exam
P8 Mission Trip Sim (MIDTERM)
Week 9
Ch 9 — From Struct to Class
Class basics, public/private, methods
P9 Stewardship Account
Week 10
Ch 10 — Constructors & Encapsulation
Constructors, destructors, composition
P10 Apologetics Library
Week 11
Ch 11 — Pointers and Dynamic Memory
Pointers, this, new/delete, linked lists
P11 Chain of Witnesses
Week 12
Ch 12 — Inheritance in C++
Base/derived, virtual, override, polymorphism
P12 Argument Case File

Phase 2 · Object-Oriented (C++ → Java)

Weeks 9–16.

Week 13 · Java
Ch 13 — Shifting Gears: Hello, Java
Java syntax, references, garbage collection
P13 Java Migration
Week 14 · Java
Ch 14 — Polymorphism in Java
@Override, instanceof, static, enhanced-for
Week 15 · Java
Ch 15 — Abstract Classes & Interfaces
Abstract methods, interfaces, multiple-interface implement
Week 16 · Java
Ch 16 — Final Review
Phase 2 cumulative — 60-min live exam
P14 Pilgrim's Journey Engine (FINAL)

16 of 16 chapters available so far. The rest are coming.

Projects

Every project earns its keep.

This course is taught at a confessional Lutheran university. The technical content is the same as any rigorous secular intro course — but the projects are pointed at questions Christians your age actually get asked.

P1
Apologist's Card
"Who am I and what question am I wrestling with?"
P2
Fine-Tuning Stats
"Is the universe designed?"
P3
The Coffee Shop Conversation
"Why does God allow suffering?"
P4
Daily Practice Tracker
"Is faith just intellectual?"
P5
Reasoning Toolkit
"Can faith be reasoned about?"
P6
Manuscript Database
"Is the Bible reliable?"
P7
Evidence Inventory
"Did the Resurrection happen?"
P8
Mission Trip Sim (MIDTERM)
"What does lived faith look like?"
P9
Stewardship Account
"What does Christianity say about money?"
P10
Apologetics Library
"The Christian intellectual tradition"
P11
Chain of Witnesses
"Has the faith been continuously believed?"
P12
Argument Case File
"What kinds of arguments for God are there?"
P13
Java Migration
"The skill is language-independent"
P14
Pilgrim's Journey Engine (FINAL)
"The shape of the Christian journey"

SEE THE FULL PROJECT ARC →

House Rules

AI is a sparring partner. Not a replacement.

Every concept and project gets attempted yourself, from scratch, with the AI off — first. Then optionally use it to review your work, explain an error, or expand your thinking. The midterm and final are closed-book, closed-AI. Show up honest.