Living Notes
These are working notes that evolve as projects surface new constraints and better approaches.
Want to suggest a book for the workshop shelf? Send a note through the Contact page.
Books and Notes
These notes reflect the Pixel Forgeworks operating philosophy: practical troubleshooting, clear ownership, adaptable design, workflow clarity, and continuous improvement through real project feedback.
The Friction Project
Notes: Reducing drag requires seeing the full operating system around the work, not just the immediate task.
Takeaways: Listen to the five voices: customer, employee, owner, community, and process. Better systems come from balancing all five in decisions.
How it shows up in projects: Incident and workflow reviews include user impact, operator burden, business tradeoffs, ecosystem effects, and process clarity before changes are finalized.
The Pragmatic Programmer
Notes: The strongest theme is decoupling and building systems that are easier to change over time.
Takeaways: Prefer adaptable structures, loose coupling, and incremental improvement in software, workflows, and documentation rather than brittle one-off solutions.
How it shows up in projects: Validation workflows, runbooks, and tooling are written so teams can evolve them safely as environments change.
The Phoenix Project
Notes: Flow, constraints, unplanned work, and reliability tradeoffs are central to operational health.
Takeaways: Protect bottlenecks, reduce avoidable WIP, and make operational work visible so recovery and planning improve over time.
How it shows up in projects: Runbooks and checklists are structured to reduce cognitive load during incidents and keep handoffs aligned across teams.