Glenn Lum Software Engineering

Tier 2

Tier 2: Core Lifecycle Stages

This is the assembly line. Code enters on one end as text in a developer’s editor and exits on the other end as a running, validated, observable process in a production environment. Every station in this assembly line is a potential bottleneck, quality gate, or failure point.


Source Control and Collaboration

L1

CONCEPT 2.1 Source Control and Collaboration

L2

DEPTH 2.1.1 The Git Object Model: Commits, Trees, and Refs

DEPTH 2.1.2 Branching Strategies: Trunk-Based Development vs GitFlow

DEPTH 2.1.3 Merge Strategies: Merge Commits, Rebase, and Squash

DEPTH 2.1.4 The Pull Request as a Quality Gate

DEPTH 2.1.5 Conflict Resolution: Textual vs Semantic Conflicts

DEPTH 2.1.6 Monorepo vs Polyrepo: Repository Structure as an Architectural Decision


Testing Strategy

L1

CONCEPT 2.2 Testing Strategy

L2

DEPTH 2.2.1 The Testing Pyramid: Cost, Speed, and Coverage as a Design Constraint

DEPTH 2.2.2 Test Doubles: Mocks, Stubs, Fakes, and Spies

DEPTH 2.2.3 What Test Coverage Measures and What It Misses

DEPTH 2.2.4 Contract Testing: How Services Agree on Interfaces

DEPTH 2.2.5 Testing in Production: Feature Flags, Canary Analysis, and Observability as Tests

DEPTH 2.2.6 The Cost of Flaky Tests


Continuous Integration (CI)

L1

CONCEPT 2.3 Continuous Integration (CI)

L2

DEPTH 2.3.1 What CI Actually Means: The Discipline vs the Tool

DEPTH 2.3.2 The Anatomy of a CI Pipeline: Triggers, Stages, and Feedback Loops

DEPTH 2.3.3 Build Reproducibility: Why the Same Source Should Always Produce the Same Artifact

DEPTH 2.3.4 Fast Feedback as a Design Constraint

DEPTH 2.3.5 The CI/CD Boundary: What CI Produces and Where It Goes


Artifact and Dependency Management

L1

CONCEPT 2.4 Artifact and Dependency Management

L2

DEPTH 2.4.1 What an Artifact Is: The Unit of Deployment

DEPTH 2.4.2 Semantic Versioning: What a Version Number Communicates

DEPTH 2.4.3 Dependency Graphs and Transitive Dependencies

DEPTH 2.4.4 Artifact Registries: Storage, Distribution, and Promotion

DEPTH 2.4.5 Dependency Pinning vs Version Ranges: The Reproducibility Tradeoff

DEPTH 2.4.6 Supply Chain Security: Why Your Dependencies Are Your Attack Surface


Continuous Delivery and Deployment (CD)

L1

CONCEPT 2.5 Continuous Delivery and Deployment (CD)

L2

DEPTH 2.5.1 Delivery vs Deployment: The Most Important Distinction in CD

DEPTH 2.5.2 Deployment Strategies: Blue/Green, Canary, Rolling, and Recreate

DEPTH 2.5.3 The Environment Pipeline: Promoting an Artifact Through Stages

DEPTH 2.5.4 Rollback vs Roll Forward: Two Philosophies for Handling Bad Releases

DEPTH 2.5.5 The Release as a Decoupled Event: Feature Flags and Dark Launches


Configuration and Feature Management

L1

CONCEPT 2.6 Configuration and Feature Management

L2

DEPTH 2.6.1 The Twelve-Factor Config Principle: Why Configuration Is Not Code

DEPTH 2.6.2 Configuration Hierarchy and Override Models

DEPTH 2.6.3 Secrets Management: Why Secrets Are Different from Configuration

DEPTH 2.6.4 Feature Flags: The Full Operational Model

DEPTH 2.6.5 Configuration Drift: How Reality Diverges from Declared State


Infrastructure as Code (IaC)

L1

CONCEPT 2.7 Infrastructure as Code (IaC)

L2

DEPTH 2.7.1 Declarative vs Imperative Infrastructure: The Model That Changes Everything

DEPTH 2.7.2 State: The Source of Truth and Source of Risk

DEPTH 2.7.3 Idempotency: Why Applying Twice Must Be Safe

DEPTH 2.7.4 The Plan/Apply Cycle: Preview as a Safety Mechanism

DEPTH 2.7.5 Modules and Code Reuse in Infrastructure

DEPTH 2.7.6 Drift Detection: When Reality Diverges from Code


← Back to Home