andygrove commented on issue #26257: URL: https://github.com/apache/datafusion/issues/26257#issuecomment-6170623040
Here are my thoughts on this. Dealing with growing complexity and technical debt over time in fast moving projects is not new, but AI has accelerated this exponentially. I haven't done an analysis, but I assume that most contributors and maintainers are putting most of their time into PR creation and PR reviews. When reviewing one PR in isolation we don't tend to question how it relates to all of the existing code in the repo / ecosystem. In addition to PR reviews, I think we need to do regular audits of the whole codebase - perhaps once per release - and look at things like code complexity and duplication, and auditing for regressions compated to the previous release. We started doing some of this with Comet since the 1.0.0 release. There are existing tools for analyzing code complexity and quality. I was too lazy to resarch them so I had Claude build me a custom tool overnight that specializes in the DataFusion ecosystem. Here is an epic with some of its findings (it found a few bugs too). https://github.com/apache/datafusion/issues/26309 I'd be interested in hearing opinions on this kind of approach. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
