lots of colleauges using copilot or whatever for autocomplete - I just find that annoying.

or writing tests - that's ... not so helpful. worst is when a lazy dev takes the generated tests and leaves it at that: usually just a few placeholders that test the happy path but ignore obvious corner cases. (I suppose for API tests that comes down to adding test case parameters)

but chatting about a large codebase, I've been amazed at how helpful it can be.

what software patterns can you see in this repo? how does the implementation compare to others in the organisation? what common features of the pattern are missing?

also, like a linter on steroids, chat can help explore how my project might be refactored to better match the organisation's coding style.