Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To what extent can the overthinking be reduced by a better system prompt? For instance, telling it not to overthink, embellish or snazz anything up, and just directly deliver the most what was requested without in the plainest form to build on in future iterations.


I tried "render an svg of five intersecting squares. don't overthink this" and... it overthought it: https://static.simonwillison.net/static/2026/cors-chat.webp


I don't think "don't overthink" is a useful guide, it's too ambiguous which leads to the model overthinking how to interpret the advice to not overthink.

I think guidelines have to be specific, such as "provide only the specific properties specified, and if other properties are required but are not specified, then ask for clarification or pick the simplest default possible". Even that's ambiguous on "simplest default possible".

I would be more specific in specific domains. The circle example from the article is clear that it defaults to elaborate stylistic choices rather than simple colours and shapes, so the prompt would have to specify "use only simple colours and the simplest possible shape that fulfills the request".


It's already very keen not to overthink.

Thinks about it all the time.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: