Comment by dvt
> For this case, i will probably lift off the example from the library docs. Or spend 5 minutes writing a bare implementation as it would be all I need at the time.
Both of these would take longer than 5 minutes. There's also no "lifting" as this case involves both Provider and Context, so you'd have to combine React doc examples.
The only alternative would be knowing it by heart, which you might, but I don't (nor do I particularly care to). There's definitely a force multiplier here, even if just in the boring boilerplate cases.
What about understanding. I've not touched React for some times, but I'm familiar enough with the library to locate every piece of exact information I need. And this for a lot of framework, languages, and libraries I've used over the year. There's documentation browsers like dash.app, zeal, devdocs, and various cheat sheets that help.