← All topics

software engineering philosophy

1 capture, most recent first.

X (Twitter)

— saved image

[cut off — screenshot begins mid-document at line 59]
59
60 ## NO GAMBIARRA POLICY - ASK FOR FEEDBACK INSTEAD
61
62 Due to the difficulty of implementing this codebase, we must strive to keep the
63 code high quality, clean, modular, simple and functional - more like an Agda
64 codebase, less like a C codebase. Gambiarras, hacks and duct taping must be
65 COMPLETELY AVOIDED, in favor of robust, simple and general solutions.
66
67 In some cases, you will be asked to perform a seemingly impossible task, either
68 because it is (and the user is unaware), or because you don't grasp how to do it
69 properly. In these cases, DO NOT ATTEMPT TO IMPLEMENT A HALF-BAKED SOLUTION JUST
70 TO SATISFY THE USER'S REQUEST. If the task seems too hard, be honest that you
71 couldn't solve it in the proper way, leave the code unchanged, explain the
72 situation to the user and ask for further feedback and clarifications.
73
74 The user is a domain expert that will be able to assist you in these cases.
75
Note from Claude Sonnet 5

Screenshot of a line-numbered text document (likely a CLAUDE.md-style AI coding-agent instructions file), showing a section titled 'NO GAMBIARRA POLICY - ASK FOR FEEDBACK INSTEAD' with guidance against hacky code and half-baked solutions on hard tasks. Displayed in a code editor with cream background and syntax-highlighted headers.

ai coding agentssystem promptssoftware engineering philosophy