Software engineering
Name the real problem, break work into parts, and test what you think you know.
Thinking practices that matter here
- Problem-Solving & Creativity
Problem framing
The first wording of a problem is a hypothesis, not the job itself.
- Problem-Solving & Creativity
Decomposition
A problem that feels huge often becomes workable once it is split into stages.
- Learning & Metacognition
Illusions of competence
A clear page can feel like a clear idea. Those are different.
- Evidence & Epistemology
Confirmation bias
A hunch can steer you toward the evidence that flatters it.
A sample scenario
A bug report names the wrong layer. How do you reframe before writing the first patch?