alphard

> When you hear the words "Yup, we do Agile, but we have our own take on it," run away, because it's going to suck hard.

Every team/company has their own take on Agile, copying what other successful teams do verbatim doesn't necessarily work. There are objectively many wrong ways to do Agile (your above example being one) but not any single "correct" way.

> It also means I never get a "process is running" prompt like in IntelliJ or Emacs when I want to exit.

No, instead you find that you can't :q - or type anything for that matter - because everything's frozen while vim is realising that the network drive is down, or you're waiting for the syntax highlighting to finish.

With the same money you can buy a Pebble, and I'm sure that someone could easily write a Pebble app that vibrates every 5 minutes.

I'm using the following to expand "%%" in command mode to the full path of the current open file's directory:

  cabbr <expr> %% expand('%:p:h')

You could also use :. instead of :p to get the relative path, see :help c_% and :help filename_modifiers

Well, although the maintainer's initial responses weren't very helpful it seems that the bug had already been fixed.

I guess it was really just a case of a bad day after all but he handled it gracefully in the end. This recent post clarifies things: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/55717...

Changing his mind (without hinting that he may have been wrong) was a step in the right direction, and he did propose a clean fix that will prevent other similar bugs, but he flagged this as a wishlist which shows that he still doesn't consider it to be of major importance. He could always safeguard the script and treat his suggestion as a wishlist item, which would have been more reasonable.