Code Principle Example: "Explicit is better than Implicit"

explicit.java

/**
 * You've probably heard it before, "explicit is better than implicit". Here's a simple
 * example of that principle in action.
 * 
 * In this example, our app has only two Fragments that can be visible at any given
 * moment: CreateFragment and TrendingFragment. Both examples achieve the same result
 * when everything is working as expected, however... 
 * 
 * In the explicit example, a final else{} branch would indiciate something's not
 * quite right with our code somewhere since we know there are only two possible
 * options: (1) createFragment is visible or (2) trendingFragment is visible.
 * 
 * If there was a bug in our code that caused neither fragment to be visible, the
 * explicit example could help us catch that bug earlier.
 * 
 * Happy coding!
 */
 
 /**
  * IMPLICIT 
  */
    @Override
    public boolean onPrepareOptionsMenu(Menu menu) {
        MenuItem shareItem = menu.findItem(R.id.action_share);
        MenuItem refreshItem = menu.findItem(R.id.action_refresh);

        if (createFragment.isVisible()) {
            shareItem.setVisible(true);
            refreshItem.setVisible(false);
        }
        else
            shareItem.setVisible(false);
            refreshItem.setVisible(true);
        }

        return super.onPrepareOptionsMenu(menu);
    }
    
  /** 
   * EXPLICIT
   */
    @Override
    public boolean onPrepareOptionsMenu(Menu menu) {
        MenuItem shareItem = menu.findItem(R.id.action_share);
        MenuItem refreshItem = menu.findItem(R.id.action_refresh);

        if (createFragment.isVisible()) {
            shareItem.setVisible(true);
            refreshItem.setVisible(false);
        }
        else if (trendingFragment.isVisible()){
            shareItem.setVisible(false);
            refreshItem.setVisible(true);
        }
        
        return super.onPrepareOptionsMenu(menu);
    }