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
Go1.25からのGOMAXPROCS
kuro_kurorrr
1
800
Team topologies and the microservice architecture: a synergistic relationship
cer
PRO
0
1k
Azure AI Foundryではじめてのマルチエージェントワークフロー
seosoft
0
120
VS Code Update for GitHub Copilot
74th
1
300
WindowInsetsだってテストしたい
ryunen344
1
190
Gleamという選択肢
comamoca
6
760
FormFlow - Build Stunning Multistep Forms
yceruto
1
190
Webの外へ飛び出せ NativePHPが切り拓くPHPの未来
takuyakatsusa
2
320
AIエージェントはこう育てる - GitHub Copilot Agentとチームの共進化サイクル
koboriakira
0
330
C++20 射影変換
faithandbrave
0
520
ruby.wasmで多人数リアルタイム通信ゲームを作ろう
lnit
2
230
「Cursor/Devin全社導入の理想と現実」のその後
saitoryc
0
140
Featured
See All Featured
Raft: Consensus for Rubyists
vanstee
140
7k
Code Review Best Practice
trishagee
68
18k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
138
34k
Navigating Team Friction
lara
187
15k
Thoughts on Productivity
jonyablonski
69
4.7k
Building Flexible Design Systems
yeseniaperezcruz
328
39k
Git: the NoSQL Database
bkeepers
PRO
430
65k
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
15
1.5k
For a Future-Friendly Web
brad_frost
179
9.8k
Designing for Performance
lara
609
69k
What's in a price? How to price your products and services
michaelherold
246
12k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
700
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.