Consider putting the log message under the frog

[00f2ff]

Another way to think about logging is as a wavering request to the computer to acknowledge that developers did in fact write code that does the thing or gets to the place it needs to go. The frog is a bit like an abstract, amphibian version of Clippy, and it reminds developers they are not alone. But if the log was under the frog, that is, providing structural support and consistency to that frog's life, perhaps then developers would feel proud of their logging.

One option is to repurpose console.log.

[davidsharp]

console.frog on a console.log, I like it