[SanderNL]

Developer productivity is not and never was bottlenecked by their tools.

One snap of the fingers in one of the many layers above us and million dollar projects succeed or fail. We are always a fancy dinner or business relation gone sour away from success or failure.

Vim or emacs come into play at layer 245 in the system and their impact on the final business reality is approximately 0,003%.

[globular-toast]

> Vim or emacs come into play at layer 245 in the system and their impact on the final business reality is approximately 0,003%.

Who cares? One fire or war and a carpenter's work all comes crumbling down. Should he then not care about his work or his tools or materials and nail any old shit together? Life is what happens when you're busy making other plans.

[SanderNL]

Who cares? Those who measure actual impact instead of showing off.

Focus on what matters is my only advice. Hint: it’s not your editor.

[freedomben]

Sure, sometimes higher layers end up killing a project before it ships. But there is still a lot of code that ships. For that code, the editor choice may have mattered. I have shipped a lot of code in my day, and since learning vim I have been much more productive. There are projects that may not have even existed were it not for Vim, because I would not have had time to get it done in the tight deadline needed.

But more importantly, I like Vim. It makes me enjoy the process much more. I do carpentry in my spare time, and I think of them much like I do my favorite carpentry tools. While they do enable some projects that otherwise couldn't have happened, most of the time their impact is just improving my experience and quality of output. That matters a great deal to me, regardless of whether it matters several layers up.

[globular-toast]

You can talk all day about high-level actions and wishes but, at the end of the day, someone needs to write some code. That's me. That's what I do. It matters.

[layer8]

For many, the editor is the software that they spend the most time using. It certainly matters knowing how to use it well.

[fragmede]

just because the project got cancelled and won't ship doesn't reduce the rate of developer productivity on the project though. it sucks when your code won't ship, but the craftwork imbued in the source is still there.