QuantLib and A.I.

Hello there. I don’t use A.I. for my posts; I prefer the human touch (and if you suspected I did use it because of em-dashes, I can point you to a snapshot of my blog from 2015 where you can see that I averaged a couple of them per post). But this doesn’t mean I’m opposed to using A.I. for coding.

(And before I forget, let me remind you that the Internet Archive provides a great service and you should donate if you can. I just did.)

Now, as I was saying: using A.I. for coding. In the past few months I started receiving pull requests for QuantLib that were developed using it, and I’m not saying that to disparage them: the authors made no mystery about it, and the quality was good. I might have been lucky. Anyway, this got me thinking: is there any way (ranging from a simple AGENTS.md to a more elaborate harness) in which we can make it easier for people to use A.I. when contributing to QuantLib?

I don’t have definitive answers myself: I’ve been using Claude for just a few months now on proprietary code at work, I like what I’m seeing so far, but I’m not an expert. Instead, I’m hoping to start a discussion about this: I opened an issue on GitHub to host it, and you’re welcome to contribute your experience, suggestions, caveats, or whatever you think useful.

That’s all for today; I’ll get out of the way now and let you think about it. Thanks, and see you next time—or, hopefully, on GitHub.