๐๐ ๐ช๐ฟ๐ผ๐๐ฒ ๐ ๐ ๐๐ผ๐ฑ๐ฒ. ๐ ๐๐ฎ๐ถ๐น๐ฒ๐ฑ ๐ง๐ผ ๐ ๐ฎ๐ถ๐ป๐๐ฎ๐ถ๐ป ๐๐.
I let AI write 80% of my plugin. Six months later, I was lost.
I found the same logic in three places. Fixing one bug meant searching through code I did not understand.
Speed is great. But speed hides the why. You accept changes without reading. You forget why you made a choice.
Here is how I fixed my workflow:
- Record decisions. Write why you chose a path. List options you rejected.
- Read high-risk changes only. Check API hooks, database schemas, and security. Auto-accept the rest.
- Set strict rules for the AI. Limit file sizes. Use a set naming prefix.
- Write why comments. Do not describe what the code does. Describe why it exists.
- Name tests by behavior. Use names like invalid_signatures_are_logged.
- Use a second AI to audit the first. Ask it to find weak spots.
Heavy docs fail. Only small habits last.
Slow down when you make a big decision. Move fast everywhere else.
Source: https://dev.to/rapls/ai-wrote-80-of-my-plugin-six-months-later-i-couldnt-maintain-it-1a0d Optional learning community: https://t.me/GyaanSetuAi