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
Sponsored
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Raka Westu Mogandhi
April 01, 2015
Programming
0
330
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
940
MVP Pattern for Android
rakawm
2
950
Other Decks in Programming
See All in Programming
The Past, Present, and Future of Enterprise Java
ivargrimstad
0
490
The Ralph Wiggum Loop: First Principles of Autonomous Development
sembayui
0
3.7k
Rで始めるML・LLM活用入門
wakamatsu_takumu
0
170
CSC307 Lecture 14
javiergs
PRO
0
470
AI駆動開発の本音 〜Claude Code並列開発で見えたエンジニアの新しい役割〜
hisuzuya
4
500
maplibre-gl-layers - 地図に移動体たくさん表示したい
kekyo
PRO
0
240
AWS×クラウドネイティブソフトウェア設計 / AWS x Cloud-Native Software Design
nrslib
15
3k
Fundamentals of Software Engineering In the Age of AI
therealdanvega
1
240
AWS Infrastructure as Code の新機能 2025 総まとめ 〜SA 4人による怒涛のデモ祭り〜
konokenj
10
3.3k
AIとペアプロして処理時間を97%削減した話 #pyconshizu
kashewnuts
1
220
AI活用のコスパを最大化する方法
ochtum
0
130
エージェント開発初心者の僕がエージェントを作った話と今後やりたいこと
thasu0123
0
240
Featured
See All Featured
Building a A Zero-Code AI SEO Workflow
portentint
PRO
0
380
brightonSEO & MeasureFest 2025 - Christian Goodrich - Winning strategies for Black Friday CRO & PPC
cargoodrich
3
120
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
52
5.9k
Getting science done with accelerated Python computing platforms
jacobtomlinson
2
140
The Mindset for Success: Future Career Progression
greggifford
PRO
0
270
What the history of the web can teach us about the future of AI
inesmontani
PRO
1
460
Building AI with AI
inesmontani
PRO
1
780
The Organizational Zoo: Understanding Human Behavior Agility Through Metaphoric Constructive Conversations (based on the works of Arthur Shelley, Ph.D)
kimpetersen
PRO
0
270
A designer walks into a library…
pauljervisheath
210
24k
How to Build an AI Search Optimization Roadmap - Criteria and Steps to Take #SEOIRL
aleyda
1
1.9k
Navigating the moral maze — ethical principles for Al-driven product design
skipperchong
2
280
GraphQLとの向き合い方2022年版
quramy
50
14k
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.