Project flagged as "Wrong type"?
-
This was submitted as a Project: How to implement a Custom Authorization Filter in C# .NET Core[^] I noticed that several experienced reviewers have flagged it as "Wrong type". What am I missing? There are many Articles that should be Tip/Tricks, but I thought pretty much anything could be a Project if it discussed a repository, unless the documentation was poor enough to simply reject it.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
This was submitted as a Project: How to implement a Custom Authorization Filter in C# .NET Core[^] I noticed that several experienced reviewers have flagged it as "Wrong type". What am I missing? There are many Articles that should be Tip/Tricks, but I thought pretty much anything could be a Project if it discussed a repository, unless the documentation was poor enough to simply reject it.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.Project type submissions are actually supposed to be the same full-fledged articles; a thorough explanation of their code, how it works, why they made it, etc. Unfortunately, most of these Proejct submissions are just people sharing their GitHub projects, which is totally understandable. If it were me, that's what I would expect. What usually happens is this gets into the realm of tool sharing, which is not what CodeProject articles (or CodeProject) is about. So sadly, I delete most of these submissions, while offering to the author, "hey, we'd love to have this if you were able to make these additions." If I had to guess, these reviewers are flagging this article as "Wrong type" because they want it to be a tip. My experience is that reviewers feel like anything that's short, or simply "not good enough to be an article" should just be a tip. Like a dumping ground of sorts. "This is good, but not article good, so, it can stay, just over there." But what tips are supposed to be is essentially extremely condensed articles. You still have to explain your code, what you're doing, why you did it, but it's a short solution to a simple problem that doesn't require / ask for in-depth explanation. Here's a recent, perfect example: Access your Microsoft JSON DOM the easy way with the dynamic keyword[^]
Thanks, Sean Ewington CodeProject