@mattpocockuk Make sure you understand and is in control over how your product is evolving. The method and scale above is something arbitrary to argue over. Pointless other than generating engagement.
@mattpocockuk Compaction seem to happen in time without me micro managing it from vscode or gh copilot.
Handoff when you want a clean slate because you can generate a summary which is sufficient for further work without the conversation history.
Clear when stuck with irreversible instruction
@jayphelps@jamonholmgren My point is that review in general is a separate discussion from whether we should know what code or AI is writing. And we should definitely know what it's writing before we post it in our own name as a PR.
@jayphelps@jamonholmgren You're not supposed to review the code after it's written, you're supposed to review it as it's being written. The AI is a copilot, not a replacement. AI assisted, not offline agents, is the way.
@davidfowl@ismetkahraman@Dave_DotNet So the solution was to make the controllers non-generic with a generic service layer called from the controller. Not as elegant as what we had. But works and did unblock the upgrade
@davidfowl@ismetkahraman@Dave_DotNet Controller types used to be mapped late. Now they're mapped early. That means we can't find the right closed type lazily with types determined by a scope matching some search params
@davidfowl@ismetkahraman@Dave_DotNet 8 to 9 broke our custom https://t.co/UZKDf1HEP4 middleware for dynamically closing generic controllers. Aot changes. That was hard to fix...