The document discusses avoiding technical debt when building products as a startup. It notes that startups focus on quickly achieving product-market fit with limited budgets, which can lead to technical debt as products and teams grow. Technical debt increases bugs, makes code hard to understand and modify, and wastes time. The document recommends standardizing code through styling, naming conventions, commit messages, unit testing, code reviews, and refactoring to help manage technical debt. It provides examples for each area and emphasizes code quality to ensure understandability and maintainability as a product and team scales.

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

3. 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

5. 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

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

7. Code Styling
Mostly handled by linter

8. 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

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

10. 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

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

15. Thank you.