Paths

Table of Contentst

Differential D14707

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

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

Details

Reviewers

chad

Commits

Restricted Diffusion Commit
rP3438664b3857: Provide documentation explicitly describing what a "root problem" is

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 updated this revision to Diff 35566.Dec 8 2015, 6:21 PM

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.

only this photo is more awesome.

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

That photo is pretty awesome.

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`"

tycho.tatitscheff awarded a token.Dec 8 2015, 8:13 PM

Closed by commit rP3438664b3857: Provide documentation explicitly describing what a "root problem" is (authored by epriestley, committed by epriestley). · Explain WhyDec 8 2015, 9:01 PM

This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

Path

Size

src/

docs/

contributor/

describing_problems.diviner

159 lines

feature_requests.diviner

4 lines

Diff 35566

View Options

src/docs/contributor/describing_problems.diviner