Build Sustainable Digital Product as Software Developer

An explanation some tips how to build sustainable digital product as software developer

Transcript

1. Build Sustainable Digital Product as Software Developer #Ngalamtalks07 28 June 2021
2. Please Remember 5M 1. Mencuci Tangan 2. Menjaga Jarak 3. Memakai Masker 4. Menjauhi Kerumunan 5. Mengurangi Mobilitas
3. About Me • Didik Tri Susanto • Informatic Engineering, UIN Maulana Malik Ibrahim Malang • Software Developer, Tech Lead at Avana • Twitter: @didikz • Linkedin: Didik Tri Susanto • Blog: medium.com/teknomuslim • Github: @didikz
4. Ability to be developed, ability to be always operational (reliable), so it can give impact / benefit to user and gaining profit for business owner
5. Why is so important? 1. Software as main platform / Digital Company 2. Tech is changing and always evolving 3. Business Competition 4. Building software is hard
6. Choosing Tech Stack 1. Suitable for your project 2. Have great support / community 3. Comfortable for you & your team 4. On budget
7. Do not over complicate, remember you can iterate later
8. How about infra & architecture? Cloud or Serverless or Simple Hosting Provider Monolith vs Microservices
9. Coding, coding, coding ...
10. Plan first, Code later
11. Technical Debt
12. Technical Debt happens when... 1. No proper plan 2. Unreasonable Deadline -> Cutting Corner 3. Inexperience of building software 4. Business Requirement Changes
14. Dealing with Technical Debt 1. Talk to stakeholder / Product owner 2. Document it and set prioritize 3. Make proper plan to refactor or write code 4. Automate your test 5. Code Review regularly
15. Once Time in Your Life
16. Write Test Now!
17. CI / CD Integration: Know when it’s Failed
18. Benefit of Test Automation 1. Stability 2. Faster Release 3. Higher Productivity 4. Scalable Code 5. Confidence to Refactor
19. Once it’s live, you can’t avoid maintenance & monitoring
20. Error Monitoring
21. Site Health Check
22. Others... • Issue tracker • Cloud monitoring tools / Health check • Grafana, Kibana
23. Safe Deployment
24. Talking About Performance... • Database Optimization ◦ Careful about your query statement & Index your important column ◦ Separate read & write DB • Network I/O ◦ Careful about calling 3rd party APIs • Server resources ◦ Use auto scaling mechanism • Better Error Handling • Cloudflare & CDN Services
25. Performance Metrics • Reduce API Response Time • 99% uptime • Good Result Google Page Insight • Fast page load • Clear Error Response • Ability to handling xx RPS (depends on product requirement) • Etc...
26. WRITE DOCUMENTATION!
27. 1. Test Case / Test Scenario 2. Product Requirement Document 3. APIs Documentation 4. Technical Documentation
28. The time has come, we need to migrate using new stack! Cool!
29. • Ask yourself, do you really need it? • Plan Properly, calculate every aspect (cost, BC possibility, stack limitation, time) • Make sure all documentation & team ready • Migrate partially instead of big bang migration • You may ended up maintaining 2 different versions
30. Final Words • Bear in mind, software is always changing • Define your Engineering KPI / Goals / Metrics • Enhance your engineering culture / development workflow • Listen to your user • Growth your engineering team’s skills