Just Say No To :nodoc: and Document Your Code! by Loren Segal
3,727 views · Published 13 December 2011 · 38:28 · Indexed 25 September 2026
Channel: Confreaks · 2011 · Science & Technology
Nobody said it was going to be easy, but documentation is an important part of making your libraries and tools usable by others. Without good documentation, your users will have a hard time adopting your code. But what is "good documentation", anyway? This talk will outline what is important to communicate in our documentation, how we should write it, and what makes documentation "good". We will look at some common pitfalls we come across when documenting libraries and frameworks, and how we can use tools like YARD to make it easier to document code. We will see how writing documentation should really not be an afterthought, but an important part of the entire coding process, and how it can be used to validate the design of your library or framework as you write it. Ultimately, this talk will show you how documentation can inform your development process and lead to stable working APIs from the get-go rather than simply leaving your documentation to the end.
More from this channel
-
34:59
MongoMapper, Mixins, and Migrations - a look at managing data-model complexity by Tim Connor
-
44:16
Go for the Rubyist: Appropriation of Great Ideas in Ruby by Dave Grijalva
-
1:13:32
Lightning Talks with Aaron Patterson and Various Presenters
-
27:22
LA Ruby Conf 2012 Maintainable Ruby on Rails by Steven Baker
-
37:02
Large scale Ruby project, challenges and Pitfalls. by Karunakar
-
28:29
Active Record Scopes and Arel by Jacob Swanner
-
10:19
Your Face in 10 minutes... with Macruby! by Haris Amin,
-
32:59
Test-driving GUIs (with RubyCocoa) by Brian Marick