Part I: "RTFM"
It's bluntly obvious what the issue is, but out of nowhere, your question has 6 downvotes, is put on hold, and you're banned from asking questions. All because you asked a question on a site called Code Review.
What's bluntly obvious to anyone that bothered spending 35 seconds of their lives reading the /on-topic page, is that the question is blatantly off-topic.
The downvotes don't come from out of nowhere, they come from site regulars that feel at home on this site. For the most part these regulars don't like downvoting, and would rather greet a newcomer with upvotes, a warm welcoming comment and a plush unicorn - but when a new user is asking their "where's my bug" question here because they got question-banned on Stack Overflow, or when they can't be bothered to read a tiny little bit about what the site they're about to post on is all about (and more importantly, what it's not about), then the question is off-topic and needs to get off the front page no matter what - we don't want to look like we're closing every question that's asked here, so closing isn't enough, they need to be either downvoted to at least -4, or outright deleted.
We're not snarky power-hungry jerks looking to poison the life of anyone coming here with an off-topic question: everytime such a post is salvageable, I've seen this community put a lot of effort into getting an iffy post back on track. It even happened that an off-topic question was edited into shape, and went "hot" and generated loads of reps for both the OP and the answerers. But broken code is broken code, and can't quite be saved - asking how to fix a specific coding issue simply belongs on Stack Overflow. Dumping walls of code onto this community and expecting someone to spend half a day finding your bug for you isn't respectful of the community either. And we comment to that effect: it's pretty seldom that a user is left without a single clue about why their post is being downvoted and/or put on hold.
We have a scope that we defined and then refined over the course of 4 years in public beta status, and like every single Stack Exchange site, you can't just look at the site's name (or icon, for that matter) and expect to know what's on-topic and what isn't, and what kind of answers are acceptable and what kind aren't.
Sure, play by ear and skip the manual. But then, don't complain when you get downvoted and closed.
One doesn't get question-banned for a single offense. To get to that point, a new user needs to repeatedly post poorly received questions - turns out, everytime a question gets closed, the message points out exactly why that happened, and links to relevant meta posts and help center pages to help you understand why this is happening, and how to avoid repeating that mistake. We can't force anyone to read the manual. But when it gets to a point where the system itself thinks you simply don't care about the rules of the community you're trying to join enough to even try to ask an on-topic question, the only thing it can do at that point is effectively to question-ban your account.
Reading the /on-topic page takes literally 2 minutes, and then if you read that and still have questions, you can search meta. And if you still ask without reading, we'll point you to resources so you can fix your standing. But we can't fix that for you, and if you don't want to help yourself, we will move on to helping new users that want to be helped.
Remember that you where once new as well.
Trust me, I do. And the minute I started being serious about my membership here, I read the help center and learned the rules. Wasn't hard, and it didn't even hurt.
Part II: Logo vs. Broken Code
I'm posting from my phone right now so it's a bit of a pain to fetch the link, but if you browse the related posts from the design announcement meta you'll quickly find a meta dating back from the Dark Ages, where the people from the community were giving their input on what the design and feel of the site ought to be - turns out the magnifying glass concept was a clear winner and by far: the SE design team did a terrific job at turning that concept into a beautiful design.
But you shouldn't judge a book by its cover, or a video game by its packaging, and if you never heard of CR you can't pretend to think you know what it's all about just by looking at its icon, regardless of what that icon is. Same for any SE community out there.
Here's a comparison between the last 90 days and the last 7 days (and heck, last 2 days as well):
Last 90 Last 7 Last 2
Closed%: 31.96% 34.49% 34.09%
BrokenCode 66.52% 64.22% 63.33%
NoCode 6.68% 3.67% 3.33%
StubCode 14.45% 11.93% 20.00%
Sure, the closed% bumped up a bit - but that was expected. Do we get more broken code? Nope! Actually, "too much broken code" was identified as a major issue all the way back in June, so that's nothing new either.
What about the activity then?
The design announcement was 7 days ago - so the last data point (11/28) aggregates that week's activity figures; notice the sudden climb, but also notice the same sudden climb 52 weeks ago as well: activity is up, but it was almost predictable - just like the upcoming December dip for the Holidays. Let's see if this week's data changes the numbers on the scale...
Feel free to query SEDE, you'll find that closed & deleted posts have not gone through the roof in the past week - quite the contrary, these figures actually went down, while total number of posts went up: there is no correlation whatsoever between the new design/logo, and an alleged increased number of closed/deleted posts (although yes, percentage-wise, closed+deleted posts did go up slightly, but nothing worth a panic attack ;). Even downvotes went down from the previous week, while total number of votes went up 80%-and-some.