> 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.
And then you hit control-C and resume editing. None of this is as dramatic as you describe, and syntax-highlight freezes aren't as common now with the improved highlighting algorithm in 7.4.
I have not been able to find a good solution to having a personal vibrating timer with me.
Requirements:
Easy to set so no frictional cost to starting a pomodoro for instance. Does not beep. Keeps vibrating until silenced rather than vibrating once and then stopping (I don't notice these).
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.
The absurd thing is that one simple, proposed patch (#20) is just a few lines of actual code - far less than all the "blah blah blah" attached to the bug report.
It fixes the problem now but does nothing to prevent the same problem showing up again in another script. Good maintainers are careful about putting some band-aid over a problem instead of fixing it. And from what he said it seems he rather plans fixing it in Upstart instead of having to patch scripts every-time. That does not sound absurd to me.
Not only is it not productive, it's disingenuous. After all, tihs is a bug that in the worst of cases you're going to be hit by only once (unless you're a masochist), so whoever you tell 'don't do that then' that has just experienced your bug already knows that.
It's the people that haven't experienced it yet that are at risk, and you can't tell those 'don't do that then' preemptively.
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.