The last time I was paid to be a developer by a company, the most prominent reasons I was not writing code were: 1. I am in the 5th meeting to discuss the deta

The last time I was paid to be a developer by a company, the most prominent reasons I was not writing code were: 1. I am in the 5th meeting to discuss the details of a 10-page document about a feature that would take 100LOC to write if we weren't using Spring. 2. I am waiting for a dependency manager that is incapable of resuming downloads to download my dependencies from the private repository of dependencies which is located overseas, and my ISP has shitty QOS to that location, and the company's dozens of network and infra people don't think it's worthwhile to set up a proxy on this continent. Or I am using wget to download the dependencies and manually moving them into the dependency manager's cache on the filesystem, which is still slow, but more certain to eventually succeed, since wget can resume downloads. 3. I am learning in my 1:1 that if another developer on my team has attempted to set up some alerting, and our QA has signed off on the alerting, and our SRE has signed off on the alerting, but the alerting is not actually working, it is my responsibility to ensure that the alerting is actually working before my manager learns that it is not working. So I should just do all the work that nominally belongs to my teammates all the time, and delegating tasks is some fake thing to make others feel good, not an actual way to designate a DRI for an objective.