Skip to main content
removed the stray unicode placeholder char; minor editorial changes; split the last paragraph into easier-digestible chunks
Source Link

I think the suggestion here is unnecessary for a number of reasons, but to touch on this particular episode:

ThereThere is a process by which blog posts that touch on community/site issues are, ideally, presented to my team for review. When the system works right, we've churnedwe churn out a lot of stuff without issues. 

The problem is, the system is brittle - itsit relies on the presence of principals, and the principals were out of the office (Ben was on holiday and I was traveling on personal business). 

We're building some redundancies into the system to prevent this from happening again - I can't promise a 0% error rate, of course, but we'll do better.

I think the suggestion here is unnecessary for a number of reasons, but to touch on this particular episode:

There is a process by which blog posts that touch on community/site issues are ideally presented to my team for review. When the system works right, we've churned out a lot of stuff without issues. The problem is, the system is brittle - its relies on the presence of principals, and the principals were out of the office (Ben was on holiday and I was traveling on personal business). We're building some redundancies into the system to prevent this from happening again - I can't promise 0% error rate, of course, but we'll do better.

I think the suggestion here is unnecessary for a number of reasons, but to touch on this particular episode:

There is a process by which blog posts that touch on community/site issues are, ideally, presented to my team for review. When the system works right, we churn out a lot of stuff without issues. 

The problem is, the system is brittle - it relies on the presence of principals, and the principals were out of the office (Ben was on holiday and I was traveling on personal business). 

We're building some redundancies into the system to prevent this from happening again - I can't promise a 0% error rate, of course, but we'll do better.

Source Link
Philippe StaffMod
  • 21.2k
  • 15
  • 67
  • 88

I think the suggestion here is unnecessary for a number of reasons, but to touch on this particular episode:

There is a process by which blog posts that touch on community/site issues are ideally presented to my team for review. When the system works right, we've churned out a lot of stuff without issues. The problem is, the system is brittle - its relies on the presence of principals, and the principals were out of the office (Ben was on holiday and I was traveling on personal business). We're building some redundancies into the system to prevent this from happening again - I can't promise 0% error rate, of course, but we'll do better.