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
F15592994: D14707.id35575.diff
Sat, May 10, 8:00 AM
F15591094: D14707.diff
Fri, May 9, 11:13 PM
F15529309: D14707.id35566.diff
Tue, Apr 22, 6:35 PM
F15528461: D14707.id35567.diff
Tue, Apr 22, 11:21 AM
F15525987: D14707.id35566.diff
Mon, Apr 21, 6:20 PM
F15519406: D14707.id.diff
Sat, Apr 19, 10:39 PM
F15516034: D14707.diff
Fri, Apr 18, 3:37 PM
F15496326: D14707.diff
Sun, Apr 13, 6:29 AM
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
Branch
ex23
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 9383
Build 11159: Run Core Tests
Build 11158: arc lint + arc unit

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.