IMHO, don't use long if/else if/else sequences if you can avoid it; use a command pattern instead. Set up a map of the "values" that can be seen to the commands to perform the processing for those different values, something like the following in Apex:

public with sharing class MyClass {
  private abstract class Command {
    // TODO specifically choose if you want a return value and which parameters are required across all the commands (each 'case')
    abstract void execute(...);
  }

  // Apex (sadly) doesn't support anonymous implementations, so this is more verbose than it would be in java
  class FirstCommand extends Command {
    override void execute(...) {
      // Do the first command's processing
    }
  }

  class SecondCommand extends Command {
    override void execute(...) {
      // Do the second command's processing
    }
  }

  // More command implementations as needed
  ...

  // TODO specifically choose what type the values can be and initialize the map accordingly
  // NB: even though this is static, the map will be re-initialized for each session that needs it, since that's how Apex works
  private static final Map<String, Command> COMMANDS = new Map<String, Command> {
    'first' => new FirstCommand(),
    'second' => new SecondCommand(),
    ...
  };

  public void runTheSwitchStatement(...) {
    ...
    // TODO this variable's type must match the command map's key type
    String variable = ...;

    Command c = COMMANDS.get(variable);

    if (c != null) {
      // TODO pass in the required parameters and process any return value, if required
      c.execute(...);
    }
  }
}

Why go to this trouble?​

1. It avoids evaluating lots of separate conditions; you compute the "variable" once and use its value to select the command required.
2. It helps you modularize/break down your code into smaller but separate blocks.
3. It allows you to write the "runTheSwitchStatement" method as short and sweet, so avoiding a potentially massively long method (code analysis of complexity should indicate it is less complex).
4. It instills an Object-Oriented mindset.