For me it's the question, why it's so hard to understand that people have different likings without to downgrade them?
Everyone thinks that his/her decisions are the most sensible ones, but in most cases they aren't.
For me it's the question, why it's so hard to understand that people have different likings without to downgrade them?
Everyone thinks that his/her decisions are the most sensible ones, but in most cases they aren't.
Tried switching from QWERTY to DVORAK recently? Same thing.
Because while everyone can have this or that preferences, personal taste is not the be all end all argument, except in the "it's a free country" way.
Whenever we want to assess the state of our tools, and what we need to make them better etc, we need to reach an agreement beyond "works for me" and personal taste.
Preferred tooling for reaching maximum productivity is an inherently personal thing - you may do your best in emacs, the other guy in vi, yet someone else in Sublime3 on Windows. Nobody is qualified to make broad sweeping judgments as to what works best for everyone.
A few try, and some inferences can be made to the lowest common denominator (see modern UI design practices), but if we're talking productivity for the super-literate user, then no, absolutely not.
For example, I might say that I'm super productive in IDE X, but I don't know for sure that I couldn't be more productive in IDE Y or Editor Z with various plugins. I haven't consulted any research in making my decision nor have I conducted any real research of my own.
I guess maybe it doesn't matter. If everyone is "happy", maybe that's good enough. But I see people struggling to do certain things in their environment of choice and that ends up having an effect on not just them but potentially their coworkers.
I think this is why people tend to make the broad statements about "X is better than Y" since they only have their own experience to go on, but without full knowledge of how someone else's mind works, it's a fool's errand. Even if changing tools would solve the things you can observe and attach a "time wasted doing X" quantity, you don't know if they won't struggle with something else after changing.
This is always true, in every domain. Sometimes it works out and sometimes it doesn't. I think it's worth some amount of effort to find out, but at some point, you have to settle on something and move on.
Personally, I used to be an emacs user, then switched to Eclipse with some emacs keybindings, then learned vim after many years of being frustrated by it, and now use an IDE with a vim plugin (and occasionally straight vim). I feel like I've settled on the best of all worlds... for _me_ at least.
That's the single best reason to stick with something as personal as an editor. Emacs, for example, has all of the features of other IDEs but with a different interface. Want to single-step through a debugger? Got it! Refactor Java? Got it! Syntax highlight 1,373 file format you've never heard of? Oh, definitely got it!
Given that for literally any feature I've seen in other IDEs and wanted to try, Emacs has already had it for a decade, I just don't have an incentive to learn a wholly different workflow.
It could be true that I could make beautiful music on a guitar, but my piano skills satisfy my music requirements. I've played a guitar long enough to enjoy it and I see the appeal, but I like playing the piano more. Both would allow me to express my intent, but I can do it more easily with the interface I've been using for several decades. Why do people keep insisting I pick up a guitar?
BTW, I had this conversation with a manager once. He wanted me to use Eclipse for Python - Python! - development and kept giving me serious grief about my "ancient" Emacs setup. We was quite serious about it, too. I finally prevailed upon him to STFU and let me work with this logic: "Are you happy with my output? You are? Great. That means Emacs works for me. I'm done talking about this."
I wish that were an exaggeration, but I really had to have this conversation with a higher-up. If I'm using Notepad but still able to get my work done on schedule and meeting our quality requirements, then back off.
Unless they work for themselves, that "anyone" can be: colleagues, supervisors, bosses, teachers, and even clients, and also industry experts and seasoned pros telling best practices.
>Preferred tooling for reaching maximum productivity is an inherently personal thing - you may do your best in emacs, the other guy in vi, yet someone else in Sublime3 on Windows.
And yet tooling is regulated all the time in all kinds of companies.
And all kinds of people mistakenly think they are more productive with X, where they would be with Y. People make bad tooling decisions all the time. For those people it's perfectly OK for others to tell them what they should use.
I'm asking what gives anyone the ability to make a correct judgment about tools and productivity?
Extended experience (compared to someone who've only used X, someone who has extensively used X,Y and Z editors trumps them).
Besides, some people have so narrow a view, that almost anybody even a little experienced can immediately tell (correctly) that they are not using the correct tools. E.g. people coding with Notepad...
Also, science. E.g. statistical tests with control groups et al, with teams using A or B editor, and checking for speed of writing code, number of bugs, impediments to workflows, etc.
To my knowledge, no such scientific statistical tests exist with a large enough sample size.