Programmer Humor

The documentation I mean here should be in the repo and checked as a part of the PR process. I don't mean it should be a manual, I just mean a readme should at least describe what the service does (it has such a generic name in my case that it's not self-evident and is so broad in scope I don't know what happened). The functions also have terrible naming and no comments to describe what they do. So, as a guy just coming into this team after re-org with no idea what all this stuff does, I was completely lost. They also changed which services which teams owned, further making it difficult to get knowledge.