The document outlines the author's experiences with implementing a new technology stack and a team transition, highlighting challenges such as team confusion, conflicts, and legacy code issues. It reflects on the complexities of project management, emphasizing the tension between ambition and project needs, and the importance of trust within a team. Ultimately, the author expresses disappointment with the outcome and stresses the lessons learned from the experience.

2. 0.
A little background

3. 1.
The story begins

4. 2.
New technology
stack

5. 3.
New team member

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

7. 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

8. 8

9. 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

10. 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

11. 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

12. 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

13. 6.
From the best to
the worst

14. 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

15. It was so over a
year...

16. ...until I started
to become
disappointed

17. 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

18. 18

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

20. 20
Attempt to
rationalize

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

22. Clean code is
controversial
Be aware of
overhead!

23. Complete a
feature, then
think about
quality

24. Perfectionism is
an optimization

25. Egg or chicken?
Team or
project?

26. I protected the
code, not the
team

27. Ownership over a
project

28. Trust is a base.
Deal with it

29. There is a burden
of mistakes

30. I really realized
my ambitions

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

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