Explain Meta Programming Like I'm Five

In short, meta programming is writing code that writes code. Or, in other words, imagine a robot that can not only build other robots, but also rebuild and modify itself.

Bob is 5 years old. (developer)
Bob have to draw a sunny house. (new feature)
Now imagine that Bob write "Sunny house" on a drawing sheet (comment or whatever used for meta programming).

He push THE magical button of the pencil (compile code or interpret it).

TADA ! There's now a sunny house, despite he didn't draw it, he asked to his magic stick to make it and the sunny house is done (the feature).

Bob is now 25.
He have to create a new URL. The controller have to use /blog/blog_id url, be seen as "blog_list" and the blog_id MUST BE a digital, any digital. There must be an error if the page id don't meet the requirement.
Bob use Symfony, write an annotation of one line and the job is done.
(Symfony core processed to write the code.)

Here's a real example :
class BlogController extends Controller
{
/**
* @Route("/blog/{page}", name="blog_list", requirements={"page"="\d+"})
*/
public function list($page)
{
// ...
}
}

If programming were a story in a book, metaproprogramming would be a story in a book that tells you how to write stories. Or for the 5 year old that lives 10 years from now, metaprogramming is like a 3D printer that allows you to also 3D print other 3D printers.