GMAT Prep Strategy & Study Material GMAT   GMAT FAQ Home Contact Us LOGIN Shopping Cart
           
About Us | Forum | MBA | Blog | Tutoring | Free Stuff | Products | Order
You are here: Question of the day
  Student Login
Dashboard Profile Message Center Download Center  
Math Question of the Day Verbal Question of the Day Word of the Day Essay of the Week
     

VERBAL QUESTION OF THE DAY


A corporate CEO may send a directive to the entire corporation with the push of a button. But a mailroom clerk may be prohibited from doing likewise unless he enlists the support of a suitably high-placed executive. It is assumed by position that the words of the CEO are far-reaching in scope and should be heard by everyone in the corporation. He is, after all, the CEO. But the clerk in the mailroom should be concerned with mailroom issues, according to his position. So any idea he might have that affects the entire corporation needs to travel up the management chain, passing management review at each step. If the idea is deemed worthy by each manager in the chain, it will arrive on the desk of an executive who will decide whether it warrants action.

From the mindset of a traditional corporation, the differing abilities of the CEO and the mail clerk to address the entire corporation are understandable. The hierarchy is clearly defined and often deeply ingrained in the functioning of the organization. In this very common management structure, it is expected that communication will flow much more readily from top to bottom than it does from bottom to top.

But this type of structure does not exist in the Open Source world. Although there are team leaders who decide which code is ready for inclusion into a project, there are no executives who determine the direction for the entire community. There is no CEO who decides which problems Open Source will or will not tackle.

Instead, the Open Source model is based on the assumption that if enough people consider a problem, there will be someone for whom the solution will be both clear and elegant. This is the principle that Eric S. Raymond calls, "Given enough eyes, all bugs are shallow." If this method is to work, then it is obvious that everyone looking at the problem must have the ability to make his solution known to the team.

[Pavlicek, Russell. Embracing Insanity: Open Source Software Development. Lafayette, IN. Sams Publishing. ©2000. p 58]


4. Consider the statement "Given enough eyes, all bugs are shallow." What does this mean?
a. The more eyes a bug has, the less room it has for other body parts.
b. Many people considering the same problem can quickly devise a group solution.
c. Many people working together can quickly eliminate possibilities and arrive at the correct solution.
d. The Open Source community has many talented people who can be assigned to work on a problem.
e. Different people view the same problem differently and in a large group, at least one person's understanding of the problem is deep enough to provide a solution for it.



 

 
 Submitted Answers
Student: 2/2/2010 10:02:47 AM
Answer is E.
   
Student: 2/2/2010 4:50:02 PM
e
   
Student: 2/18/2010 3:58:39 AM
option E
   
 
    Answer

The correct answer is E.


Tell a friend about this!
   Questions and answers
    Today
    One day ago
    Two days ago
    Three days ago
    Four days ago
    Five days ago
    Six days ago
    Seven days ago
    Eight days ago
    Nine days ago
    Ten days ago
    Eleven days ago
    Twelve days ago
    Thirteen days ago
    Fourteen days ago
    Fifteen days ago
    Sixteen days ago
    Seventeen days ago
    Eighteen days ago
    Nineteen days ago
    Twenty days ago
    Twenty-one days ago
    Twenty-two days ago
    Twenty-three days ago
    Twenty-four days ago
    Twenty-five days ago
    Twenty-six days ago
    Twenty-seven days ago
    Twenty-eight days ago
    Twenty-nine days ago
    Thirty days ago
 
 
 Test Features | About Us | How to Buy | Links | About GMAT | Site Map | Privacy Policy | *GMAT Trademark | News | Feedback
    Submit Your Comments | Affiliates | Careers | Resources | Essay Grading | Support    
info@gmatscore.com   |  +1 617 229 5146
Copyright © 2009 GMAT Score. All Rights reserved.