Pain of engineering management

Presented at Functional Scala 2023 (London, UK)

Transcript

1. Pain of engineering management
2. Roksolana Diachuk •Engineering manager at Captify •Women Who Code Kyiv Data Engineering Lead •Speaker
3. Transition (expectations)
4. Transition (reality)
5. Responsibilities People management Team/tech strategy Planning Engineering
6. Pain #1. Tech debt
7. Types of work 50% 50% Product Tech
8. State in the team 30% 70% Product Tech 15% 85% Product Tech
9. Dif f iculties Priority of tech debt Team capacity It’s boring!
10. Tech roadmap
11. Disaster case
12. DB migration Service 1 Service 2 Service 3
13. UI update Load to DBX New db in AWS Another db in AWS DB migration
14. Pain #2. Libraries migration
15. Scala chapter
16. From Pants to SBT
17. Dif f iculties Unexpected build behaviour Shared code in libraries Embedded libraries
18. What worked Scala chapter as space for discussions Teams capacity planning (roadmaps) Blocked tasks with the update
19. Pain #3. Scala versions
20. 2.12 Versioning nightmare 2.11 2.13
21. Dif f iculties Capacity planning Shared libraries between teams Different progress in the codebase
22. What worked Ongoing initiative in the roadmap Teams collaboration Constant review of the versions update
23. Pain #4. Pipelines evolution
24. Get deprecated and die Continue to live and rot Pipelines EOL
25. 40% pipelines deprecated Other 40% rewritten or planned to Pipelines EOL
26. Data evolution
27. Infrastructure evolution
28. What worked Careful planning Space for research Review of the business/tech needs
29. Pain #5. Onboarding newcomers
30. Full Stack to Scala engineer Scala book Scala course First tasks Success!
31. Dif f iculties Scala environment Diverse tech Different coding styles Lack of documentation
32. Full Stack to Scala engineer Scala book Scala course First small f ixes In progress Refactoring Metrics and alerts creation
33. Prevention mechanisms Unification of approaches Constant code base updates Extensive documentation Space for asking questions
34. Conclusions
35. Conclusions Team collaboration matters Engineering wide initiatives speed up changes Tech debt directly affects performance Documentation is the key
36. Thank you for attention!
37. dead_ fl owers22 roksolana-d roksolanadiachuk roksolanad My contact info Scala course
38. Stand with Ukraine