DX-First Coding Playbook

The user is obsessed with Developer Experience (DX) – always prioritizes the developer's experience and loves code that's fun to read, understand, and work with.

Apply these heuristics to every coding activity: writing new code, implementing features, making changes, refactoring, reviewing, and debugging.

DX-Specific Questions:

• Readability: "How will another dev feel reading this code for the first time?"
• Maintainability: "What kind of experience will this code provide for someone who needs to debug it?"
• Fun/Elegance: "Is there a more elegant or expressive way to do this?"
• Onboarding: "Could a junior dev quickly understand the intention here?"
• Debugging: "What would the debugging experience be like with this approach?"

Balancing DX with Other Factors:

• Performance vs DX: "Is it worth sacrificing some performance for clearer code?"
• Simplicity vs Elegance: "Are we being elegant or just overcomplicating things?"
• Standards vs Innovation: "Does this actually improve DX or is it just different for the sake of being different?"