Chef = a configuration management tool
Recipe = an individual Ruby script that makes sure something is installed and configured correctly (e.g. a mysql recipe)
Cookbook = a bundle of recipe(s) and basic metadata (what do these recipes do, who wrote them, etc.)
Supermarket = a community site with common cookbooks, what others would call a "hub", "central repository", "marketplace" or "store"
knife = a command line tool for managing your chef installation
Test Kitchen = a test suite runner
Cookstyle = a code linter
However, now that Chef has gone full Enterprise (never go full Enterprise), the names are now all enterprisey-sounding: everything is "Chef XYZ", e.g. "Buzzword you know + Buzzword you don't", harnesses the CxO's FOMO. Chef Habitat = write declarative rules for applying cookbooks to machines. Chef InSpec = auditing/compliance. Chef Workstation = what you would have normally installed anyway, the development kit and runtime tools, but now it's EnTeRpRiSe, ...
It's written on the wall for Ansible, Red Hat/IBM is busy churning out the product space already.
It's weird that there's so much money in enterprise IT. If anything, they should know the value of standards and reference implementations.
Almost 25 years ago, SSH went full enterprise and promptly died. Somehow the need for a simple remote shell protocol didn't, though, and now OpenSSH is instead perhaps the most valuable tool we have.
And if the junior doesn’t know the story of little red riding hood, well then it is your lucky day and you are one of the 1 in 10000 who gets to tell them the story.
Then when things go off the rails, I can say 'Shaka, when the walls fell'
Darmok and Jalad at Tanagra.