Slide 1

Slide 1 text

Pain of engineering management

Slide 2

Slide 2 text

Roksolana Diachuk •Engineering manager at Captify •Women Who Code Kyiv Data Engineering Lead •Speaker

Slide 3

Slide 3 text

Transition (expectations)

Slide 4

Slide 4 text

Transition (reality)

Slide 5

Slide 5 text

Responsibilities People management Team/tech strategy Planning Engineering

Slide 6

Slide 6 text

Pain #1. Tech debt

Slide 7

Slide 7 text

Types of work 50% 50% Product Tech

Slide 8

Slide 8 text

State in the team 30% 70% Product Tech 15% 85% Product Tech

Slide 9

Slide 9 text

Dif f iculties Priority of tech debt Team capacity It’s boring!

Slide 10

Slide 10 text

Tech roadmap

Slide 11

Slide 11 text

Disaster case

Slide 12

Slide 12 text

DB migration Service 1 Service 2 Service 3

Slide 13

Slide 13 text

UI update Load to DBX New db in AWS Another db in AWS DB migration

Slide 14

Slide 14 text

Pain #2. Libraries migration

Slide 15

Slide 15 text

Scala chapter

Slide 16

Slide 16 text

From Pants to SBT

Slide 17

Slide 17 text

Dif f iculties Unexpected build behaviour Shared code in libraries Embedded libraries

Slide 18

Slide 18 text

What worked Scala chapter as space for discussions Teams capacity planning (roadmaps) Blocked tasks with the update

Slide 19

Slide 19 text

Pain #3. Scala versions

Slide 20

Slide 20 text

2.12 Versioning nightmare 2.11 2.13

Slide 21

Slide 21 text

Dif f iculties Capacity planning Shared libraries between teams Different progress in the codebase

Slide 22

Slide 22 text

What worked Ongoing initiative in the roadmap Teams collaboration Constant review of the versions update

Slide 23

Slide 23 text

Pain #4. Pipelines evolution

Slide 24

Slide 24 text

Get deprecated and die Continue to live and rot Pipelines EOL

Slide 25

Slide 25 text

40% pipelines deprecated Other 40% rewritten or planned to Pipelines EOL

Slide 26

Slide 26 text

Data evolution

Slide 27

Slide 27 text

Infrastructure evolution

Slide 28

Slide 28 text

What worked Careful planning Space for research Review of the business/tech needs

Slide 29

Slide 29 text

Pain #5. Onboarding newcomers

Slide 30

Slide 30 text

Full Stack to Scala engineer Scala book Scala course First tasks Success!

Slide 31

Slide 31 text

Dif f iculties Scala environment Diverse tech Different coding styles Lack of documentation

Slide 32

Slide 32 text

Full Stack to Scala engineer Scala book Scala course First small f ixes In progress Refactoring Metrics and alerts creation

Slide 33

Slide 33 text

Prevention mechanisms Unification of approaches Constant code base updates Extensive documentation Space for asking questions

Slide 34

Slide 34 text

Conclusions

Slide 35

Slide 35 text

Conclusions Team collaboration matters Engineering wide initiatives speed up changes Tech debt directly affects performance Documentation is the key

Slide 36

Slide 36 text

Thank you for attention!

Slide 37

Slide 37 text

dead_ fl owers22 roksolana-d roksolanadiachuk roksolanad My contact info Scala course

Slide 38

Slide 38 text

Stand with Ukraine