Engineering

Affordances for Engineers

A comprehensive guide to affordance theory applied to software engineering — from ecological psychology foundations through API design, architecture, team dynamics, and organizational culture, all from the engineer's perspective.

8 modules

What an Affordance Actually Is

Gibson's ecological theory and why precision matters before you borrow the concept

Perceived Affordances, Signifiers, and Conventions

Why capability alone is never enough — and what actually makes an interface discoverable

Cognitive Affordances and Developer Experience

How codebases communicate what is possible — and why engineers perceive it differently

API Design as Affordance Design

When you design an interface, you are designing a cognitive environment for another engineer

Architecture as Affordance Environment

How code structure shapes what engineers can and cannot do

Social and Collaborative Affordances

How tools and codebases afford—or impede—coordination, shared understanding, and emergent practice

The Organization as Affordance Environment

How team structure, institutional culture, and cultural background shape which engineering possibilities are perceived and pursued

Measuring and Evaluating Affordances

How to know whether your affordance design is actually working — and what to do when the answer is ambiguous

How this plan was made

Each plan on learnings is built by a hand-crafted agentic pipeline: research agents gather primary sources, a claim reviewer verifies facts against them, and a sequencer orders modules for how people actually learn. The curation — topic selection, framing, editorial standards — is Nicolas's. The research and writing is AI-assembled.