I've done much of what kevinkar above has done, plus:
- changed the gear display in the DIS to show the actual gear I'm in next to D or S (can't be done with DSG transmissions)
- activated the OEM alarm
- activate windows down/up with the remote
- enabled window operation for a short while after key out and door open
- disabled Car-Net
- modified DRL behavior so they don't switch off when the turn signals are on
- modified the tails such that the inner tails on the hatch lid copy what the outer tails do (parking lights/turns/brakes)
- enabled the "tear wipe" wiper function (adds an extra wipe at highway speed several seconds after it finishes wiping after a windshield wash)
Plus, OBDeleven has been essential for coding after OEM additions, such as:
- enable OEM door warning lights
- enable OEM fogs
- enable OEM footwell lights
OBDeleven is certainly quirky, the commands sometimes unintuitive, and you can get yourself into trouble really quickly if you just start compulsively changing things to see what they do. The best advice I can give is to first make a backup map of every module (has to be done separately for each module). You can only do this in the pro account version, which I highly recommend paying the $30 for. Keep the text backups in a database such as Excel or Google docs. If you ever mess up coding something, you can always reference your stock backup. You can't re-upload an old backup to revert your module to a previous state, but having the references alone for how your modules were coded as stock is golden.
Check out the link in my sig for all the coding changes I've made, complete with annotations.