I have one problem with this. Assuming that there was a blog that we can contribute to, would there be contributions?
It's nothing against the people here, trust me.
If we look at all the blogs and see how many posts have been made since 1st jan 2014:
Science Fiction & Fantasy: 54
Server Fault: 7
Super User: 2
Information Security: 9
Code Review should have a blog.
The benefits I see are:
a mechanism for less fact-based / more opinion based content that the Q&A component
another way to allow the community to participate and express themselves... perhaps:
no formal 'bloggers' per se
'committee' of some sort that 'vettes' submissions.
A place to describe the culture of Code ...
Code Review with a blog is a very good idea.
Although many codes are posted here for review, I think the common points can be accumulated and as a learning be shared in the blog along with some code snippets.
This can help in analysis, and will also invite people who would not come to CodeReview post because they were not concerned with the code under ...
One post in a whole month? Less with more contributors? I'm sure I can do that. I'd happily volunteer for coordinating the blog as well, but I think we should have some "blog committee" and a dedicated [private] chatroom where the coordination will take place.
I can think of several things I could easily write about...
Beta Progress | About Code ...
Meta-Coordination, and more
I am happy to:
facilitate the blog for any issues where moderator assistance or intervention is needed, locating the right SE folk or resources, etc. Wherever keeping the blog active requires it, and a moderator assistance can help.
edit and/or review draft blogs
write a blog entry occasionally (one every few months or so), if I ...
Would I like a Blog
Yes I would. I would like to see articles on how to code review better. I would read artciles about best practice on many major languages.
Would I contribute
Personally unlikely. I have a hard enough time writing for my own blog.
But I would comment on things I read in the blog.
But are there people willing to contribute (its a lot of ...
Review Open-Source Software
On Code Review, asking to review other people's code is normally off-topic.1 However, a blog is not subject to the same restrictions.
Unlike most answers on Code Review, which are directed to a small audience, a technical review of widely used software would be of general interest. If we blog about a security, correctness, or ...
We don't have a blog yet, so the dates ought to be relative to some hypothetical start date...
I suggest post one be posted at T, where T is the Friday immediately following our blog's launch date.
T : 1st post
T +2 weeks: 2nd post
T +4 weeks: 3rd post
T +6 weeks: 4th post
Let's kick-start with a post every 2 weeks for the first 5 posts. 1.5 months down.
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 ...
I don't think I'd be of much use as a post contributor, but I'd love to proofread, review, and edit submitted posts, and support contributors in any other way. Whether I review crappy code or enlightening blog posts, it's all just another kind of nitpicking constructive criticism.
I am not sure how other sites manage their blogs, but a meta tag blog-review ...
I could contribute on an occasional basis. Potential topics:
Things I recently learned via CR
Why I review other people's code
Interesting code/question/technique that was recently posted on CR that deserves deeper dive, more explanation
Collection of commonly given advice for C++ code review (doesn't necessarily mean "best" -- just "frequent.")
I didn't know SE actually had blogs!
I would be happy to write occasionally and review other people's work.
I really liked the idea of reviewing open-source software.
Also, I like the idea of writing simple How-Tos for more specific/obscure programming issues. Perhaps explaining how to use poorly documented APIs (IXMLDom and ADO for C++ on Windows) or ...
As several people have already said they would like their post reviewed when they write one, why don't we write them together as a community answer for a meta question per blog post?
Several answers could be used to split it into smaller parts that are edited independently (to make conflicts less common).
I would love to write some blog posts. It could only be on rare occasion though, I'm too busy to do it on a schedule.
I would be more available to edit/review blogs, and that is something I am willing to do as well.
I would also be happy to write some articles, probably once every few months, but just like Malachi I would need a complete review of the said articles before posting them.
Therefore, I'm really a fan of having a dedicated blog committee to review and validate the articles (we will later find an overly long acronym for the committee to make it sound cool). ...
Let's get this started
Hello, I'm Clippy. It looks like you're trying to start a Code Review Blog. Would you like to:
get help with writing a “hello world” entry?
write the blog without help?
give me your delicious brainz?
BLAM! Oh, sorry if zombie Clippy was annoying you – we aren't that fond of zombies ourselves. In fact, we had quite the infestation ...
Oh hey, that's a perfect line in your C implementation of Hello World! But wait, where's the rest of it? We gotta see that too!
Here on Code Review we chew on your working but crappy beast of a code and spit out stunning elegant beauties. Ok that's a lie, but we do tell you how to do it. And that's actually better:
Give a man a ...
I would be interested in writing for the blog as well.
I think I will particularly talk about [unit-testing] but if I find a nice topic I could also expand on more metaprogramming stuff like code generation/reflection and how it might solve common problems or writing your own diagnostic tools for code.
I'm willing to blog
I am offering to help a bit every now and then with the blog (like once a month or so).
Things I could do on the blog:
Trying to attract more users to the site, and trying to make the new ones stay
Post about learning a new language, and ways that you can learn them (Can be CR related!)
Highlights of CR questions and answers
What's going ...
About Code Review itself
How to write a good question or a good answer.
What's on/off topic here (it won't hurt to remind what's good and what's not).
Why most of the questions migrated on Code Review are actually off-topic for this website.
pulled from Morwenn's Phase-1 meta question
SE is no longer starting new individual site Community Blogs
tl;dr (as of 1 year ago) follows
[...]we at Stack Exchange have not been doing enough to make blogs work[...]
[...]Blogs aren't Q&A, but the spirit remains the same - a blog with content but no updates is a promise unfulfilled by our network.
Right now, out of the 22 community ...
I would like to chip in as well for both reviewing posts and writing the occasional one.
In terms of what I would write about, I would probably steer towards doing some form of deep dive. So take an interesting question from the last x days and review it in depth, explaining why it's better to do x rather than y (note: this wouldn't be an actual review, ...
Language Specific Common Review Issues
Namespaces in C++, C# in general, etc.
pulled from Morwenn's Phase-1 meta question
Yes, let's have a blog.
And here is why...
Code Review is different to (most) other StackExchange sites, and the ones it is similar to are the ones with good blogs.
My thoughts regarding naysayers on the point of content
The big difference with Code Review is in the content, and the way we go about producing that content.
Unlike sites like StackOverflow, ...
As one of the referenced bloggers, I would not contribute to a Code Review blog.
Other bloggers have mentioned they also wouldn't contribute. I can't see there being enough contributors making enough contributions to be worthwhile.