๐๐ ๐ช๐ฟ๐ผ๐๐ฒ ๐ ๐ ๐๐ผ๐ฑ๐ฒ. ๐ ๐๐ฎ๐ถ๐น๐ฒ๐ฑ ๐๐ผ ๐ ๐ฎ๐ถ๐ป๐๐ฎ๐ถ๐ป ๐๐.
AI wrote 80% of my plugin. I felt fast. Six months later, I failed to maintain it.
I found the same logic in three places. The bug was easy. Reading my own code was hard.
Speed hides the cost. Chat history vanishes. You accept code without reading. You lose the reason for your design.
I changed my workflow to fix this.
- Save the why in a file.
- Write one paragraph per feature.
- Review public API changes.
- Auto-accept internal changes.
- Set strict rules for folders.
- Name tests by what they do.
Heavy processes fail. I tried long specs. They did not work. I tried reading every line. I quit by lunch.
Small habits worked.
Write why you rejected an option. Future-you will try the same wrong idea again.
Comment on the reason, not the behavior. The code shows the behavior. The comment shows the intent.
Slow down at the seams. Slow down when you decide a boundary. Let the AI run fast in the middle.
Your future self will thank you.
Source: https://dev.to/rapls/ai-wrote-80-of-my-plugin-six-months-later-i-couldnt-maintain-it-1a0d