What to Fix First When Your Generator Slows Down the Whole Solution
You ship a source generator. Next sprint, the assemble slows by forty percent. No new files changed. Just the existing generator, now doing more effort than it should. This is not a bug report. It is a concept failure that compounds every day you ignore it. This bit matters. I have seen crews fight this for weeks: add cache, split the generator, shift to partial methods. Sometimes it helps. Often it makes things worse. Because the real limiter is rarely the one you think it is. So before you throw memory at it, read this. We will walk through what to fix open, what to leave alone, and when to walk away. Fix this part opened. Where the Slowdown Shows Up in Real task According to industry interview notes, the gap is rarely tools — it is inconsistent handoffs between steps.