1.
0.
A little background

2.
1.
The story begins

3.
2.
New technology
stack

4.
3.
New team member

5.
4.
Second teammate
or “Why so
complex?”

6.
5. First troubles
✗ Team is confused by non-understanding
what’s going on
✗ I increase time spending on PR reviews to
adjust that code
✗ Team is confused even more, a lot of conflicts
appear
✗ I continue to push believing you all will be
thankful eventually
7

7.
8

8.
Common arguments
Their:
✗ This looks complex
My:
✗ You just didn’t get
into it
✗ We have complex
application
✗ This will help us in
future
✗ Ruby ecosystem is
not quiet ready
9

9.
Common arguments
Their:
✗ You’re wrong
My:
✗ You can’t know, you
don’t know what I
know
✗ I take responsibility
over the project
✗ What is your
alternative?
10

10.
Common arguments
Their:
✗ Are you the smartest
one? One against all?
My:
✗ There are a lot of
proofs that crowd
might be wrong
✗ What do you know
that I don’t know?
11

11.
Common arguments
Their:
✗ Do you try to realize
your ambitions?
My:
✗ No, I think exclusively
about the project
✗ I believe, this is helpful
for the project
12

12.
6.
From the best to
the worst

13.
Consequences
✗ We spend too much time on discussions on
different approaches
✗ In new application we started to have legacy
code
✗ Members of other teams afraid to be shifted to
us
✗ I was the only one who knows the vision of
project
14

14.
It was so over a
year...

15.
...until I started
to become
disappointed

16.
I started to suspect smthing...
✗ Profit is much less than pain
✗ Situation doesn’t get better
✗ They have simple Rails on DDD workshop
✗ The last straw was convo with Solnic
✗ If I could live this again, I won’t do this again
✗ I hate to be wrong
17

17.
18

18.
19
Thanks!
Any questions?
You can find me at:
✗ @sergey_kukunin
✗ sergey.kukunin@gmail.com

19.
20
Attempt to
rationalize

20.
Architecture was
ready for future
that hasn’t came

21.
Clean code is
controversial
Be aware of
overhead!

22.
Complete a
feature, then
think about
quality

23.
Perfectionism is
an optimization

24.
Egg or chicken?
Team or
project?

25.
I protected the
code, not the
team

26.
Ownership over a
project

27.
Trust is a base.
Deal with it

28.
There is a burden
of mistakes

29.
I really realized
my ambitions

30.
Your brain is your
enemy. Don’t
trust him

31.
32
Thanks!
Any questions?
You can find me at:
✗ @sergey_kukunin
✗ sergey.kukunin@gmail.com