Vitaly Sharovatov

Javascript developer -> teamlead -> mentor & dev 🥑

Tbilisi, Georgia Joined on Mar 1, 2021 https://git.io/teamlead

Work

dev 🥑 at Qase.io

javascript, management, processes, psychology

people management, software development processes, quality management

12 posts published

0 comments written

0 tags followed

Vitaly Sharovatov

Dec 22 '22

Designing a team that would produce software of good quality: overcome mental sets

9 min read

Vitaly Sharovatov

Dec 7 '22

Designing a team that would produce software of good quality: set up dogfooding

10 min read

Vitaly Sharovatov

Nov 2 '22

Designing a team that would produce software of good quality: get rid of individual performance reviews

8 min read

Vitaly Sharovatov

Oct 18 '22

Designing a team that would produce software of good quality: turnover effect

5 min read

Vitaly Sharovatov

Oct 11 '22

Designing a team that would produce software of good quality: emotions and interest

6 min read

Vitaly Sharovatov

Oct 3 '22

Designing a team that would produce software of good quality: management complexity

6 min read

Vitaly Sharovatov

Sep 26 '22

Designing a team that would produce software of good quality: team size

3 min read

Vitaly Sharovatov

Sep 19 '22

Designing a team that would produce software of good quality: knowledge overlap

4 min read

Vitaly Sharovatov

Sep 8 '22

Designing a team that would produce software of good quality: no time pressure

6 min read

Vitaly Sharovatov

Sep 1 '22

Designing a team that would produce software of good quality: team processess issues

7 min read

Vitaly Sharovatov

Aug 25 '22

Designing a team that would produce software of good quality: information loss problem

5 min read

Vitaly Sharovatov

Mar 29 '22

Happy developers are more productive: studies and advices

6 min read

DEV Community

Vitaly Sharovatov

Badges

Three Year Club

Writing Debut

Two Year Club

8 Week Writing Streak

4 Week Writing Streak

One Year Club

Skills/Languages

Available for

Designing a team that would produce software of good quality: overcome mental sets

Designing a team that would produce software of good quality: set up dogfooding

Designing a team that would produce software of good quality: get rid of individual performance reviews

Designing a team that would produce software of good quality: turnover effect

Designing a team that would produce software of good quality: emotions and interest

Designing a team that would produce software of good quality: management complexity

Designing a team that would produce software of good quality: team size

Designing a team that would produce software of good quality: knowledge overlap

Designing a team that would produce software of good quality: no time pressure

Designing a team that would produce software of good quality: team processess issues

Designing a team that would produce software of good quality: information loss problem

Happy developers are more productive: studies and advices