6 ms·
How will you know when it's actually working as intended? The issue is /strongly/ epistemological.
by Fellshard 4y ago
How will you know when it's actually working as intended? The issue is /strongly/ epistemological.
- nineteen999 4y agoI think this is the main thing that sticks out to me. I think Hillel Wayne is right to point out that it moves the main task of a developer from writing code to proofreading it (to a small degree now, perhaps to a larger degree in the future). Most programmers prefer to write their new code than to read someone else's. So if we are delegating our favourite parts to AI, how long before we ask it to write the unit tests as well? Who's going to validate that the unit tests it writes are correct? I forsee a bunch of frustrated QA teams at least in the (near) future being asked to test sloppy code which has passed a bunch of sloppy unit tests, but has had only minimal review from the developer(s) responsible for it. Perhaps I'm overthinking it.
- bqmjjx0kac 4y agoThe QA team composed of AIs says it looks OK — ship it!