How I Think About Solving Problems

Writing on his personal blog, Nicholas C. Zakas describes how he arrived at a repeatable way to evaluate the problems that come up during engineering work: a short list of questions he asks himself, in order, for each problem as it arises. Going through them sequentially, he says, helped him make the best decision possible in each case.

The five questions

  1. Is this really a problem?
  2. Does the problem need to be solved?
  3. Does the problem need to be solved now?
  4. Does the problem need to be solved by me?
  5. Is there a simpler problem I can solve instead?

The framing connects to an earlier discussion of what it takes to be a senior developer; Zakas argues that this kind of thinking belongs on that list too.

Source: Nicholas C. Zakas, via CSS-Tricks.