Build Software That Lasts
Start this planThe rate and safety with which valuable changes flow from commit to production (deployment frequency, lead time, cycle time). (Setting direction and reconciling trade-offs at scale.)
started 0 · finished 0 (claimed) · not yet measured (verified) · no data (n<5)
Ordered tasks (55) — this is what a project auto-creates
- #1Developer Learning, Competence & ProficiencyHighTo Do
How durable engineering skill is actually built — through structured mental models and demonstrated proficiency — and why it is the hinge on which product quality turns.
Assignee: Unassigned · due 0 days after project start · takes 14 days
- #2Hands-On Deliberate PracticeMediumTo Do
Makes the case for active building over passive consumption, and shows how deliberate practice converts information into retained, usable skill and confidence.
Assignee: Unassigned · due 14 days after project start · takes 7 days
- #3Coding Self-Efficacy & ConfidenceMediumTo Do
The belief system that keeps a developer trying when code breaks, and why that confidence is earned rather than pep-talked into existence.
Assignee: Unassigned · due 21 days after project start · takes 7 days
- #4Pedagogical / Instructional DesignMediumTo Do
The instructional choices — sequencing, worked examples, constrained scope — that determine whether learning material actually produces competence.
Assignee: Unassigned · due 28 days after project start · takes 7 days
- #5Debugging & Problem Decomposition SkillMediumTo Do
Treats debugging and decomposition as a trainable, systematic discipline — the skill that turns opaque failures into understood, fixable problems.
Assignee: Unassigned · due 35 days after project start · takes 7 days
- #6Framework, Library & Platform LeverageMediumTo Do
When leaning on existing frameworks, libraries, and platforms accelerates delivery — and when the leverage quietly becomes a liability.
Assignee: Unassigned · due 42 days after project start · takes 7 days
- #7Task Automation & Workflow EfficiencyMediumTo Do
Shows how automating repetitive workflows compounds engineer productivity and reduces the human error that undermines reliability.
Assignee: Unassigned · due 49 days after project start · takes 7 days
- #8Algorithms & CS FundamentalsLowTo Do
Shows how algorithmic and data-structure literacy determines whether your software degrades gracefully or collapses as data and load grow. You get the reasoning that separates code that works in the demo from code that survives production scale.
Assignee: Unassigned · due 56 days after project start · takes 3 days
- #9Managing Complexity / Cognitive LoadHighTo Do
Apply a working definition of the complexity that actually kills software — the accidental kind, invented by your own structure — and how to keep it below the threshold where a change becomes an act of archaeology.
Assignee: Unassigned · due 59 days after project start · takes 14 days
- #10Modularity, Information Hiding & Deep ModulesHighTo Do
Why the ratio of interface cost to hidden functionality — module depth — matters more than module count. You learn to judge a module by how much it lets callers ignore.
Assignee: Unassigned · due 73 days after project start · takes 14 days
- #11Coupling / DecouplingHighTo Do
Separates the several distinct forms of coupling — static, dynamic, temporal, implementation, deployment — so you can decouple the dimension that's actually blocking independent change instead of chasing decoupling as a blanket virtue.
Assignee: Unassigned · due 87 days after project start · takes 14 days
- #12Code Readability, Naming & DocumentationHighTo Do
Focus on about making intent legible to the next human — through names that encode meaning, comments that capture what code cannot, and formatting that reveals structure — so that reading the code is faster than re-deriving it.
Assignee: Unassigned · due 101 days after project start · takes 14 days
- #13Testing & TestabilityHighTo Do
Both halves of testing — the suite you write and the design properties that make writing it possible — because most testing pain is actually a design problem wearing a testing costume.
Assignee: Unassigned · due 115 days after project start · takes 14 days
- #14Security Posture & ControlsHighTo Do
The controls that resist threats — authentication, authorization, secure coding, and data protection — and the practice of moving security earlier into development.
Assignee: Unassigned · due 129 days after project start · takes 14 days
- #15API & Interface Design QualityHighTo Do
Design interface contracts that consumers can integrate against once and rely on for years, even as your implementation changes underneath them.
Assignee: Unassigned · due 143 days after project start · takes 14 days
- #16Quality Assurance & Defect RemovalHighTo Do
The systematic inspection, review, and testing rigor that catches defects before users do — and where in the lifecycle each technique pays off.
Assignee: Unassigned · due 157 days after project start · takes 14 days
- #17Idiomatic / Pythonic Style & ConventionsMediumTo Do
Write code that reads like the language was designed to solve your problem — and why that legibility outlives you.
Assignee: Unassigned · due 171 days after project start · takes 7 days
- #18Strategic Design Investment / RefactoringHighTo Do
Design and refactoring as a continuous investment decision rather than a project phase — how to trade the certain cost of good structure now against the compounding interest of tactical shortcuts.
Assignee: Unassigned · due 178 days after project start · takes 14 days
- #19Domain Modeling & Ubiquitous LanguageMediumTo Do
Build a shared, expressive model of the business and encode it directly in your code and conversations. You'll learn to distill the core domain and speak one language across product and engineering.
Assignee: Unassigned · due 192 days after project start · takes 7 days
- #20Deployment Pipeline & CI/CD AutomationHighTo Do
The automated build-test-deploy pipeline as the machine that converts a commit into a low-risk production change, and why small batches beat big careful ones.
Assignee: Unassigned · due 199 days after project start · takes 14 days
- #21Containerization, Orchestration & Infrastructure-as-CodeMediumTo Do
Packaging services as immutable containers, orchestrating them, and defining infrastructure as versioned declarative code — the substrate that makes environments reproducible and scaling automatic.
Assignee: Unassigned · due 213 days after project start · takes 7 days
- #22Observability, Monitoring & TelemetryHighTo Do
The logs, metrics, and distributed traces that let you infer what a running system is doing — and why observability is a design property, not a dashboard you buy.
Assignee: Unassigned · due 220 days after project start · takes 14 days
- #23Resilience & Fault Tolerance PatternsHighTo Do
Use the concrete failure-isolation patterns and how to choose among them so one dependency's outage doesn't take your whole system down.
Assignee: Unassigned · due 234 days after project start · takes 14 days
- #24Data Modeling, Storage & Distributed Data ManagementHighTo Do
How data modeling, storage-engine choice, replication, and ownership boundaries determine whether your system survives faults and scales without corruption.
Assignee: Unassigned · due 248 days after project start · takes 14 days
- #25Maintainability & EvolvabilityHighTo Do
Focus on the terminal outcome most of the book serves: the ease with which a team can understand, operate, and change a system across its whole lifetime — and how low coupling, low cognitive load, testability, and domain modeling converge to produce it.
Assignee: Unassigned · due 262 days after project start · takes 14 days
- #26Delivery Velocity & Deployment FrequencyHighTo Do
Define velocity as the safe, repeatable flow of change from commit to production—and shows what actually moves it.
Assignee: Unassigned · due 276 days after project start · takes 14 days
- #27Scalability & ElasticityHighTo Do
Design systems that absorb load growth by adding resources rather than rewriting, and how to scale each component on its own schedule.
Assignee: Unassigned · due 290 days after project start · takes 14 days
- #28Performance & EfficiencyHighTo Do
Making the system fast and cheap under its real workload — latency, throughput, and the cost of the resources consumed to achieve them.
Assignee: Unassigned · due 304 days after project start · takes 14 days
- #29Team Collaboration, Autonomy & OwnershipHighTo Do
Structuring teams for autonomy and shared ownership so they can ship independently, and aligning that structure with your architecture per Conway's Law.
Assignee: Unassigned · due 318 days after project start · takes 14 days
- #30Flow, WIP Control & Constraint ManagementHighTo Do
Shows how limiting work-in-process, shrinking batch size, and managing constraints produce smoother, more predictable delivery.
Assignee: Unassigned · due 332 days after project start · takes 14 days
- #31Technical Debt & Structural DecayHighTo Do
Technical debt as a measurable drag on delivery and gives you a way to decide which debt to pay down and when.
Assignee: Unassigned · due 346 days after project start · takes 14 days
- #32Incident Response & Recovery (MTTR)HighTo Do
Focus on about the full incident loop — detect, restore service, then learn hard enough that the same class of failure doesn't recur.
Assignee: Unassigned · due 360 days after project start · takes 14 days
- #33Fast Feedback Loops & Iterative/Empirical PracticeHighTo Do
Short iterative cycles and empirical practice — how fast feedback converts uncertainty into confident, maintainable decisions.
Assignee: Unassigned · due 374 days after project start · takes 14 days
- #34Deployment / Change ConfidenceMediumTo Do
The low-fear, high-confidence state that lets teams ship without dread. You get the tests, automation, and decoupling that manufacture it.
Assignee: Unassigned · due 388 days after project start · takes 7 days
- #35UI/UX & Visual Design QualityHighTo Do
The interface qualities — visual hierarchy, consistency, accessibility, and usability — that determine whether users can scan, understand, and complete their tasks.
Assignee: Unassigned · due 395 days after project start · takes 14 days
- #36Realistic Estimation & Scheduling DisciplineLowTo Do
Apply a way to produce estimates that inform decisions instead of manufacturing false confidence, and to schedule around uncertainty rather than deny it.
Assignee: Unassigned · due 409 days after project start · takes 3 days
- #37Incremental Migration & Legacy EvolutionLowTo Do
Evolve a legacy system through small reversible steps rather than a big-bang rewrite, and how that discipline unlocks independent deployability.
Assignee: Unassigned · due 412 days after project start · takes 3 days
- #38LLM/AI Response Quality & GroundingMediumTo Do
Address how to make AI and LLM features reliable — grounding output in retrieved context and constraining hallucination — so they deliver real value rather than plausible nonsense.
Assignee: Unassigned · due 415 days after project start · takes 7 days
- #39Architecture Style & Trade-off FitHighTo Do
Focus on about choosing an architectural style as a trade-off analysis against your specific drivers — workload, team shape, domain complexity, volatility — rather than adopting whatever the industry is currently celebrating.
Assignee: Unassigned · due 422 days after project start · takes 14 days
- #40Service Decomposition & GranularityHighTo Do
Criteria for where to draw service boundaries — around business capabilities and subdomains — and how to size them. You learn why granularity is a spectrum to tune, not a target to hit.
Assignee: Unassigned · due 436 days after project start · takes 14 days
- #41Independent DeployabilityMediumTo Do
Define the concrete capability that makes distributed architecture worth its cost — shipping one component to production without dragging others along — and what has to be true for it to actually hold.
Assignee: Unassigned · due 450 days after project start · takes 7 days
- #42System Reliability & AvailabilityHighTo Do
Reliability and availability as measurable outcomes produced by architecture, resilience patterns, observability, and data design — not as an aspiration but as a target you set and defend.
Assignee: Unassigned · due 457 days after project start · takes 14 days
- #43Generative Culture & Psychological SafetyHighTo Do
Build the trust, information flow, and blameless learning that let engineers take interpersonal risks — surfacing bad news, admitting error, and challenging decisions.
Assignee: Unassigned · due 471 days after project start · takes 14 days
- #44Conceptual Integrity & Architectural LeadershipMediumTo Do
Why a system that reflects one coherent set of ideas is easier to learn and change, and how to preserve that coherence as teams multiply.
Assignee: Unassigned · due 485 days after project start · takes 7 days
- #45Communication & Coordination OverheadHighTo Do
Quantifies why coordination cost grows nonlinearly with team size and what that means for how you structure and staff projects.
Assignee: Unassigned · due 492 days after project start · takes 14 days
- #46SLO / Error Budget & Toil ReductionHighTo Do
Quantify reliability as targets and error budgets, and how to use them to arbitrate the velocity-versus-reliability fight — plus how to cap operational toil.
Assignee: Unassigned · due 506 days after project start · takes 14 days
- #47Platform Engineering & Developer ExperienceHighTo Do
Build internal platforms as products — paved paths and self-service that hide infrastructure complexity and let product teams move without reinventing plumbing.
Assignee: Unassigned · due 520 days after project start · takes 14 days
- #48Software Quality (Product)HighTo Do
Focus on about the composite outcome — correctness, reliability, robustness, and usability of what you actually shipped — and the practices that produce it.
Assignee: Unassigned · due 534 days after project start · takes 14 days
- #49User Satisfaction & Business ValueHighTo Do
Connect your engineering outcomes to the thing that justifies them: users who succeed and adopt, and business value the software actually unlocks.
Assignee: Unassigned · due 548 days after project start · takes 14 days
- #50Engineer Well-being & SustainabilityMediumTo Do
How engineer well-being is manufactured — or destroyed — by upstream decisions about culture, schedule, and on-call design, not by perks bolted on afterward.
Assignee: Unassigned · due 562 days after project start · takes 7 days
- #51Career Impact, Reputation & AdvancementHighTo Do
Unpacks how organizational impact and reputation actually accrue for engineers — through visible execution, influence, and business understanding — and how that advancement feeds back into their sustainability.
Assignee: Unassigned · due 569 days after project start · takes 14 days
- #52Contextual Conditions (Domain Complexity, Team, Workload, Volatility)MediumTo Do
Why the right architectural and organizational choice is context-dependent — shaped by domain complexity, team size, workload, and ecosystem volatility — and how to read your own context before deciding.
Assignee: Unassigned · due 583 days after project start · takes 7 days
- #53Language/Product Design & LongevityLowTo Do
Examine what makes a language or product durable over decades — minimalism, backward compatibility, and articulated principles — versus what makes it a churning liability.
Assignee: Unassigned · due 590 days after project start · takes 3 days
- #54Chaos Engineering & Proactive Resilience TestingLowTo Do
How deliberately injecting failure into running systems converts hopeful assumptions about resilience into measured facts. You get the discipline of designing safe experiments that expose weakness before customers do.
Assignee: Unassigned · due 593 days after project start · takes 3 days
- #55Decentralized Consensus & Cryptographic TrustLowTo Do
Clarifies when cryptographic consensus and immutability genuinely earn a place in durable software versus when they add irreversible complexity for no benefit. You get the criteria for deciding whether trustlessness is actually your problem.
Assignee: Unassigned · due 596 days after project start · takes 3 days