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
66
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
60
Alice and the return to the world of pods and higher-order functions
roksolanad
0
150
Modern data pipelines in AdTech - life in the trenches
roksolanad
1
260
Alice and travelling back in time
roksolanad
0
130
Big Data at AdTech
roksolanad
0
270
Alice and the Mad Hatter: Predict or not to predict
roksolanad
0
130
Alice in the world of machine learning
roksolanad
0
87
Alice and the lost pod: practical guide to Kubernetes in Scala
roksolanad
1
290
Scala meets Kubernetes
roksolanad
0
450
Other Decks in Technology
See All in Technology
Commitment vs Harrisonism - Keynote for Scrum Niseko 2024
miholovesq
6
1.1k
Oracle Cloud Infrastructureデータベース・クラウド:各バージョンのサポート期間
oracle4engineer
PRO
27
12k
オーティファイ会社紹介資料 / Autify Company Deck
autifyhq
9
120k
GitHub Universe: Evaluating RAG apps in GitHub Actions
pamelafox
0
180
話題のGraphRAG、その可能性と課題を理解する
hide212131
4
1.5k
Datachain会社紹介資料(2024年11月) / Company Deck
datachain
3
16k
生成AIの強みと弱みを理解して、生成AIがもたらすパワーをプロダクトの価値へ繋げるために実践したこと / advance-ai-generating
cyberagentdevelopers
PRO
1
180
グローバル展開を見据えたサービスにおける機械翻訳プラクティス / dp-ai-translating
cyberagentdevelopers
PRO
1
150
30万人が利用するチャットをFirebase Realtime DatabaseからActionCableへ移行する方法
ryosk7
5
350
[AWS JAPAN 生成AIハッカソン] Dialog の紹介
yoshimi0227
0
150
とあるユーザー企業におけるリスクベースで考えるセキュリティ業務のお話し
4su_para
3
330
顧客が本当に必要だったもの - パフォーマンス改善編 / Make what is needed
soudai
24
6.8k
Featured
See All Featured
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
92
16k
How to Think Like a Performance Engineer
csswizardry
19
1.1k
Code Reviewing Like a Champion
maltzj
519
39k
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
250
21k
Embracing the Ebb and Flow
colly
84
4.4k
Become a Pro
speakerdeck
PRO
24
5k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
355
29k
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.2k
Learning to Love Humans: Emotional Interface Design
aarron
272
40k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
167
49k
KATA
mclloyd
29
13k
Designing for Performance
lara
604
68k
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