Creative method

A creative method is a structured practice for getting past a roadblock, exposing assumptions, generating alternatives, or improving an idea. It treats creativity as a set of usable tools rather than a rare talent: a programmer can deliberately change perspective, ask better questions, or give an unfinished idea another round of attention. section 8.1 section 8.4

Methods are not isolated tricks. They interact with technical knowledge, communication, constraints, critical thinking, curiosity, and a productive state of mind. A useful habit is to select a method that matches the obstacle, then test whether its surprising output actually improves the work. section 1.4 section 1.4.1

A practical toolbox can include:

• Ask naive questions or pose “What if...?” scenarios to reveal hidden assumptions, implicit knowledge, and consequences. section 8.4.1
• Use the Lunette technique to move between levels of abstraction: zoom into code, then step back to a bird’s-eye view. section 8.4.1
• Reverse brainstorm by voicing criticism first, then using it to motivate improvements. section 8.4.1
• Create unusual classifications of project concerns, or imagine an expert’s perspective to disrupt familiar thinking. section 8.4.1

Creative methods can be borrowed from art, writing, philosophy, and agile retrospectives, but borrowing is not blind imitation. Paint handling may not help a software problem directly; higher-level practices and habits may. Keep the playful experiment, but verify its value in the actual programming situation. section 8.1 section 8.2

Figure 1.3 The Creative Programmer mind map that ties together all seven chapters of this book.

Use the mind map to place creative methods among the connected dimensions of creative problem solving, rather than treating them as a separate bag of tricks. section 1.4