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
Unknown Object (File)
Tue, Feb 11, 12:02 AM
Unknown Object (File)
Sun, Feb 9, 12:02 AM
Unknown Object (File)
Tue, Feb 4, 1:58 PM
Unknown Object (File)
Wed, Jan 29, 7:36 PM
Unknown Object (File)
Mon, Jan 27, 10:14 PM
Unknown Object (File)
Fri, Jan 24, 10:20 AM
Unknown Object (File)
Jan 21 2025, 9:57 AM
Unknown Object (File)
Jan 20 2025, 12:10 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
Branch
ex23
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 9384
Build 11161: Run Core Tests
Build 11160: 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
23

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