Page MenuHomePhabricator

Provide documentation explicitly describing what a "root problem" is
ClosedPublic

Authored by epriestley on Dec 8 2015, 6:21 PM.

Details

Summary

A guide to basic skills every software professional should have.

This is so fundamental that I don't think the document is actually helpful, but we can try it I guess.

Test Plan

Reading?

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Provide documentation explicitly describing what a "root problem" is.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
  • One fewer spelling mistake.
chad edited edge metadata.

only this photo is more awesome.

readImage.jpg (314×236 px, 21 KB)

This revision is now accepted and ready to land.Dec 8 2015, 6:30 PM

One idea, to really spark the importance of getting to the root problem.
Adjust the language where necessary of course.

src/docs/contributor/describing_problems.diviner
24

"Or we may not understand the true meaning of your problem, and mark it as wontfix"

This revision was automatically updated to reflect the committed changes.