It didn't read like "bragging" to me so much as being honest about the worst parts of a job, kind of like the "for better or for worse" part of a wedding vow.

It didn't read like "bragging" to me so much as being honest about the worst parts of a job, kind of like the "for better or for worse" part of a wedding vow. Occasional unexpected work is a fact of life for roles that oversee mission critical products. It wouldn't surprise me if this was true at Apple, where small teams are responsible for products that tens of millions of people uses. If a showstopping OSX bug pops up on a Friday afternoon, do you really expect some kind of weekend skeleton crew to do the coding or should, you know, the people responsible for the relevant parts of the code come in?