What helps me is having good reliable documentation. A painful deployment process (for a side project) is running into unknowns that sends you down a rabbit hole of searching error after error when all you wanted to do is make your app live. π Documentation won't account for every little bug, but good docs from the tools you use are key.
Hi, my nameβs Aaron Powell and Iβm a Cloud Advocate at Microsoft. My area of specialty is front-end web dev and .NET (especially F#), but I enjoy doing silly things with technology.
I totally hear you on good documentation beign a life saver. I spent yesterday down a massive rabbit hole trying to work out why something was falling over only to find that there's a bug in the dependency I was using! π€£
Is GitHub the first stop for you when looking for docs on a project?
What helps me is having good reliable documentation. A painful deployment process (for a side project) is running into unknowns that sends you down a rabbit hole of searching error after error when all you wanted to do is make your app live. π Documentation won't account for every little bug, but good docs from the tools you use are key.
I totally hear you on good documentation beign a life saver. I spent yesterday down a massive rabbit hole trying to work out why something was falling over only to find that there's a bug in the dependency I was using! π€£
Is GitHub the first stop for you when looking for docs on a project?
I'd say the first step is usually searching
moduleName docs
. GitHub is most likely the first result though πSo True, Andy! Developers need good documentation to help keep projects healthy!