6 ms·

I've seen far too many developers spend far too much time configuring literally everything but especially their IDEs. I've gotten so very tired of hearing that

I've seen far too many developers spend far too much time configuring literally everything but especially their IDEs. I've gotten so very tired of hearing that nonsense as an excuse in a scrum for no progress yesterday. I don't care. I don't need their tools to do my job; maybe they quite literally do and couldn't make any progress with out them...but I'm more convinced these types have little appreciation for work ethic. All the configuration knobs on an IDE don't make a lick of sense if your goal is being useful to those paying for your services. Each and every one (with the exceptions of autocomplete, goto and syntax highlighting) are better implemented as separate tools. But that mentality got lost long, long ago.

damagednoob 6y ago
I keep relearning this lesson: First it was with competitive gaming. In tournaments, competition machines have their configs reset after each match. You have a limited amount of time to setup before game time because admins also have to check your config. I learned to have a fairly simple config (i.e. close to defaults) so I wouldn't run out of time. Second time round it was with vim and Ruby. I spent nearly 2 months trying to get the right combination of plugins to get something close to a decent IDE experience. I ended up packing it in for RubyMine which gave me what I wanted right out the box.