3 ms·

"A problem well stated is a problem half solved"

• gaius 13y ago
  Also see the Kepner-Tregoe method. Doing the "is, is-not" step really helps narrow it down.
  • kamaal 13y ago
    Programmers have been doing this from more than half a century. Its called debugging. Its basically to learn to localize the problem to a specific part in the code/system. Study the inputs and outputs to that system. Establish single responsibility to that part of the code. Now study the input and expected output from that part of the code. If they mismatch, correct the code and test it out for all possible values of the input. Additionally automate it/check list it such that those mistakes are not made in the future.
    • Swannie 13y ago
      When you are dealing with multiple systems and sub-systems, it's not so easy.