« back to discussion

Is it ok to submit small info to Tutorials?

A lot of the time I find a SO question or blog spot which explains one tiny thing about a particular topic, for example: http://stackoverflow.com/questions/38549/difference-between-inner-and-outer-join?rq=1

Is it ok to submit these to Tutorials? They are not really tutorials, but explain important but tiny things very well.

Maybe a 4th category like "Tips" would be nice.

over 3 years ago, by Walkman

5 Replies

lush

I guess that what the wiki is for.

It would be cool if we had a gists/coderwall section to our profile we can share useful snippets.

I think the guy formally known as Pineapple uses a specific app to store snippets.

But I agree, this is a useful necessity.

lush, over 3 years ago

Walkman

I don't specifically talk about code snippets, but rather very small amount of information which can guide you in a specific topic, like a small blog post about something, or questions like that from SO.

Walkman, over 3 years ago

pineapple
posted by Walkman on Mon, Aug 19 at 09:02AM

I don't specifically talk about code snippets, but rather very small amount of information which can guide you in a specific topic, like a small blog post about something, or questions like that from SO.

Hey there,

I would hesitate to allow that... but if they are GOOD, then I think that's ok (tutorials). The problem starts when people just start submitting a lot of blog posts or something else with only a paragraph of text and a snippet. We've had problems with that in the past and it really takes away from the quality. If you feel it is extremely helpful then sure, I think you should submit it.

pineapple, over 3 years ago

Walkman

Or this: http://blog.glebm.com/2013/08/23/screenshots-in-git.html
I think it's a very good idea, but doesn't really fit "Tutorials" and a lot of these would make the overall quality of Pineapple go down. What to do with them?

Walkman, over 3 years ago

pineapple
posted by Walkman on Sun, Aug 25 at 04:54PM

Or this: http://blog.glebm.com/2013/08/23/screenshots-in-git.html
I think it's a very good idea, but doesn't really fit "Tutorials" and a lot of these would make the overall quality of Pineapple go down. What to do with them?

Yes, good question. Those types of fragmented disposable content would definitely dilute the quality (that one is good, but I know most of them aren't). I'd say generally they should not be allowed. If you want to submit that one though that's ok.

pineapple, over 3 years ago


Login or to comment.

« back to discussion

Tutorials are any resources you learn from.

Examples: an intro to html5 screencast, a pdf about git, photoshop effects tutorials, meta-programming in ruby, lambda calculus, higher-order fixed-point combinators.

Tools are websites, apps or services used -on- your project (indirectly), to aid the process.

Examples: A color scheme generator, email marketing software, usability heat maps, css3 code generators, a downloadable png compressor.

Assets are downloadable files used -in- your projects, usually as code, textures, or images.

Examples: a jquery sticky menu, photoshop brushes, background textures, mvc frameworks, twitter bootstrap, 960 grid system.