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
Cloudflare AgentsとAI SDKでAIエージェントを作ってみた
briete
0
140
Goで実践するドメイン駆動開発 AIと歩み始めた新規プロダクト開発の現在地
imkaoru
4
800
Swift Concurrency - 状態監視の罠
objectiveaudio
2
510
育てるアーキテクチャ:戦い抜くPythonマイクロサービスの設計と進化戦略
fujidomoe
1
170
Things You Thought You Didn’t Need To Care About That Have a Big Impact On Your Job
hollycummins
0
210
Railsだからできる 例外業務に禍根を残さない 設定設計パターン
ei_ei_eiichi
0
440
Catch Up: Go Style Guide Update
andpad
0
210
overlayPreferenceValue で実現する ピュア SwiftUI な AdMob ネイティブ広告
uhucream
0
180
Server Side Kotlin Meetup vol.16: 内部動作を理解して ハイパフォーマンスなサーバサイド Kotlin アプリケーションを書こう
ternbusty
1
120
理論と実務のギャップを超える
eycjur
0
120
CSC305 Lecture 06
javiergs
PRO
0
210
Signals & Resource API in Angular: 3 Effective Rules for Your Architecture @BASTA 2025 in Mainz
manfredsteyer
PRO
0
110
Featured
See All Featured
Git: the NoSQL Database
bkeepers
PRO
431
66k
Raft: Consensus for Rubyists
vanstee
139
7.1k
Build your cross-platform service in a week with App Engine
jlugia
232
18k
Faster Mobile Websites
deanohume
310
31k
RailsConf 2023
tenderlove
30
1.2k
Unsuck your backbone
ammeep
671
58k
Designing Experiences People Love
moore
142
24k
Bash Introduction
62gerente
615
210k
Context Engineering - Making Every Token Count
addyosmani
5
220
Making Projects Easy
brettharned
119
6.4k
Fashionably flexible responsive web design (full day workshop)
malarkey
407
66k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
46
7.7k
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.