The design guidelines (https://github.com/ardanlabs/gotraining/blob/master/topics/g...) are especially good. And it's not go-specific, it can be applied to any software crafting tool.
We cannot "throw more developpers at the problem".
First because they are expensive. But also because that makes management exponentially expensive while necessarily helping with delivery (lump of work fallacy).
Or you are correct and this is appallingly bad drafting and formatting.