WordPress’s get_queried_object() function has the distinction of being, I think, the most useful core function in WordPress that I didn’t know about for the longest time.

Large, collaboratively-created systems almost always contain pitfalls: misleading bits that don’t work the way they should. When someone thinks of these pitfall-prone systems, the English language, with all its/it’s inconsistencies, often comes to his/her/his or her/their/there/they’re mind.

A guy named Anh read our article on custom taxonomies and custom fields, and contacted us pointing to a similar article he wrote on his own site. His article’s good—what I like about it, specifically, are the bolded key points on the differences between taxonomies and fields, such as:

This article looks at the two major systems for adding data to posts in WordPress: custom taxonomies and custom fields. Since some needs can reasonably by solved by either custom fields or custom taxonomies, we’ll use a practical example—a movie review site—to help define overall principles for when it’s best to use each tool.