A Documentation Talk 4.07 http://spkr8.com/t/8258

Description:

"A Documentation Talk" sounds pretty boring, right? Wouldn't it be scandalously titillating if this talk's title included detailed analysis of the expectations and results of the talk itself? Jeez it's like someone's making an overt metaphor for how Rubyists document their code.

At GitHub, we add docs to every single method we write, and we couldn't be more excited about it. It means faster and simpler code. It means stronger tests. It means your developers can pay attention to new commits without stressing about them. Documentation will make your project so very happy.

Comments on this Talk

Avatar-missing-icon-08 delbert, 03 Sep 04:17 PM

Great way to finish up the conference. I was going to leave early, but this was definitely worth staying for.

Stream.12748 Jeff Casimir, 08 Sep 01:07 AM

Solid talk. I would love to see more details on the structure of a great readme. Maybe an example broken down as to "why it works."

Have an account? Sign in or register.

Leave a Comment

5 Ratings: 4.07

Delivery: 4.08

Content: 4.06

Leave a Rating:
Sign in or register.

Last Five Ratings

Time & Location

September 2, 2011 — 03:30 PM
Boulder, CO (Map It)

Event

Rocky Mountain Ruby (23 talks)

August 31 - September 2, 2011

Other talks at this event