2 ms·
I agree to some extent. But there are redundancies that are inherently beneficial and make code more robust and readable, like separating interface from impleme
by layer8 4y ago
I agree to some extent. But there are redundancies that are inherently beneficial and make code more robust and readable, like separating interface from implementation (where some declarative elements have to be repeated), or explicit type annotations instead of full-program type inference. There are also strictly necessary redundancies, like when you pattern-match an ADT, you repeat its declared structure. For desirable or necessary redundancies like that, AI code completion can still save time.
Intelligent unit test creation (if it is indeed intelligent) is also a good use-case. Not to relieve the programmer from thinking, but to save typing and to point out potentially useful tests that you might not have thought of.
- nine_k 4y agoThis is trivial stuff which is handled well by any competent IDE from 2015, and even a well enough-working set of editor templates. I don't see where "AI" is required for stuff like this.
- js8 4y agoI agree, but also, this is actually where AI (whatever it is) would be helpful. Suggesting actual abstractions that could replace boilerplate. Of course, these can build on existing abstractions.