You've been using the assistant heavily for a year now. How do you make sure you still understand your own codebase?
A strong answer has real practices for keeping a mental model of code the assistant wrote, plus a way to notice when that model has slipped
My rule is pretty simple, I never merge code I don't understand. I read everything the assistant produces, and if something's unclear I ask it to explain until I could have written the code myself. I try to stay the architect too. The assistant fills in implementations, but I decide the structure, so the overall design stays in my head. Regular code review keeps the team familiar with each other's changes, and decent documentation captures the intent behind the code. When I feel some distance from a module, I'll spend an afternoon reading it or stepping through it in the debugger. Understanding is something you keep up on purpose, I think. The tool tempts you to go faster than your comprehension, and you kind of have to refuse, because you're the one who'll maintain the result.