HN Explorer

Ask HN: Vim, Emacs and the time spent configuring

2 points by not-so-darkstar ↗ HN
Many developers spend a lot of time "sharpening the axe" for the alleged excuse of increased productivity. At what point this actually causes the opposite effect?

I'm proposing this question since I've come the realization that your tools aren't as important as the internet people make it believe, at the cost of countless wasted hours.

Sure, I may be faster than average at editing code and I can customize any aspect of my programming environment, but what if the time spent learning this knowledge was invested in actually useful knowledge.

4 comments

[ 4.4 ms ] story [ 21.1 ms ] thread
jqpabc123
To some, the computer is more than just a tool. It is an all consuming virtual environment that comes to define their existence.

These folks don't want to avoid the details and minutia and eccentricities of applications, they want to wallow in them.

Their appetite for this sort of "knowledge" borders on addiction. They program the computer but the computer has also programmed them.

clircle
Taking away Emacs may just lead you to procrastinate on something different, not work on something productive. So, I'm not sure that this is a tool problem or a personal problem.
german_dong
What is "actually useful?" My definition is "things that would get my dick wet." Some would say sex that doesn't result in procreation is a waste of time. They would also similarly characterize futzing with emacs or playing candy crush. tldr: you do you.
juxtapose
From a Lacanian perspective: They do it because the configuration loop itself is the Drive. The 'better working environment' is just the Object a (the carrot on the stick), but the true surplus jouissance is the tinkering itself. It's not about efficiency; it's about the thrill of the chase.