3 ms·

> We are professionals. The defaults, believe me, are not for us. I like this conclusion

• megameter 6y ago
  I have found that the configuration needs are all in the task. Most tasks are default-friendly by dint of harmonizing well. The ones that aren't must be acknowledged, and attacked directly and mercilessly with automation. That could mean a bit of custom code, recording a macro for keystrokes or mouse clicks, or transforming the task into data to make it programmable or searchable. Knowing the tools only means adding more options along these axes. Customizing the WM and editors can help, but it leans more in the direction of directionless tinkering. I develop in Windows and make use of its tiling shortcuts(Win + arrow keys) all the time - it's 80% of a tiling WM and is always there and has been there since Vista. That's the benefit of knowing what defaults can do, and "merciless automation" on top of defaults goes a long way. Anyway, whatever editor you use, you still depend on the keyboard to type the code, the monitor to view it, and comfortable ergonomics for a long session. Identifying the best thing for the task is an art form. I recently invested in cheaper headphones(!) because they are lighter weight and therefore contribute less to neck strain; I also expect them to last longer since drop impacts will be less forceful.