Glenn Lum Software Engineering

Tier 3

Tier 3: Cross-Cutting Disciplines

These practices don’t belong to any single stage of the lifecycle; they apply across all of them, all the time. They are the difference between a system that works and a system that is reliable, secure, and sustainable.


Observability and Monitoring

L1

CONCEPT 3.1 Observability and Monitoring

L2

DEPTH 3.1.1 Monitoring vs Observability: Known Unknowns vs Unknown Unknowns

DEPTH 3.1.2 The Three Pillars: Metrics, Logs, and Traces

DEPTH 3.1.3 Metrics: Counters, Gauges, Histograms, and What Gets Lost in Aggregation

DEPTH 3.1.4 Distributed Tracing: How Requests Travel Across Service Boundaries

DEPTH 3.1.5 The SLI/SLO/SLA Framework: Defining Reliability from the User’s Perspective

DEPTH 3.1.6 Alerting Philosophy: Symptoms Over Causes, and the Cost of Alert Fatigue


Security (DevSecOps)

L1

CONCEPT 3.2 Security (DevSecOps)

L2

DEPTH 3.2.1 Shifting Security Left: From Audit to Embedded Practice

DEPTH 3.2.2 Threat Modeling: Thinking About What Can Go Wrong Before You Build

DEPTH 3.2.3 The OWASP Top 10: The Recurring Vulnerability Classes

DEPTH 3.2.4 Static and Dynamic Analysis: SAST and DAST

DEPTH 3.2.5 The Principle of Least Privilege: Why Permissions Should Be Minimal by Default

DEPTH 3.2.6 Secrets and Credential Management: Injection, Rotation, and Audit

DEPTH 3.2.7 Supply Chain Security: SBOMs, Signing, and Dependency Provenance


Reliability Engineering

L1

CONCEPT 3.3 Reliability Engineering

L2

DEPTH 3.3.1 SLIs, SLOs, and Error Budgets: The Language of Reliability

DEPTH 3.3.2 Failure Modes in Distributed Systems: Partial Failure and Cascading Failure

DEPTH 3.3.3 Circuit Breakers, Retries, and Timeouts: The Resilience Primitives

DEPTH 3.3.4 Chaos Engineering: Deliberately Breaking Things

DEPTH 3.3.5 Toil: The Invisible Reliability Tax

DEPTH 3.3.6 Runbooks and Incident Response: Operationalizing the Failure Model


Cost Awareness (FinOps Thinking)

L1

CONCEPT 3.4 Cost Awareness (FinOps Thinking)

L2

DEPTH 3.4.1 The Cloud Billing Model: On-Demand, Reserved, and Spot

DEPTH 3.4.2 Resource Right-Sizing: Utilization vs Allocation

DEPTH 3.4.3 Cost Attribution: Tagging, Showback, and Chargeback

DEPTH 3.4.4 The Cost of Data Transfer: Architecture Decisions and Network Egress

DEPTH 3.4.5 Reserved Instances and Savings Plans: Commitment as a Financial Tool

DEPTH 3.4.6 Waste Identification: Idle Resources, Orphaned Assets, and Oversized Instances


Emerging Technology

L1

CONCEPT 3.5 Emerging Technology

L2

DEPTH 3.5.1 The Tradeoff Map: What Every New Technology Is Actually Buying and Paying

DEPTH 3.5.2 Stack Layer Diagnosis: Locating a New Technology in the Known Problem Space

DEPTH 3.5.3 The Maturity Gradient: Understanding Where a Technology Sits in Its Lifecycle

DEPTH 3.5.4 Separating Signal from Momentum: Identifying Genuine Architectural Shifts

DEPTH 3.5.5 Transfer Learning: How Foundational Knowledge Extends to New Contexts

DEPTH 3.5.6 The Adoption Decision: A Framework for Engaging With Emerging Technology in Production


← Back to Home