Great question. I find as a tester, who tested first and was introduced to coding later, having a good set of examples of code implementation or up to date docs in the readme was critical to my success.
There are many repo's and libraries that I started with and just couldn't use, or get off the ground due to lack of 'how to use it'. I brought this up with other developers and they mentioned, just go read the code, but at that time in my career, I had no idea what was happening in the code. This is a great place to start in my opinion.
Great question. I find as a tester, who tested first and was introduced to coding later, having a good set of examples of code implementation or up to date docs in the readme was critical to my success.
There are many repo's and libraries that I started with and just couldn't use, or get off the ground due to lack of 'how to use it'. I brought this up with other developers and they mentioned, just go read the code, but at that time in my career, I had no idea what was happening in the code. This is a great place to start in my opinion.
This is also very true. @itsasine a good example of a very well documented codebase is Dev itself.