Page MenuHomePhabricator

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

Authored by epriestley on Dec 8 2015, 6:21 PM.
Tags
None
Referenced Files
F19798683: D14707.id35566.diff
Feb 27 2026, 9:54 PM
F19796579: D14707.id35566.diff
Feb 27 2026, 4:28 PM
F19796206: D14707.id35566.diff
Feb 27 2026, 1:36 PM
F19793437: D14707.id35575.diff
Feb 26 2026, 5:02 PM
F19687369: D14707.id35566.diff
Feb 9 2026, 3:27 PM
F19687349: D14707.id35566.diff
Feb 9 2026, 3:18 PM
F19661335: D14707.diff
Feb 7 2026, 6:19 AM
F19611022: D14707.diff
Feb 3 2026, 5:35 PM
Subscribers
Tokens
"Love" token, awarded by tycho.tatitscheff.

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.