When I first started learning to code, I had a wealth of resources around me: two mentors, a paid online learning module with Codecademy, and an ever-growing list of friends who would show up to my streams to help me learn. Notice I didn't say docs:
I couldn't depend on docs to help me when I was lost because I was new and almost every doc went completely above my head.

"Ah, but Pj, docs aren't for brand new coders! It's for people looking to learn about something specific! It's for experienced developers!"
I disagree. Docs are for everyone.
This talk will aim to answer questions like:
"What am I assuming about the person reading these docs?"
"How can I help make my docs better?"
"Who's job is it to make the docs?"
"What SHOULD docs function be?"

While this talk focuses on docs, it is not a presentation strictly for Technical Writers. This talk is for everyone who ever read a doc top to bottom and didn't find what they were looking for and then found the answer in a 10-year-old Stack overflow question.