Behind the curtain: what it feels like to work in AI right now

Re:Behind the curtain: what it feels like to work in AI righ... by jacquesm on Friday April 07, 2023 @02:05AM (#35478590)

It isn't in my experience. Understanding code that you did not write for a problem that you do not fully grasp is a lot of work. It's hard enough when you did write the code and when you do fully grasp the problem, which you'd have to if you were to write it yourself. Typically that's what first draft code is for: to see if you actually understand the problem.

[ Parent | on HN ]

Re:Behind the curtain: what it feels like to work in AI righ... by copperx on Friday April 07, 2023 @02:49AM (#35478870)

Understanding the code of a fully fledged application is hard.

But with ChatGPT you can build it piece by piece.

[ Parent | on HN ]

Re:Behind the curtain: what it feels like to work in AI righ... by jacquesm on Friday April 07, 2023 @03:01AM (#35478937)

With a brain you can also build it piece by piece, in fact I don't know of any other way of writing a large software system than doing it piece by piece.

[ Parent | on HN ]

Re:Behind the curtain: what it feels like to work in AI righ... by copperx on Friday April 07, 2023 @11:31PM (#35490253)

Sure, but the argument was that reading an entire application's code is hard, therefore GPT-4 is counterproductive.

[ Parent | on HN ]

Re:Behind the curtain: what it feels like to work in AI righ... by IanCal on Friday April 07, 2023 @05:41AM (#35479878)

Do you find it takes more time to review a PR than it took for someone to figure out the solution and implement it?

[ Parent | on HN ]