#All of the Above.
Why restrict it to only one topic? Have a blog post about the evolution of Code Review, and the next one about Code Review itself, or when someone's inspiration pushes them to address language-specific common review issues, if it's good content it's content that we want, even if it's about common bad advice, or anything related to Code Review.
Chaotic? Okay, give it a name then. The scope is "Anything About Code Review" (AA/CR).
It's a Community thing. We chat about it, and then make it happen - we've done that all along, and we're getting pretty good at it (I think). I don't see what could go wrong with anyone submitting a draft to the BCC / "Blog Coordination Committee" (perhaps we can run an informal "meta-election" for seats?), and having it reviewed and eventually published.
The Blog Overflow page has a section titled "But we don’t have anything to write about":
###But we don’t have anything to write about. Sure you do! If there was nothing to write about, your Stack Exchange site wouldn’t exist! Stack Exchange sites trick you into writing.
- Interview top users. Just who is that user who is shooting up the reputation leagues?
- Highlight top content. What great question was posted on the site recently? Recognize it! Don’t just copy the question and its answers to the blog, blog about the question and its answers. A fine line there, eh? Delve deeper into the question or an answer. Add more context. Compare or analyze answers against each other. There is a lot to work with here.
- Review a product. Reviews don’t fit the Q&A nature of the sites, but these rules don’t apply on the blog! Between a review written by a random person on the internet and a review written by a user on the site who consistently gets a lot of upvotes, which review would you trust more?
- Tell us an interesting story. Did you go on an incredible cycling trip? Play a really interesting game? Read a great book on math? All it takes to get started is a set of pictures or screenshots you can share with some narrative stitching it together. So long as it’s topical and you’re excited about it, others in the community would probably enjoy sharing your experience!
- Explore hot topics. Is there a topic on your site that keeps getting asked about over and over? [cough]linked-list[cough] Maybe some tips or a closer look at the topic would interest the community.
- Keep up with current events. What is making news for your community? What interests the community?
A lot of this contributes to making the blog interesting, with new topics every issue, and a lot of this contradicts the idea of having a narrow idea of what this blog is/should be all about.
It's about Code Review and its community - about our meta-frustrations (poor questions, graduation, etc.), our questions and our reviews, the review challenges, and everything else we do and think of; it's about us all, and everything that comes with that - monkeys, acronyms, zombies and all.
