Figure 1a shows how incidents happened substantially less on Saturday
and Sunday even though traffic to the site remains consistent throughout
the week. Figure 1b shows a six-month period during which there were only
two weeks with no incidents: the week of Christmas and the week when
employees are expected to write peer reviews for each other.
These two data points seem to suggest that when Facebook employees are
not actively making changes to infrastructure because they are busy with
other things (weekends, holidays, or even performance reviews), the site
experiences higher levels of reliability.
Via Lobsters, Graham King » Facebook’s code quality problem
I guess Facebook's old motto of “move fast and break
things” was probably not the best motto a company could have.
You have my permission to link freely to any entry here. Go
ahead, I won't bite. I promise.
The dates are the permanent links to that day's entries (or
entry, if there is only one entry). The titles are the permanent
links to that entry only. The format for the links are
simple: Start with the base link for this site: https://boston.conman.org/, then add the date you are
interested in, say 2000/08/01,
so that would make the final URL:
https://boston.conman.org/2000/08/01
You can also specify the entire month by leaving off the day
portion. You can even select an arbitrary portion of time.
You may also note subtle shading of the links and that's
intentional: the “closer” the link is (relative to the
page) the “brighter” it appears. It's an experiment in
using color shading to denote the distance a link is from here. If
you don't notice it, don't worry; it's not all that
important.
It is assumed that every brand name, slogan, corporate name,
symbol, design element, et cetera mentioned in these pages is a
protected and/or trademarked entity, the sole property of its
owner(s), and acknowledgement of this status is implied.
