There's also an unresolved bug when a certain email is both coming from an on-prem exchange and at the same time is used as a registered account at Microsoft, outlook seems to have continuous disconnections and prompts to login into the Microsoft account in outlook rather than sticking to the already logged in exchange email. Frustrating to say the least.
That's true for new projects, I've found that as a bootstrap mechanism it is not ideal, takes away your hard earned preferences/know-how abs leaves you barely engaged on the technical path. On the other side I already have quite big codebases, some legacy and inherited, there exist vast amount of context to work on and figure out stuff/fixes/bugs/improvements and Claude Code excels 95% of the time in figuring the existing flows and functionality, if a vague or precise issue is known that's facing some files elaborations or user work flows it can do a good job in pointing out what are, with a high chance, the issues.
I've been through projects that gave schema migrations and when there was any mistake or error during schema migrations it was a real big pain to rollback, fix and release. With mongodb this is gone, schemas are no more of an issue as long as you make sure to keep the models sane and the business logic of the fields up to date.