← CatZep/Engineering Guides/Reference

Engineering Craft & Process

Code smells, design patterns, core algorithms, and process notes.

Choose a concept, then work through an example

4 guides in this section. Each article states its audience and assumptions, explains specialized terms, and gives a worked example or practical exercise.

Technical topics distinguish toy models from product behavior. Leadership topics distinguish context-dependent frameworks from evidence and personal claims.

01·Code Smells & RefactoringsUse maintainability symptoms to identify a behavior-preserving refactoring, not to add patterns automatically. 02·ScrumUnderstand Scrum's commitments and feedback loop while separating optional estimation practices from framework requirements. 03·Design PatternsUnderstand what coupling each design pattern addresses and when simpler composition is sufficient. 04·Basic Algorithms & PatternsChoose an algorithm from input constraints, then check its boundary cases and cost.

Find a guide

4 guides

Basic Algorithms & Patterns

Choose an algorithm from input constraints, then check its boundary cases and cost.

Preconditions and postconditions · Loop invariants · Variants and well-founded orders · Complexity and workload assumptions · Recursion and induction

Code Smells — A Practical Refactoring Guide

Use maintainability symptoms to identify a behavior-preserving refactoring, not to add patterns automatically.

Refactoring and code smells · Liskov substitution and interfaces · Preconditions and postconditions · Aliasing and frame conditions · Strategy, Adapter, and Observer

Design Patterns — A Practical Reference

Understand what coupling each design pattern addresses and when simpler composition is sufficient.

Strategy, Adapter, and Observer · Liskov substitution and interfaces · Refactoring and code smells · Aliasing and frame conditions · Preconditions and postconditions

Scrum — A Practical Guide

Understand Scrum's commitments and feedback loop while separating optional estimation practices from framework requirements.

Scrum empiricism and commitments · Definition of Done versus acceptance criteria · Outputs, outcomes, and measurement · Ownership, accountability, and decision rights · Stakeholders and alignment