Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Pain of engineering management
Search
Roksolana
December 01, 2023
Technology
1
74
Pain of engineering management
Presented at Functional Scala 2023 (London, UK)
Roksolana
December 01, 2023
Tweet
Share
More Decks by Roksolana
See All by Roksolana
Productionizing Big Data - stories from the trenches
roksolanad
0
68
Alice and the return to the world of pods and higher-order functions
roksolanad
0
180
Modern data pipelines in AdTech - life in the trenches
roksolanad
1
290
Alice and travelling back in time
roksolanad
0
170
Big Data at AdTech
roksolanad
0
340
Alice and the Mad Hatter: Predict or not to predict
roksolanad
0
190
Alice in the world of machine learning
roksolanad
0
120
Alice and the lost pod: practical guide to Kubernetes in Scala
roksolanad
1
330
Scala meets Kubernetes
roksolanad
0
500
Other Decks in Technology
See All in Technology
KubeCon + CloudNativeCon Japan 2025 Recap
donkomura
0
170
20250807_Kiroと私の反省会
riz3f7
0
180
リリース2ヶ月で収益化した話
kent_code3
1
200
Mambaで物体検出 完全に理解した
shirarei24
2
220
AIに目を奪われすぎて、周りの困っている人間が見えなくなっていませんか?
cap120
1
440
【CEDEC2025】『Shadowverse: Worlds Beyond』二度目のDCG開発でゲームをリデザインする~遊びやすさと競技性の両立~
cygames
PRO
1
300
【CEDEC2025】『ウマ娘 プリティーダービー』における映像制作のさらなる高品質化へ!~ 豊富な素材出力と制作フローの改善を実現するツールについて~
cygames
PRO
0
230
解消したはずが…技術と人間のエラーが交錯する恐怖体験
lamaglama39
0
190
【CEDEC2025】現場を理解して実現!ゲーム開発を効率化するWebサービスの開発と、利用促進のための継続的な改善
cygames
PRO
0
730
相互運用可能な学修歴クレデンシャルに向けた標準技術と国際動向
fujie
0
210
みんなのSRE 〜チーム全員でのSRE活動にするための4つの取り組み〜
kakehashi
PRO
2
140
Amazon Bedrock AgentCoreのフロントエンドを探す旅 (Next.js編)
kmiya84377
1
120
Featured
See All Featured
How GitHub (no longer) Works
holman
314
140k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
10
1k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
251
21k
Connecting the Dots Between Site Speed, User Experience & Your Business [WebExpo 2025]
tammyeverts
8
430
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
47
9.6k
Building Flexible Design Systems
yeseniaperezcruz
328
39k
Making the Leap to Tech Lead
cromwellryan
134
9.5k
Optimising Largest Contentful Paint
csswizardry
37
3.4k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
130
19k
A better future with KSS
kneath
238
17k
Exploring the Power of Turbo Streams & Action Cable | RailsConf2023
kevinliebholz
34
6k
Raft: Consensus for Rubyists
vanstee
140
7.1k
Transcript
Pain of engineering management
Roksolana Diachuk •Engineering manager at Captify •Women Who Code Kyiv
Data Engineering Lead •Speaker
Transition (expectations)
Transition (reality)
Responsibilities People management Team/tech strategy Planning Engineering
Pain #1. Tech debt
Types of work 50% 50% Product Tech
State in the team 30% 70% Product Tech 15% 85%
Product Tech
Dif f iculties Priority of tech debt Team capacity It’s
boring!
Tech roadmap
Disaster case
DB migration Service 1 Service 2 Service 3
UI update Load to DBX New db in AWS Another
db in AWS DB migration
Pain #2. Libraries migration
Scala chapter
From Pants to SBT
Dif f iculties Unexpected build behaviour Shared code in libraries
Embedded libraries
What worked Scala chapter as space for discussions Teams capacity
planning (roadmaps) Blocked tasks with the update
Pain #3. Scala versions
2.12 Versioning nightmare 2.11 2.13
Dif f iculties Capacity planning Shared libraries between teams Different
progress in the codebase
What worked Ongoing initiative in the roadmap Teams collaboration Constant
review of the versions update
Pain #4. Pipelines evolution
Get deprecated and die Continue to live and rot Pipelines
EOL
40% pipelines deprecated Other 40% rewritten or planned to Pipelines
EOL
Data evolution
Infrastructure evolution
What worked Careful planning Space for research Review of the
business/tech needs
Pain #5. Onboarding newcomers
Full Stack to Scala engineer Scala book Scala course First
tasks Success!
Dif f iculties Scala environment Diverse tech Different coding styles
Lack of documentation
Full Stack to Scala engineer Scala book Scala course First
small f ixes In progress Refactoring Metrics and alerts creation
Prevention mechanisms Unification of approaches Constant code base updates Extensive
documentation Space for asking questions
Conclusions
Conclusions Team collaboration matters Engineering wide initiatives speed up changes
Tech debt directly affects performance Documentation is the key
Thank you for attention!
dead_ fl owers22 roksolana-d roksolanadiachuk roksolanad My contact info Scala
course
Stand with Ukraine