6 ms·
> But general code search, linter/test integration, and embedded features like autocomplete, pop-up signatures or docs, etc., are disastrously bad things hands
by Denvercoder9 7y ago
> But general code search, linter/test integration, and embedded features like autocomplete, pop-up signatures or docs, etc., are disastrously bad things hands down for regular development.
Do you have any substantiation for that claim?
- mlthoughts2018 7y agoMany years of experience leading software teams and watching these tools hold back younger engineers time and again. Random breakages, surprise integration quirks, facilitating confusion of the design principles in the underlying code they only see through the IDE, inability to do necessary work in environments that can’t support the IDE (like during an outage that requires access to a different environment for a change). It’s been one of the most common patterns of lost productivity I’ve seen in my career, across many companies and many cohorts of engineers that would control for virtually any confounders, leaving me only to believe it’s the principle of using IDE assistance for these things.