Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Code Documentation
Search
Raka Westu Mogandhi
April 01, 2015
Programming
0
320
Code Documentation
Code documentation for team collaborating.
Raka Westu Mogandhi
April 01, 2015
Tweet
Share
More Decks by Raka Westu Mogandhi
See All by Raka Westu Mogandhi
Cross Platform Development using Xamarin Forms
rakawm
0
3.2k
Android Material Design
rakawm
0
930
MVP Pattern for Android
rakawm
2
940
Other Decks in Programming
See All in Programming
MCPで実現するAIエージェント駆動のNext.jsアプリデバッグ手法
nyatinte
7
1.1k
AIと私たちの学習の変化を考える - Claude Codeの学習モードを例に
azukiazusa1
8
3.5k
デザイナーが Androidエンジニアに 挑戦してみた
874wokiite
0
280
OSS開発者という働き方
andpad
5
1.7k
複雑なドメインに挑む.pdf
yukisakai1225
5
1.1k
時間軸から考えるTerraformを使う理由と留意点
fufuhu
15
4.6k
Azure SRE Agentで運用は楽になるのか?
kkamegawa
0
2k
Compose Multiplatform × AI で作る、次世代アプリ開発支援ツールの設計と実装
thagikura
0
140
@Environment(\.keyPath)那么好我不允许你们不知道! / atEnvironment keyPath is so good and you should know it!
lovee
0
110
ProxyによるWindow間RPC機構の構築
syumai
3
1.1k
Go言語での実装を通して学ぶLLMファインチューニングの仕組み / fukuokago22-llm-peft
monochromegane
0
120
Design Foundational Data Engineering Observability
sucitw
3
190
Featured
See All Featured
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
44
2.5k
GraphQLの誤解/rethinking-graphql
sonatard
72
11k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
33
2.4k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
139
34k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
131
19k
Thoughts on Productivity
jonyablonski
70
4.8k
Balancing Empowerment & Direction
lara
3
620
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
32
1.5k
Context Engineering - Making Every Token Count
addyosmani
1
31
Become a Pro
speakerdeck
PRO
29
5.5k
KATA
mclloyd
32
14k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
30
9.6k
Transcript
CODE DOCUMENTATION Raka Westu Mogandhi BrownBag Onebit April 1st 2014
What is code documentation? Written text besides the code that
explain how the code works.
Why? • Code is hard to read and maintained. •
Peoples need to know how to use that code. • Less time to learn and continuing the project.
What is the purpose? To make developers read their codes
much easier
Good Documentation should: • Be easy to understand. • Provide
valid and working examples. • Provide reference in all classes, method and variables.
How to write code documentation? • Write the explanation of
how your code works. • Write the example if necessary.
Examples. • Java (using javadoc) more at http://www.oracle.com/technetwork/articles/java/index-137868.html – Class
/** * Represents wobe product. * @author rakawm * @version 0.0.6 */ public class Product { – Method /** * Return formatted string of DateTime object in UTC timezone. * Format: dd-MM-yyyy HH:mm or dd-MM-yyyy HH:mm:ss. * @param dateTime DateTime object. * @return formatted string of time. */ public static String toServerUTC(DateTime dateTime) {
Examples (Continued) • PHP /** * Summary. * * Description.
* * @since x.x.x * @access (for functions: only use if private) * * @see Function/method/class relied on * @link URL * @global type $varname Description. * @global type $varname Description. * * @param type $var Description. * @param type $var Optional. Description. * @return type Description. */
Examples (Continued) • PHP /** * Summary. * * Description.
* * @since x.x.x * @access (for functions: only use if private) * * @see Function/method/class relied on * @link URL * @global type $varname Description. * @global type $varname Description. * * @param type $var Description. * @param type $var Optional. Description. * @return type Description. */
Recap • Documentation is important for all team members, especially
engineer. • Need to be documented: – All function, classes and variables.