[AlexMuir]

No idea how this is getting so many points. There's absolutely nothing of any practical interest here. Use version control and documentation... End of post. I'd say these are more industry standard practices than leading edge.

[joshdotsmith]

There will always be a new freshman class. Every year, someone joins HN (or the community at large) knowing next to nothing. We should welcome those people, not make them feel bad for being new.

[noblethrasher]

Yep. HN wants to avoid eternal Septembers; occasional Septembers are fine though.

[Isamu]

>No idea how this is getting so many points.

Because the basics have to be pointed out again ... and again.

I think the upvotes don't primarily mean "omg I never thought to do this" but rather "will someone please staple this to the foreheads of all the clueless devs I've had to clean up after."

[pietro]

> I'd say these are more industry standard practices than leading edge.

Yeah, that's sort of what "best practices" are all about. They are for teaching outsiders what insiders have learned through practice. The intended audience is everyone who doesn't already know this.

If you consider the article of no practical interest for a seasoned insider, that's about the highest praise you can give.

[opendais]

I upvoted it on the odd hope that one of my coworkers sees it and actually considers following some of it. ;)

[btrombley]

It's best practices, not new practices, and a very clear concise write up at that. I wish if read this 6 months ago, rather than learning it the hard way.

[romanovcode]

>First of all, use git for version control. It is modern, works great and the majority of developers are either comfortable in using it or want to start using it.

Not to mention those points were mainly subjective. Don't get me wrong, I like and use Git myself but statements like "Use this, most people use it so you must use it too!" are just horrible.

[euphemize]

True, although you'd be surprised to see how many people fail to provide proper docs, or use git for source control, still in 2014. I agree with others in here, maybe the title is just misleading more than anything else.

[gnaritas]

Failing to use git as your source control mechanism is not an actual problem; failing to use any source control is a problem, you don't have to use git.

[ricardolopes]

I have to agree. Interesting topic, but not a lot of new content there.