I tend to agree with this as well. In my own experience, dealing with software written with "forced collaboration" (meaning bringing more than 1 developer just

I tend to agree with this as well. In my own experience, dealing with software written with "forced collaboration" (meaning bringing more than 1 developer just for the sake of saying it was done by a team) usually results in more difficulties in later maintenance than the other way around. Specially in micro/tiny services, where sometimes one person can do most of it quickly. I agree with you take and had the same feeling that the author just seems to have faced one of those cases and extrapolated.