Developer Tools: Infrastructure & Developer Experience

01

Design process (from Christopher Alexander's 'Notes on the Synthesis of Form'): 1) lay out constraints, 2) generate solutions satisfying them, 3) revisit constraints if feedback reveals gaps—loop back to step 1 rather than patching solutions directly.

02

The common failure mode is 'design wackamole': skipping constraint re-evaluation and spot-fixing symptoms (e.g. 'make X more prominent') when user feedback arrives, which creates a disjointed patchwork prioritizing some interactions arbitrarily over others.

03

AI agents exacerbate wackamole design by readily executing narrow prompts like 'add an affordance for Y' without questioning whether the underlying constraint set needs revision—mirroring how agents add unnecessary try-catch/utility duplication in code.

04

Workflow: maintain a running document of minor UI 'papercuts' instead of reactively fixing each one; ship obvious fixes immediately but batch small annoyances for a cohesive redesign later, avoiding accumulated patchwork mess.

05

AI design agents systematically over-add (extra copy, lines, icons, belt-and-suspenders elements), producing UI that looks polished but is functionally worse—counteract by auditing every element and asking 'do I actually need that?'

06

'Prototype gravity' risk: building the first design version directly in the production codebase creates inertia to just refine that version rather than exploring alternatives, and forces the agent to graft onto existing real-app constraints prematurely—iterate in a dedicated design tool (Figma, Cursor Design Mode, Claude Design, HTML prototypes) generating 3-4 variants first.

07

At Ref, a /showcase page is used for agents to build and iterate on UI components in isolation before wiring them into the main app, enforcing separation of views/logic and reusable component libraries for visual cohesion.

08

For features spanning frontend and backend, Ref splits PRs by layer: backend changes get unit/integration test verification, frontend changes require human review via preview deploys with real backend data—since even agent-built designs matching spec often still need adjustment once seen with real data.