← Templates

Build Software That Lasts

55 tasks

The 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.)

Start this plan

Sign in to review and change this plan before creating a private project.

Derived from guideBuild Software That Lasts
Source details

Derivation tier: T1

software-engineering · 95d8e72598b132ba77c4244edc536a88ee44c78970c18390fea4c6019d5d0e6f

Authorship and review status are not recorded here.

Template tasks (55)

Review tasks and choose or change owners before creating your project. Assigning an agent does not start it.

Tasks begin as To Do in your project.

  • #1Developer Learning, Competence & ProficiencyHigh

    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.

    Completion check

    The developer learning, competence & proficiency work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 0 days after project start · Planned duration: 14 days

  • #2Hands-On Deliberate PracticeMedium

    Makes the case for active building over passive consumption, and shows how deliberate practice converts information into retained, usable skill and confidence.

    Completion check

    The hands-on deliberate practice work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 14 days after project start · Planned duration: 7 days

  • #3Coding Self-Efficacy & ConfidenceMedium

    The belief system that keeps a developer trying when code breaks, and why that confidence is earned rather than pep-talked into existence.

    Completion check

    The coding self-efficacy & confidence work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 21 days after project start · Planned duration: 7 days

  • #4Pedagogical / Instructional DesignMedium

    The instructional choices — sequencing, worked examples, constrained scope — that determine whether learning material actually produces competence.

    Completion check

    The pedagogical / instructional design work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 28 days after project start · Planned duration: 7 days

  • #5Debugging & Problem Decomposition SkillMedium

    Treats debugging and decomposition as a trainable, systematic discipline — the skill that turns opaque failures into understood, fixable problems.

    Completion check

    The debugging & problem decomposition skill work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 35 days after project start · Planned duration: 7 days

  • #6Framework, Library & Platform LeverageMedium

    When leaning on existing frameworks, libraries, and platforms accelerates delivery — and when the leverage quietly becomes a liability.

    Completion check

    The framework, library & platform leverage work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 42 days after project start · Planned duration: 7 days

  • #7Task Automation & Workflow EfficiencyMedium

    Shows how automating repetitive workflows compounds engineer productivity and reduces the human error that undermines reliability.

    Completion check

    The task automation & workflow efficiency work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 49 days after project start · Planned duration: 7 days

  • #8Algorithms & CS FundamentalsLow

    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.

    Completion check

    The algorithms & cs fundamentals work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 56 days after project start · Planned duration: 3 days

  • #9Managing Complexity / Cognitive LoadHigh

    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.

    Completion check

    The managing complexity / cognitive load work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 59 days after project start · Planned duration: 14 days

  • #10Modularity, Information Hiding & Deep ModulesHigh

    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.

    Completion check

    The modularity, information hiding & deep modules work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 73 days after project start · Planned duration: 14 days

  • #11Coupling / DecouplingHigh

    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.

    Completion check

    The coupling / decoupling work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 87 days after project start · Planned duration: 14 days

  • #12Code Readability, Naming & DocumentationHigh

    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.

    Completion check

    The code readability, naming & documentation work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 101 days after project start · Planned duration: 14 days

  • #13Testing & TestabilityHigh

    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.

    Completion check

    The testing & testability work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 115 days after project start · Planned duration: 14 days

  • #14Security Posture & ControlsHigh

    The controls that resist threats — authentication, authorization, secure coding, and data protection — and the practice of moving security earlier into development.

    Completion check

    The security posture & controls work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 129 days after project start · Planned duration: 14 days

  • #15API & Interface Design QualityHigh

    Design interface contracts that consumers can integrate against once and rely on for years, even as your implementation changes underneath them.

    Completion check

    The api & interface design quality work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 143 days after project start · Planned duration: 14 days

  • #16Quality Assurance & Defect RemovalHigh

    The systematic inspection, review, and testing rigor that catches defects before users do — and where in the lifecycle each technique pays off.

    Completion check

    The quality assurance & defect removal work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 157 days after project start · Planned duration: 14 days

  • #17Idiomatic / Pythonic Style & ConventionsMedium

    Write code that reads like the language was designed to solve your problem — and why that legibility outlives you.

    Completion check

    The idiomatic / pythonic style & conventions work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 171 days after project start · Planned duration: 7 days

  • #18Strategic Design Investment / RefactoringHigh

    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.

    Completion check

    The strategic design investment / refactoring work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 178 days after project start · Planned duration: 14 days

  • #19Domain Modeling & Ubiquitous LanguageMedium

    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.

    Completion check

    The domain modeling & ubiquitous language work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 192 days after project start · Planned duration: 7 days

  • #20Deployment Pipeline & CI/CD AutomationHigh

    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.

    Completion check

    The deployment pipeline & ci/cd automation work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 199 days after project start · Planned duration: 14 days

  • #21Containerization, Orchestration & Infrastructure-as-CodeMedium

    Packaging services as immutable containers, orchestrating them, and defining infrastructure as versioned declarative code — the substrate that makes environments reproducible and scaling automatic.

    Completion check

    The containerization, orchestration & infrastructure-as-code work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 213 days after project start · Planned duration: 7 days

  • #22Observability, Monitoring & TelemetryHigh

    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.

    Completion check

    The observability, monitoring & telemetry work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 220 days after project start · Planned duration: 14 days

  • #23Resilience & Fault Tolerance PatternsHigh

    Use the concrete failure-isolation patterns and how to choose among them so one dependency's outage doesn't take your whole system down.

    Completion check

    The resilience & fault tolerance patterns work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 234 days after project start · Planned duration: 14 days

  • #24Data Modeling, Storage & Distributed Data ManagementHigh

    How data modeling, storage-engine choice, replication, and ownership boundaries determine whether your system survives faults and scales without corruption.

    Completion check

    The data modeling, storage & distributed data management work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 248 days after project start · Planned duration: 14 days

  • #25Maintainability & EvolvabilityHigh

    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.

    Completion check

    The maintainability & evolvability work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 262 days after project start · Planned duration: 14 days

  • #26Delivery Velocity & Deployment FrequencyHigh

    Define velocity as the safe, repeatable flow of change from commit to production—and shows what actually moves it.

    Completion check

    The delivery velocity & deployment frequency work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 276 days after project start · Planned duration: 14 days

  • #27Scalability & ElasticityHigh

    Design systems that absorb load growth by adding resources rather than rewriting, and how to scale each component on its own schedule.

    Completion check

    The scalability & elasticity work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 290 days after project start · Planned duration: 14 days

  • #28Performance & EfficiencyHigh

    Making the system fast and cheap under its real workload — latency, throughput, and the cost of the resources consumed to achieve them.

    Completion check

    The performance & efficiency work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 304 days after project start · Planned duration: 14 days

  • #29Team Collaboration, Autonomy & OwnershipHigh

    Structuring teams for autonomy and shared ownership so they can ship independently, and aligning that structure with your architecture per Conway's Law.

    Completion check

    The team collaboration, autonomy & ownership work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 318 days after project start · Planned duration: 14 days

  • #30Flow, WIP Control & Constraint ManagementHigh

    Shows how limiting work-in-process, shrinking batch size, and managing constraints produce smoother, more predictable delivery.

    Completion check

    The flow, wip control & constraint management work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 332 days after project start · Planned duration: 14 days

  • #31Technical Debt & Structural DecayHigh

    Technical debt as a measurable drag on delivery and gives you a way to decide which debt to pay down and when.

    Completion check

    The technical debt & structural decay work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 346 days after project start · Planned duration: 14 days

  • #32Incident Response & Recovery (MTTR)High

    Focus on about the full incident loop — detect, restore service, then learn hard enough that the same class of failure doesn't recur.

    Completion check

    The incident response & recovery (mttr) work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 360 days after project start · Planned duration: 14 days

  • #33Fast Feedback Loops & Iterative/Empirical PracticeHigh

    Short iterative cycles and empirical practice — how fast feedback converts uncertainty into confident, maintainable decisions.

    Completion check

    The fast feedback loops & iterative/empirical practice work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 374 days after project start · Planned duration: 14 days

  • #34Deployment / Change ConfidenceMedium

    The low-fear, high-confidence state that lets teams ship without dread. You get the tests, automation, and decoupling that manufacture it.

    Completion check

    The deployment / change confidence work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 388 days after project start · Planned duration: 7 days

  • #35UI/UX & Visual Design QualityHigh

    The interface qualities — visual hierarchy, consistency, accessibility, and usability — that determine whether users can scan, understand, and complete their tasks.

    Completion check

    The ui/ux & visual design quality work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 395 days after project start · Planned duration: 14 days

  • #36Realistic Estimation & Scheduling DisciplineLow

    Apply a way to produce estimates that inform decisions instead of manufacturing false confidence, and to schedule around uncertainty rather than deny it.

    Completion check

    The realistic estimation & scheduling discipline work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 409 days after project start · Planned duration: 3 days

  • #37Incremental Migration & Legacy EvolutionLow

    Evolve a legacy system through small reversible steps rather than a big-bang rewrite, and how that discipline unlocks independent deployability.

    Completion check

    The incremental migration & legacy evolution work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 412 days after project start · Planned duration: 3 days

  • #38LLM/AI Response Quality & GroundingMedium

    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.

    Completion check

    The llm/ai response quality & grounding work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 415 days after project start · Planned duration: 7 days

  • #39Architecture Style & Trade-off FitHigh

    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.

    Completion check

    The architecture style & trade-off fit work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 422 days after project start · Planned duration: 14 days

  • #40Service Decomposition & GranularityHigh

    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.

    Completion check

    The service decomposition & granularity work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 436 days after project start · Planned duration: 14 days

  • #41Independent DeployabilityMedium

    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.

    Completion check

    The independent deployability work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 450 days after project start · Planned duration: 7 days

  • #42System Reliability & AvailabilityHigh

    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.

    Completion check

    The system reliability & availability work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 457 days after project start · Planned duration: 14 days

  • #43Generative Culture & Psychological SafetyHigh

    Build the trust, information flow, and blameless learning that let engineers take interpersonal risks — surfacing bad news, admitting error, and challenging decisions.

    Completion check

    The generative culture & psychological safety work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 471 days after project start · Planned duration: 14 days

  • #44Conceptual Integrity & Architectural LeadershipMedium

    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.

    Completion check

    The conceptual integrity & architectural leadership work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 485 days after project start · Planned duration: 7 days

  • #45Communication & Coordination OverheadHigh

    Quantifies why coordination cost grows nonlinearly with team size and what that means for how you structure and staff projects.

    Completion check

    The communication & coordination overhead work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 492 days after project start · Planned duration: 14 days

  • #46SLO / Error Budget & Toil ReductionHigh

    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.

    Completion check

    The slo / error budget & toil reduction work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 506 days after project start · Planned duration: 14 days

  • #47Platform Engineering & Developer ExperienceHigh

    Build internal platforms as products — paved paths and self-service that hide infrastructure complexity and let product teams move without reinventing plumbing.

    Completion check

    The platform engineering & developer experience work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 520 days after project start · Planned duration: 14 days

  • #48Software Quality (Product)High

    Focus on about the composite outcome — correctness, reliability, robustness, and usability of what you actually shipped — and the practices that produce it.

    Completion check

    The software quality (product) work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 534 days after project start · Planned duration: 14 days

  • #49User Satisfaction & Business ValueHigh

    Connect your engineering outcomes to the thing that justifies them: users who succeed and adopt, and business value the software actually unlocks.

    Completion check

    The user satisfaction & business value work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 548 days after project start · Planned duration: 14 days

  • #50Engineer Well-being & SustainabilityMedium

    How engineer well-being is manufactured — or destroyed — by upstream decisions about culture, schedule, and on-call design, not by perks bolted on afterward.

    Completion check

    The engineer well-being & sustainability work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 562 days after project start · Planned duration: 7 days

  • #51Career Impact, Reputation & AdvancementHigh

    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.

    Completion check

    The career impact, reputation & advancement work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 569 days after project start · Planned duration: 14 days

  • #52Contextual Conditions (Domain Complexity, Team, Workload, Volatility)Medium

    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.

    Completion check

    The contextual conditions (domain complexity, team, workload, volatility) work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 583 days after project start · Planned duration: 7 days

  • #53Language/Product Design & LongevityLow

    Examine what makes a language or product durable over decades — minimalism, backward compatibility, and articulated principles — versus what makes it a churning liability.

    Completion check

    The language/product design & longevity work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 590 days after project start · Planned duration: 3 days

  • #54Chaos Engineering & Proactive Resilience TestingLow

    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.

    Completion check

    The chaos engineering & proactive resilience testing work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 593 days after project start · Planned duration: 3 days

  • #55Decentralized Consensus & Cryptographic TrustLow

    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.

    Completion check

    The decentralized consensus & cryptographic trust work is complete: key decisions are recorded and outputs are ready for the next phase.

    Choose or change the owner during setup.

    Starts 596 days after project start · Planned duration: 3 days

Start this plan

Sign in to review and change this plan before creating a private project.

Template usage
  • Recorded uses: 0
  • Projects marked complete: 0 (self-declared)
  • Independent completion results are not available.