[DJBunnies]

I think that all the time.

Or more specifically, "I wish these services were a monolith so we could have better type checks/easier logging/debugging."

[bluefirebrand]

"I wish these services were a monolith so there was any amount of discoverability at all, and I don't have to beg for time from busy people on other teams to help me use their undocumented APIs"

[arinlen]

> I wish these services were a monolith so there was any amount of discoverability at all,

Why do you conflate microservices with discoverability? What's wrong with simply calling a web service?

> (...) and I don't have to beg for time from busy people on other teams to help me use their undocumented APIs

And you believe that the same hypothetical team you claim doesn't document their API would all of a sudden documented all its internal?

[bluefirebrand]

If it was a monolith I would have access to the same codebase, so I could just go look at stuff in the code?

Versus microservices where I might not have permissions to look at their repos.

[thaneross]

It's a fascinating set of priories that lead to these policies.

"We trust you enough to run your code in production but we can't let you read another team's code because you might steal it. Yes, the odds that anyone wants to steal the code for this mundane microservice are staggeringly low... and yes you're going to be less productive and more prone to serious bugs by being in the dark, but that's your problem."

[bluefirebrand]

I honestly don't even know if it's "you might steal it"

It's just this vague notion of "if you aren't contributing to this repo you don't need to access it" or something.