Slide DevCoach

DevCoach 141 : Back-End | Membangun Software dengan Prinsip Clean Code dan Design Pattern.

Transcript

2. Agenda • Memahami pentingnya kode yang bersih • Clean Code dengan implementasi di JavaScript • Mengenal Design Pattern Back-End
3. Back-End Kenapa sih kita perlu menuliskan kode yang bersih?
4. Back-End “Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” - Martin Fowler
5. Back-End
6. Back-End WTH WTH WTH WTH WTH WTH WTH WTH WTH
7. Clean Code Back-End
8. What is Clean Code? Clean code is simple and direct. Clean code reads like well-written prose. Clean code never obscures the designer’s intent but rather is full of crisp abstractions and straightforward lines of control. Back-End
9. Meaningful Names Back-End
10. Back-End
11. Use Intention-Revealing Names Back-End const d = "01-03-2024" const date = "01-03-2024" Bad ❌ Good ✅
12. Use Pronounceable Names Back-End const ttl = 2000 const total = 2000 Bad ❌ Good ✅
13. Use Searchable Names Back-End checkFile("/home/js/"); const filePath = "/home/js/"; checkFile(filePath); Bad ❌ Good ✅
14. Avoid Mental Mapping Back-End Bad ❌ Good ✅
15. Class and Method Names Back-End • Nama class menggunakan kata benda • Nama method menggunakan kata kerja let customer; let account; addCustomer() deleteAccount()
16. Functions Back-End
17. Small! Back-End “The first rule of functions is that they should be small. The second rule of functions is that they should be smaller than that”. - Robert C. Martin Functions panjangnya 20-30 baris.
18. Do One Thing Back-End Bad ❌ Good ✅
19. Function Arguments Back-End Bad ❌ Good ✅
20. Formatting Back-End
21. Vertical Formatting Back-End Bad ❌ Good ✅
22. Horizontal Formatting Back-End Bad ❌ Good ✅
23. More detail Clean Code Book GitHub Repository https://github.com/ryanmcder mott/clean-code-javascript Back-End
24. Design Pattern Back-End
25. What is Design Pattern? Design Pattern adalah sebuah solusi umum yang telah teruji dan bisa digunakan kembali untuk menyelesaikan suatu masalah yang sering terjadi pada perancangan perangkat lunak [8]. Back-End
26. Why Design Pattern? • Improves kualitas kode • Meningkatkan maintainability • Memfasilitasi komunikasi dan kolaborasi antar anggota tim Back-End
27. Jenis Design Pattern • Creational Pattern : Berhubungan dengan penciptaan suatu objek (instantiation). • Structural Pattern : Berhubungan dengan komposisi suatu objek (relationships). • Behavioral Pattern : Berhubungan dengan komunikasi antar objek (communications). Back-End
28. Creational Pattern • Factory Method • Abstract Factory • Builder • Prototype • Singleton Back-End
29. Structural Pattern • Adapter • Bridge • Composite • Decorator • Facade • Flyweight • Proxy Back-End
30. Behavioral Pattern • Template method • Observer • Mediator • Iterator • more Back-End
31. More detail at .. https://refactoring.guru/design-patterns Back-End
32. Thank You arasopraza aras@dicoding.com arasopraza Back-End arsyopraza
33. Feedback! Hadiah: • 2 Token Langganan Academy (30 Hari) *untuk pengisi feedback terpilih! dicoding.id/devcoachfeedback
35. Back-End Demo Redis https://github.com/arasopraza/Demo-Developer-Coaching-129.git