1.
Avoiding Technical Debt
Ikatan Alumni TOKI Gathering @ TOKI Camp 2017

2.
Problems
Phase as a startup..
❏ Product market fit, as soon as possible
❏ With limited budget
❏ Build fast, break fast
❏ As some metrics grow
❏ More backlogs
❏ More budget
❏ Growing team

3.
Cost of Technical Debt
❏ Fix one bug, and two more pop up
❏ Really hard to understand code and modify it
❏ Waste time to explain the code
❏ New features, here comes old feature bugs
❏ Human cost

4.
Code Assets Standardization
❏ Code styling
❏ Naming convention
❏ Commit message
❏ Unit testing
❏ Code review
❏ Refactor

5.
Code Styling
Mostly handled by linter

6.
Naming Conventions
❏ Filename: TitleCase, kebab-case, etc
❏ Class name: Noun
❏ Function name: Verb, camelCase
❏ Git branching name:
❏ add/new-feature
❏ update/existing-feature
❏ fix/bugs
❏ try/new-things

7.
Unit test
❏ Happy case + exception case
❏ First step of bug fixing

8.
Code Review
❏ Ensuring the code is understandable and maintainable
❏ Minimum one reviewer for each pull request
❏ 60 minutes timeboxing
❏ Everyone input is valid
❏ Share code ownership

9.
Refactor
❏ Keep improving code quality
❏ Tools: design pattern, unit test
❏ Reference: Clean Code: A Handbook of Agile Software Craftsmanship by
Robert C Martin

10.
Thank you.