4 ms·
I worked in one of the infrastructure SRE teams. These four lines exposed via an RPC a certain state of the system that its internal customers often needed to k
by fishnchips 12y ago
I worked in one of the infrastructure SRE teams. These four lines exposed via an RPC a certain state of the system that its internal customers often needed to know but were unable to find out on their own without specialist knowledge so they ended up filing tickets. Those four lines of code simply embedded that knowledge. I'd imagine a good analogy would be marking a private method public in an API. So in that sense those four lines were not cosmetic and they may warrant some discussion and a mgmt-level decision. But I was completely unprepared for what followed.
- fishnchips 12y agoI suppose what I'm trying to say is that the problem was obvious, the solution was obvious and whether that was the right solution to the problem could be discussed but did not require that level of decorum and could have been handled without engineers' constant involvement.