Is there work you deliberately keep away from the assistant? What kinds, and why those?
A strong answer has an actual rule for when generation is off the table, and the rule comes down to what verification costs.
I keep it away from anything where a mistake would be expensive. So core business logic, security-sensitive code, anything touching authentication or payments, I write that myself, because those need careful human judgment. Architecture decisions too, since they depend on context about our systems and our team that the model just doesn't have. Where it does well is the routine work. Boilerplate, tests, small utilities, documentation, explaining code, all of that fits. So I lean on it when the task is well-defined and low-risk, and I do the high-stakes thinking myself. It's a tool with limits, and I think the job is knowing where it's strong and using it there. When I'm not sure which side a task falls on, I default to writing it myself and only reach for the assistant once the shape is clear.