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
Frustration Forbidden Burnout
Search
Nikita Galkin
November 17, 2018
Programming
0
77
Frustration Forbidden Burnout
Nikita Galkin
November 17, 2018
Tweet
Share
More Decks by Nikita Galkin
See All by Nikita Galkin
React applications Failures
galkin
0
310
Node.js Development in 2022
galkin
0
840
Cloud Native Approach for Node.js Developers
galkin
0
96
Deep Dive Into NestJS at FWDays
galkin
0
520
Node.js Recipes: Road to Production.
galkin
0
200
Auth for React.js App
galkin
1
160
Web Developer Toolbox at 2020
galkin
1
240
Node.js Development in 2020: trends and techniques
galkin
0
560
Backend For Frontend: The Missing Manual at Devoxx Ukraine
galkin
1
170
Other Decks in Programming
See All in Programming
Claude Codeの「Compacting Conversation」を体感50%減! CLAUDE.md + 8 Skills で挑むコンテキスト管理術
kmurahama
1
710
Giselleで作るAI QAアシスタント 〜 Pull Requestレビューに継続的QAを
codenote
0
330
Flutter On-device AI로 완성하는 오프라인 앱, 박제창 @DevFest INCHEON 2025
itsmedreamwalker
1
180
メルカリのリーダビリティチームが取り組む、AI時代のスケーラブルな品質文化
cloverrose
2
450
リリース時」テストから「デイリー実行」へ!開発マネージャが取り組んだ、レガシー自動テストのモダン化戦略
goataka
0
160
Developing static sites with Ruby
okuramasafumi
1
340
QAフローを最適化し、品質水準を満たしながらリリースまでの期間を最短化する #RSGT2026
shibayu36
0
1.5k
ゲームの物理 剛体編
fadis
0
390
Context is King? 〜Verifiability時代とコンテキスト設計 / Beyond "Context is King"
rkaga
10
1.5k
AI Agent Tool のためのバックエンドアーキテクチャを考える #encraft
izumin5210
6
1.5k
AIエージェントの設計で注意するべきポイント6選
har1101
6
2.9k
まだ間に合う!Claude Code元年をふりかえる
nogu66
5
930
Featured
See All Featured
Docker and Python
trallard
47
3.7k
Fireside Chat
paigeccino
41
3.8k
How STYLIGHT went responsive
nonsquared
100
6k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
666
130k
A Guide to Academic Writing Using Generative AI - A Workshop
ks91
PRO
0
170
Keith and Marios Guide to Fast Websites
keithpitt
413
23k
How to Get Subject Matter Experts Bought In and Actively Contributing to SEO & PR Initiatives.
livdayseo
0
41
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
38
2.7k
What’s in a name? Adding method to the madness
productmarketing
PRO
24
3.9k
The Illustrated Children's Guide to Kubernetes
chrisshort
51
51k
Darren the Foodie - Storyboard
khoart
PRO
1
2.1k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
132
19k
Transcript
None
Expectations Reality VS
None
• Autonomy • Competence • Teamwork • Predictability • Money
• Bureaucracy • Non Maintainability • Toxic team • Waste
of time • Salary delays
• Autonomy • Competence • Teamwork • Predictability • Money
• Bureaucracy • Non Maintainability • Toxic team • Waste of time • Salary delays
frustration
Sync expectations
1. Ask questions
None
2. Iterate each other
None
3. Have process and follow them
The process has a focus and steps. Steps following guarantees
the result.
4. Improve processes together
Process Evolution is a everyday work
5. Make follow up notes after meetings
1. Ask questions 2. Iterate each other 3. Have processes
and follow them 4. Improve processes together 5. Make follow up notes after meetings
Make follow up notes after meetings COMMUNICATE AND WRITE
Frustration Forbidden! Burnout! You can find me on Twitter as
@galk_in Slides are available at speakerdeck.com/galkin or at my site galk.in