Live data from Hacker News

AI coding and the peanut butter and jelly problem

iamcharliegraham.substack.com

1–10 of 83 posts

Re: AI coding and the peanut butter and jelly problem

#6
Okay, but like.

If you do have that skill to communicate clearly and describe the requirements of a novel problem, why is the AI still useful? Actually writing the code should be relatively trivial from there. If it isn't, that points to a problem with your tools/architecture/etc. Programmers IMX are, on average, far too tolerant of boilerplate.

Re: AI coding and the peanut butter and jelly problem

#8
post #6

Okay, but like. If you do have that skill to communicate clearly and describe the requirements of a novel problem, why is the AI still useful? Actually writing the code should be relatively trivial from there. If it isn't, that points to a problem with your tools/architecture/etc. Programmers IMX are, on average, far too tolerant of boilerplate.

Once you've got to a detailed specification, LLMs are a lot faster at correctly typing code than you are.

Re: AI coding and the peanut butter and jelly problem

#9
post #6

Okay, but like. If you do have that skill to communicate clearly and describe the requirements of a novel problem, why is the AI still useful? Actually writing the code should be relatively trivial from there. If it isn't, that points to a problem with your tools/architecture/etc. Programmers IMX are, on average, far too tolerant of boilerplate.

Useful boilerplate:

- documentation (reference, tutorials, overviews) - tools - logging and log analyzers - monitoring - configurability - unit tests - fuzzers - UIs - and not least: lots and lots of prototypes and iterating on ideas

All of these are "trivial" once you have the main code, but they are incredibly valuable, and LLMs do a fantastic job.

Post reply on HN