[META] I know the sub is new but stop posting links. Post real content why something is good. Its getting real fanboy-ish when there is potential for more.

For real guys, this is getting absolutely ridiculous. And I know the sub is new, but whenever someone links a post to say, vim - tmux - sublime text etc. There is no point. This is getting posted for the link karma, not to showcase a tool, feature, or product and certainly not to inform anyone of the value of these things. It will be upvoted because it is popular, but the community gains nothing from it. Don't let this be a circlejerk please.

There is a HUGE potential to have this subreddit be a platform to expose and be exposed to all the great new ideas and tools that are out there you haven't even thought to look for, to share the knowledge on how to use these things and what makes them great, superior tools comparatively. It is exciting and you should be excited about it, but just throwing out links is not the way to do it.


Now I don't mean to be the buzzkill on your internet points, but if you use something, you like something tell us what's so special about the damn thing and why we should care. Take some time about it.

We, every single one of us, has spent a TON of time doing our own research, professional or novice, on specific tech stacks, applications, operations, to accomplish certain tasks. And I mean a ton. Why cheapen the content here by linking a meaningless website when you could help someone?


I will give you an example.

Has anyone heard of Middleman?

Story time. Me, coming straight out of college, thought - what is the first thing you need to start in freelance web development and make a quick splash in the biz? Your own website. I was wrong of course, but needless to say I spent 5 months looking in every nook and cranny of the different technologies I could use to put out something on the web. And I learned a lot.

  • Now the first thing you will realize is that you want to template content. Well what's out there? Anyone in web development and hating their job will inform you that CMS's still exist. Take your pick Wordpress, Joomla, etc. And you will realize that all that overhead is totally fucking unnecessary to post a couple portfolio pictures online - I mean, a MySQL database backend for a 3 page site is excessive to say the least.

  • Then you will look into Django, Rails, yadda yadda and if all you want is a simple website to quickly throw on the web - diving right into these is (while worth it) intimidating. Less overhead than a CMS? sure - but there is still some there, and if all you want is the simplest way to produce simple website there are better options.

  • Static site generators! I paid all this money to go to college and became very familiar with HTML, CSS, Javascript, and then to apply it - well, they didn't tell me jack shit. I'm not knocking Rails/Sinatra or Django and all that, but are they really that straight forward when you haven't been exposed to RESTful APIs before? And do you need to know that (it is certainly a good thing to learn but now isn't the time) to put up a website ASAP? Nope, Jekyll and Middleman

Why would anyone care about this thing? What makes it so great?

Well, it is a static site generator - it runs through all of your dynamic templates and database content and smushes it together, links all the pages, creates a sitemap, and spits out a pure HTML CSS Javascript website build with no overhead other than what is seen on the page. You won't need to host your databases on your server, you won't need to maintain a complex HTTP request chain if you don't want to, and making working mock-ups or prototypes could not be simpler.

More over, since it is basically an HTML preprocessor - you can use ANY language you want, templates can be erb, slim, haml - write in Markdown - hell it supports them all. Frontmatter all the content for a page, you don't need any database more complex than a yaml or json file for all the sites content. In development it supports ActiveReload, file compression at build time. The fact that it is a preprocessor itself makes it perfect to use CSS preprocessors like Susy and Compass right there during development with no added overhead and all of their features.

And even if you have seen all these things, I think that is a little more informative than linking to https://middlemanapp.com/ for a pretty thumbnail, don't you? Do you want to hear about something? or do you want to learn about something in this sub?


tl;dr I am not sure of the mod's vision of this subreddit, or where they want to go with it. Stop linking trivial, popular things. If you're going to post something, put some content behind it and reasoning.

Please, up vote substance and not because you use it or have heard about it.

Posted Feb 11, 2015, 10:35 PM UTC

8517
kyrul•

I like this. Perhaps there could be a rule for self-posts only, with a link to the tool in question within the self-post, and some guidelines as to what you should say about it.

e.g.

[Name] - [Link]

[Summary description]

[Cool examples of what it can do: code, screenshots, etc.]

[Anecdotes, comparison to similar tools, pros/cons]

16
-blindOP•

Exactly, wouldn't it be cool if people provided some sort of introduction to something instead of having to scour random blogs for it to be accessible? This subreddit could be incredible

6
JewCFroot•

I think is wonderful. Self posts tend to encourage quality posts more than anything else (as people get to put the time into reading).

3
alinroc•

What if it's a link to a blog doing exactly what's being asked here? In that case, you'd just be regurgitating the content on the linked blog, which doesn't really add value.

1
-blindOP•

You're missing my point, let's say you have a tool like Vagrant for example. Do you know how many differing Vagrant howto's are out there on different, some obscure some not, blogs? Vagrant isn't all that accessible, and sifting through google searches only goes so far. You're bound to miss something, most of the posts are introductory walk-throughs of questionable quality that don't provide any insight into the actual tool itself, linking to these tutorials is just regurgitating that. And we all have done that, we all have already spent countless hours finding these things for different tools to get an inkling of an idea of what they do.

Instead I propose having this sub be a list of those tools, with everyone contributing their collaborated knowledge there. What if all that was centralized? What if to get introduced to a tool, you could come here, find the master thread, and just read - tutorial gifs - use scenarios - whatever, then walk away and use it. That would be valuable. Wouldn't that be more valuable than finding a link to Vagrant's website, then "hmm what does this do now? And why would I care?"

2
androidgeekMOD•

I agree with you when you mention tools like Vim Sublime etc... however I'm also trying to keep an open mind that there may be a few new self starting developers out there who never heard of these 'obvious' tools. If a new dev learned about these tools on the subreddit...then that seems to be more meaningful than getting wrapped up in someone trying to receive link karma.

The circlejerk reference may be true at this very moment... The subreddit was created less than 2 days ago and it took off. It is expected people are going to get excited and share their favorite tools. Once we stop trending (which should be in a couple hours) I'm sure activity will slow and better content will rise.

And to be perfectly honest when I created the subreddit I had no concrete vision to what I wanted it to be. I thought 10-20 people would subscribe and I would learn about a couple new tools. But once it took off I kind of let the subscribers dictate how the subreddit would behave.

With implementation of tags and some moderation I think this subreddit could be a useful programming tool as well.

6
-blindOP•

I hear ya and sorry if I came across a bit strong, I didn't mean to. Don't get me wrong - your idea here is absolutely phenomenal and I really want it to succeed. It's such an elegant solution to this problem of an ever growing developer tool space and I've been looking for one for awhile because the google machine is just not up to snuff anymore.

I know its just the newness of the sub creating that wild-west effect of "don't you like this tool!" posts as it's just kind of finding it's way. It might not have come across as such in my post, but I was more of remarking on the popularity and visibility of posts about vim and stuff not that they were posted - we've all been there and they should definitely be included, but when something obvious like that completely dwarfs the visibility of other more specialized tools because aren't familiar with them and thus don't up vote. It was more of a criticism of what kind of things people up vote, not what is posted. Like if the vim post was then commented with a comment containing a gif of someone moving around a txt file 500x and macro'ing simple tasks to explain why it is so popular, that'd be way more valuable to learning than seeing "wow this is popular". All I was trying to get across

In my head I kind of have a pipedream vision of this subreddit being like a new outlet for people to teach tools to people, like instead of all the random blog posts out there like "How to set up Rails on a heroku server" on guyteachesrails.com - they could just post it here and teach other people what they themselves have researched and understood. The hours of searching for these scarce howto's of questionable quality with google, if people already familiar with these tools had a common place to answer questions about them and explain the functions - I know I'm not being really realistic here.

I think the Tags will help a lot - CaBz idea about the comment is the best solution alongside that imo, it was not something I had thought of when I posted this, maybe something like r/dataisbeautiful's posting guideline #3 about sourcing in a comment

[OC] posts must state the data source and tool(s) used in a comment. Only [OC] posts may link to image files.

I don't know man, that's just my thoughts. You're doing a great job and this place is already awesome, can't wait to see where it goes

2
Xplodeme•

I'm late to the party for this thread but I think you should take a look at r/metal. They maintain a blacklist of bands that you are not allowed to post about unless they release something new. The blacklist is in the sidebar all the time.

The word blacklist is a bit unfortunate but the sentiment is quite sober. These bands are so popular that the subreddit would be filled with these bands only if they were not blacklisted. The list also serves as recommendations for new metalheads to dig into.

I think a similar list in this subreddit would be quite an advantage. Both for old timers that might have missed something, and newcomers just getting into the field.

1
CaBz•

Personally, as a lazy dev, I like Quick link. Optionally, first comment should explain the link.

It's my opinion.

5
androidgeekMOD•

Speaking not just for the lazy devs but all devs in general, I think it's easier to quickly scan with link titles (and tags coming hopefuly tomorrow) than text posts. I think most people would agree with that. But if someone feels the need to create a text post to tell their story or give a more detailed description about the tool then that's great, go for it!

Also with the comment suggestion... I like that a lot. Already with some tools I found here, the comments have helped.

Lastly, as developers... we tend to be good researchers. Clicking on a link that catches our eye and a quick 10 second glance never seems to hurt.

5
CaBz•

I bookmarked around 20 links yesterday and today. All because the title inspired me and I followed the link and it seemed really nice. That was my opinion, but if some people needs more, then I guess it's cool!

2
[deleted]•

[deleted]

1
OrwellandWhisky•

I respect your opinion, CaBz, but must disagree on one point specifically: Your use of the word "optionally".

If there's no reason or explanation for a link, just "This tool is a thing!", then the community will quickly devolve into a million links to a million tools with no compelling reason to click on any one of them. "Photoshop, a photo editor." is uninformative and ignorable.

On another note, and to address OP's other point, perhaps we should specifically ban linking to the classic editors (VIM, Sublime, etc.) and anything that ships on most computers.

Just my $.02 :)

4
-blindOP•

Also being a lazy dev, having to dig around through a myriad of website links to find the purpose of a "quick link" would take more time than reading a description of why I should care about a thing that has been posted. That's my take on it.

The first comment system I could respect and get behind, anything the poster would provide a brief summary and use description within the context of the post is all I want.

2
tesselode•

I think if you're going to go this route, descriptions should be a comment. Self-posts may not be the way to go; direct links are pretty convenient. It wouldn't be a bad idea to make descriptive comments mandatory.

5
PasswordIsntHAMSTER•

I feel ya. Submissions should definitely include an exposition to the tool.

2
PasswordIsntHAMSTER•

Additionally - putting descriptions in self posts really helps with search indexing.

2
Muchoz•

Please make this a sticky. This should be read by everyone. I didn't subscribe to this subreddit only to be shown links to the website of Sublime Text or whatever popular software is out there atm. Even if I were new to this kind of stuff, I would still want to read the opinion of a user of that software, the op's opinion. And that opinion should be well written and be worth of giving an upvote too, not the simple link that is attached to the post like everyone is doing now simply for the karma. It doesn't bring anything to my feed either.

Edit: First post following this terminology is here: Browser Sync.

2
[deleted]•

[deleted]

1