20 Patterns to Watch for in Your Engineering Team

by GitPrime Press

52 pages, ebook

Published January 1, 2019

Reviews

[Arturo Herrero · Rating 4 out of 5]

20 Patterns to Watch for in Your Engineering Team

[Deepika Ghodki · Rating 2 out of 5]

This is more like an article about various work patterns to watch out for and is meant only for engineering managers. It seemed very basic and something you may already know (if you're working in tech that is). As an individual contributor, I couldn't find anything new and insightful in here, I don't know if managers would have a different take.

We all know things like -
- one shouldn't be a domain champion for a long term sustainability,
- one should request frequent reviews on smaller changes,
- help more than required,
- have a strong sense of ownership,
- define problem scope,
- not have knowledge silos and so on.

I suppose this might be a good guidebook for someone looking to improve team efficiency or understand team dynamics in general.

In conclusion, I personally did not find a lot of merit in reading this.

[Serkan Olgun · Rating 4 out of 5]

This is a collection of 20 work patterns of individuals and teams of Software Engineers, with details of “What is it?” and “How to recognize it?”, as well as suggestions on “What to do?” by Pluralsight. Pluralsight, especially after acquiring GitPrime, has been focused a lot on the data & metrics side of Software Development. Using their experience and expertise, they came up with this guide to help Managers and Leaders with recognizing patterns in their teams and team members, and act accordingly.

It is a short book of 52 pages —half of them are cover pages—, which is easy and concise. Some patterns are quite obvious; but a few of them were very interesting. Although it is not an “eye-opener” material, it is definitely worth the time.

[Héctor Iván Patricio Moreno · Rating 3 out of 5]

Quick and easy but instructive read to learn some of the patterns you want and do not want to see in your team.

[Ferhat Elmas · Rating 4 out of 5]

A short, concise and useful description of patterns in software development teams.

[Shelling · Rating 1 out of 5]

Terrible, absolutely terrible, a waste of time.