"I never got how this worked" ~ is a common talk heard by all developers at one time or another, the other one is - "This is black magic" or it works on my machine or it should work.
This talk aims to highlight the importance of reading the documentation attached to a work repo. This talk is the other side to Write F*&K!ng ReadMe. It highlights how to demystify one's code once created as a repo, using the instructional manual AKA the ReadMe.

It aims to help developers to understand :
- the importance of ReadMe as a tool to understand how to use someone's code.
- how to break the ReadMe down to decipher how a project is coded or built and how to use it.
- how to use ReadMe to get more resources on the project if needed.
- An actionable breakdown of how to figure out how to
use a ReadMe.
- finding out about open-sourced contributions etc.
- provide actionable steps for all of the above.

- This talk is aimed to be a community talk.
- It can be 30 - 50 mins long based on the audience.
- target: Anyone but catering mostly to entry-level and mid-devs.