> "Working software over comprehensive documentation"

> Tends to make very frustrating-to-use software, because it's never fully working and has minimal documentation.

Another problem:

It makes onboarding new engineers difficult. Without any documentation on what each API endpoint does, or the purpose of every repo, getting an understanding of how the system works ends up requiring scanning through code manually or taking a lot of time from other engineers asking questions.

It's especially bad when microservices are given non-descriptive names like Galactus or Omega Star.