Don't Flip the Bozo Bit

Do you "flip the bozo bit" on people?

If you don't know what that means, you probably do it unknowingly!

What it means

When you "flip the bozo bit" on someone you ignore everything they say or do. You flip the bozo bit on a person when they are wrong or make a mistake over and over again. Usually you flip the bozo bit unconsciously.

An example

You are writing a program with Bob. Bob constantly writes buggy code. You get frustrated by Bob's bugs and slowly start ignoring all the code he submits and start writing everything yourself. You've flipped the bozo bit!

This is bad for everyone. Now you are doing more work, and Bob is becoming resentful because you are ignoring his ideas and work.

Alternatives to Flipping the Bozo Bit

Instead of flipping the bozo bit, perhaps you could work with another person. If that's not possible, take a more constructive approach:

  1. Teach. Talk to Bob and figure out why he is making repeated mistakes. We all have large gaps in our education. If you've never been exposed to a concept, there's no reason why you should understand it. Try and find what it is Bob hasn't been exposed to yet, and help him learn it.
  2. Change Roles. Maybe Bob should be working in another area. Find an area where you're the bozo and Bob's the expert. Let him work in that area, while you work in your area. He can even explain a thing or two to you.

Why We Flip the Bozo Bit

It seems like a simple evolutionary trick to save time. If someone is right only 10% of the time, would it be faster to ignore every statement they made, or faster to analyze each statement carefully in case it's the 1 out of 10 statements that might be true? Seems like it would be faster to just ignore everything by flipping the bozo bit.

But this is a bad solution. The two presented above are better.

Notes

  1. Thanks to Tom Price for telling me about this.

Links

  1. Bozo bit on Wikipedia.
  2. Origin of the term?


Posted 12/14/2009

Was this essay useful to you? Yes | No
Powered by
brecksblog Posts: What can a Programmer learn from Rock Climbing? Look for a Line Backpack the World with Zero Planning The Economy Explained Ruby You Can't Predict the Future Critical Thinking Kids are Neat How is Intelligence Distributed? Recommendations Are Far From Good Nature Verse Nurture Circle of Competence What Percentage of the Brain Does What The Recency Effect The Ovarian Lottery & Other Side Projects Happiness is in Mediocristan What I Want Orbits The Do You Know Game and Why We Need Celebrities Design Matters, a lot Competition and Specialization Simple, but not easy Flip Flopping The Churn Rate of Data Culture and Complexity The Invention of Free Will Why is it best to do one thing really, really well? The Hidden Benefits of Automation Metrics for Programmers HackerNews Data: Visits as a Function of Karma Don't talk about what you will do, talk about what you have done Why it's worth it to buy the book The Least You Can Do Four Tips to Improve Communication Network Effects If you can explain something logically, you can explain it simply With Computers: Don't Repeat Yourself. With People: DO Repeat Yourself When forced to wait, wait! How to Buy Low, Sell High Flee the Bubble Checklist for New Products Diversification in Startups Thoughts on Setting Goals Problems Worth Solving Make Something 40% of Your Customers Must Have SEO Made Easy: LUMPS Don't Flip the Bozo Bit (un)features Get Stuff Done By Setting Arbitrary Constraints Why You Shouldn't Save Blogging for Old Age 6 Specific Ways to Find Programming Mentors Orders of Magnitude The Many Worlds Law Twelve Tips to Master Programming Faster What's Linear Algebra? Fiction or Nonfiction? Experience is What You Get I'm Back Check out my roommates' companies:
Jellyfish Art makes great Jellyfish tanks
30 Words makes great language guides