Skip to main content

The Bystander Effect


At work, each floor has a kitchen area, with two beverage fridges, containing sodas, milk, and a variety of juices. Beverages are stocked weekly, and often checked for expiry or spoil. Last week, one of the fridges broke down, and to protect the milk from spoiling, someone moved it to the neighboring fridge. The next day I passed by the kitchen, the fridge was still broken, and more beverages started migrating to the working fridge. A week passed, and nothing changed. I realized that we are witnessing the bystander effect in action.

The bystander effect or bystander apathy is a phenomenon where people are less likely to act when others are present, because they assume that in a group someone eventually will. The apathy increases with the number of people in a group. The internet has a lot of examples of the bystander effect, and advice on how to circumvent it when you need to ask for help. Most of the examples involve dire and emergency situations, which highlight the incongruity of the help offered by the group. Interestingly however, we also experience the bystander apathy in milder non-emergency situations, for example when something is obviously broken, and we implicitly assume that someone else in the group will step up and fix it.

The solution to the fridge problem was very easy. I submitted a facilities request, and within an hour the fridge was fixed, and the beverages happily migrated to their respective locations. Perhaps the bystander apathy has its merit; someone eventually will act.

Comments

Popular posts from this blog

Kindle Paperwhite

I have always been allergic to buying specialized electronic devices that do only one thing, such as the Kindle, the iPod, and fitness trackers. Why buy these when technology evolves so fast that a multi-purpose device such as the phone or a smart watch can eventually do the same thing, but with the convenience of updates that fix bugs and add functionality? So, I was shocked when this weekend I made an impulse buy and got the newest Kindle Paperwhite—a special purpose device for reading eBooks. I was walking past the Amazon store in the mall and saw that the newest Kindle Paperwhites were marked down by $40 for the holidays. The device looked good in the display, so I went in to look at it closely. The Paperwhite is small and light, with a 6” screen that is backlit and waterproof.   The text was crisp and readable, and in the ambient light, it felt like I am reading a printed book. I was sold and bought it on the spot. At home I have struggled to put it down. The bo...

A paper a day keeps the doctor away: NoDB

In most database systems, the user defines the shape of the data that is stored and queried using concepts such as entities and relations. The database system takes care of translating that shape into physical storage, and managing its lifecycle. Most of the systems store data in the form of tuples, either in row format, or broken down into columns and stored in columnar format. The system also stores metadata associated with the data, that helps with speedy retrieval and processing. Defining the shape of the data a priori, and transforming it from the raw or ingestion format to the storage format is a cost that database systems incur to make queries faster. What if we can have fast queries without incurring that initial cost? In the paper " NoDB: Efficient Query Execution on Raw Data Files ", the authors examine that question, and advocate a system (NoDB) that answers it. The authors start with the motivation for such a system. With the recent explosion of data...

A paper a day keeps the doctor away: MillWheel: Fault-Tolerant Stream Processing at Internet Scale

The recent data explosion, and the increase in appetite for fast results spurred a lot of interest in low-latency data processing systems. One such system is MillWheel, presented in the paper " MillWheel: Fault-Tolerant Stream Processing at Internet Scale ", which is widely used at Google. In MillWheel, the users specify a directed computation graph that describe what they would like to do, and write application code that runs on each individual node in the graph. The system takes care of managing the flow of data within the graph, persisting the state of the computation, and handling any failures that occur, relieving the users from that burden. MillWheel exposes an API for record processing, that handles each record in an idempotent fashion, with an exactly once delivery semantics. The system checkpoints progress with a fine granularity, removing the need to buffer data between external senders. The authors describe the system using the Zeitgeist produ...