I find that Code Review is getting pretty boring and unprofessional. The reason why I think this way is that many good questions about real-world problems don't get very much attention. Instead, the hundredth implementation of linked-lists, heaps, project-euler, factorials, fibonacci, sortings or other programming challenge garbage get countless upvotes and answers. I'm not posting any links because I'm pretty sure you know what I mean.
Consequently instead of attracting more professionals to come over to Code Review to share their code and use-cases, and who could also take a look at some other interesting problems and share their valuable knowledge, we seem to favor simple and recurring questions by not voting for the interesing ones and not encouraging their authors for providing as much context as possible so that everyone can learn from them - OP, reviewer and especially other readers.
This has also another negative side effect: there seem to be very few active users who write reviews or share their solutions to intriguing every-day matters.
I also think we are often too forgiving with questions that lack context and don't get closed. This gives a signal that poor questions are acceptable and the only beneficiary is the OP because only they know enough to be able to apply any suggestions. This makes Code Review not very useful to others.
I wish there would be some additional categorizing to easier distinguish informative questions you can learn from, from those that are pure waste of time. But since there is no such thing I usually see Code Review like this: many upvotes(7+) and answers (3+) = very likely not worth the time; few upvotes(<4) and few answers (0-2) = highly likely something interesting.
Is there anything we can do about? I really liked Code Review for it's every-day riddles and learnt a lot of new stuff myself either by trying to crack some of them or just by reading and seeing tools, APIs or libraries I've never seen or tried to used in a certain way before, but recently it's been somehow mostly only unexciting junk. I don't like Code Review as I used to.
This has bothered me for quite some time already and can at the same time be seen as another answer to To serve, what is it to ask for review? that tries to promote poor quality input. I 100% disagree with it. Both, well written questions and answers should be CR's target. Not questions with vague description and unclear purpose of the code.
Quite contrary to the other question I suggest we be a lot stricter about the rules and encourage people to take more time and present their code in a more attractive and informative fashion because I see Code Review primarily as a platform that should be educational to more people than just to the OP.
In other words: what can we do about under-supporting/promoting good questions and over-promoting the not so good, attractive or simply bad ones?