4 ms·
I classify my work into priorities such as P0, P1, and P2. For P0, I write the code myself and use AI only for verification. This includes business logic or ar
by jdw64 6mo ago
I classify my work into priorities such as P0, P1, and P2.
For P0, I write the code myself and use AI only for verification. This includes business logic or areas where failure must not happen. Typical examples are JWT authentication, API key handling, and, in PLC-related work, equipment interlocks, deletion logic, and machine control.
For P1, I use AI when writing logic that connects the backend and frontend. Even if something goes wrong, the damage is relatively limited, and I have found that AI often writes this kind of code better than I do, especially when it is built on top of P0 logic that I have already defined.
For P2, I let AI write the code and only verify that it builds successfully. This mostly applies to frontend-related work. Of course, if the frontend includes core animation logic, I may write that myself, but in most cases I let AI handle it.
- karlosh 6mo ago[dead]
- Garza231 6mo agoGood framework. The one risk is that P1 code written by AI can silently break the assumptions your P0 code was built on. Worth adding a periodic check for that boundary specifically.
- jdw64 6mo agoAdding a verification layer is always the right move. That’s a good idea. I should think about adding some kind of periodic check as well.
- quadium4004 6mo ago[dead]