Work Log
Record attempts, observed results, assumptions, and decisions in a work log so later readers can understand why a change was accepted.
Record attempts, observed results, assumptions, and decisions in a work log so later readers can understand why a change was accepted.
Write a technical search query with the tool, operation, and relevant condition, preserve diagnostic details, and verify a found answer.
Build a small runnable example that preserves a failure, state expected and actual results, and replace real data without removing the bug.
A ride from 23:00 to 06:00 reports minus seventeen hours. Follow the evidence from a failing example to a tested rule, and record where that rule applies.
Investigate the conditions behind a recurring problem, distinguish containment from corrective action, and check outcomes without assuming one final cause.
Use repeated why questions to trace possible causes, check the evidence for each connection, and branch when one explanation is not enough.