Bugs and Suggestions

10-Feb-16 7:27

Glad you got what you want.

No argument though. I read many times what you wrote. And the answer what I gave and what Sean gave landed on the same content except different links.

Here is the content both places.
What I gave you as a link :

What is a tip?
A Tips and Tricks post is a single problem, with a single solution, and a super-short write-up. Ideally you could consume it in under 30 seconds.

And what Sean gave you :

So we are going to clarify what a tip is: A Tips and Tricks post is a single problem, with a single solution, and a super-short write-up. Ideally you could consume it in under 30 seconds.

I don't think you need article clarification.

Nelek10-Feb-16 21:07

10-Feb-16 21:07

Another time... the question was not about the definition of a tip or the definition of an article, I have read those definitions surely more than you and I use those links always in my messages to articles in moderation.

The full point was about the comparison of both and specially the undefined grey zone between them and how to consider it.

Thanks for trying to help though.

M.D.V.

If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.

Master.Man198011-Feb-16 4:08

11-Feb-16 4:08

Nelek:
I have read those definitions

Actually my answer was not to give a definition. I assume you get the idea of differences or grey zone issues between Tip and Article when you read it and understand their definitions. There is big difference between reading and understanding. To me, this resolves the grey zone.

Now let me step back and ask you a question.
What things you understand as the grey zone issue ? Members will get benefit from this.

modified 16-Mar-16 14:54pm.

Nelek11-Feb-16 12:45

11-Feb-16 12:45

Master.Man1980 wrote:
There is big difference between reading and understanding.

It is not the same not understand something, that understand it wrong. With the second you think everything is ok, until someone shows you it is not. I thought I had understood it, but the comment of the other day told me "hey, maybe is not like that". So that's exactly why I am asking, I am asking for clarification.

Not all users are english native (I am not at least). What for you is so clear, for other might be not. And if you are active in the moderation, you will see I am not the only one with similar concept (even many english speakers think/thought like me).

And since I have received a concrete answer with something it is 100% concrete that I find crystal clear... this thread is done for me.

Thanks for trying to help.

M.D.V.

Master.Man198012-Feb-16 4:58

12-Feb-16 4:58

Nelek:
Thanks for trying to help.

You're welcome.

Sean Ewington10-Feb-16 5:28

Sean Ewington

10-Feb-16 5:28

Because of the confusion, we've tried to clarify: Tips/Tricks - CodeProject[^]

Thanks,
Sean Ewington
CodeProject

Nelek10-Feb-16 5:56

10-Feb-16 5:56

OK... definition is now clear. Thanks for the answer and the explanation Sean.

If I understand it correctly, the focus is to let tips short and concise and join the grey zone to the articles. I will accordingly reduce my "Have you consider..." posts

M.D.V.

User 1106097910-Feb-16 11:05

User 11060979

10-Feb-16 11:05

From my point of view it is simply overkill of definitions over definitions again. Let the author decide whether it is a tip or an article. What I agree is, that an article needs a certain level... what certain level means I'm not able to define.
But a definition, that a tip needs to be readed in 30 seconds.... no sorry, it's stupid. Next definition will be Lounge discussions needs to be readable in 10 Sec...
Only my mind, does not count anyway.

modified 19-Jan-21 21:04pm.

Chris Maunder11-Feb-16 3:35

Chris Maunder

11-Feb-16 3:35

Way back in the dawn of time everything was an article. There were no tips. The cutoff for acceptance was

1. did the author have the rights to publish it
2. was it on topic
3. was it of sufficient quality

We then added Technical Blogs and Tips/Tricks

These are all still "article types", meaning they must all adhere to the three criteria above.

Technical blogs are technical articles, not ramblings about what you did on a Saturday. They are simply an article that's been posted in a blog and will be aggregated by our crawler and posted as an article.

Tips are "tips". Short, punchy, consumable-in-30-seconds type things with the goal of providing a quick answer to a specific problem.

What I've seen happening is that the tips category has been used for "things not worthy of being an article". If it's not worthy of posting it should be removed. If it's a tip it should be a tip. If it's not a tip then it's an article. "Article" is actually the catch-all here, not tips, and this then leads to the other conversations about whether we need a HowTo category, a Walkthrough category, a Tutorial category, an Interview category etc etc.

The question then comes down to:

1. What value will this add
2. Will this make it more painful for authors.

At this point I'm not willing to introduce more article categories until I feel the "Tips" category is working. The blame for the confusion must lie with us: we're the ones who have been explaining the difference. We'll be the ones to clean it up (mostly). Hopefully from now on everyone else has a clearer picture of what we're trying to do.

cheers
Chris Maunder

Master.Man198011-Feb-16 4:13

11-Feb-16 4:13

I believe all is there from Sean article. Code Project Article FAQ[^]. It just a lack of understanding it.

Nelek11-Feb-16 12:40