3 ms·

If I could get them jazzed to tell me about their editor configuration, that was almost always a good candidate. Because people who care about writing code care

If I could get them jazzed to tell me about their editor configuration, that was almost always a good candidate. Because people who care about writing code care about editors. I've spent a great deal of time modifying my editor config. I advocate for "tools day" where I work, which is a day where a team get together to share ideas about tooling and collaborate on config to make the team more productive. I regularly share what I change in my config with people. I couldn't spend more than 30 seconds talking about it though. I have a problem, I solve it, I share the solution, and I spend no time or effort remembering what I did after that. It's one of the least interesting things about dev...

animal531 4y ago
The same here, but to such an extent that it sometimes becomes a problem during interviews. For example I hate laptop trackpads, I always use a mouse, so then during a tech interview they give you the crappiest laptop imaginable without a mouse. I also for example press F7 to compile (along with 20 other shortcuts), so when confronted with a generic editor in a test I'm again wasting half my time struggling around on it.
geraldwhen 4y ago
I find editor usage quite interesting, in fact. I’m responsible for mentoring and training other developers, and mastery of an IDE is the easiest, biggest win you can get for productivity. How do I easily attach the debugger? How do I jump between recent files? How do I use column mode to fix a bunch of sample data? How do I jump between file and test? Junior devs by and large can’t do any of these things, and it has a material impact on work output. So I teach them.