Statement on A.I. Use – September 2025

From the introduction to Self-Guided SQL

“The content in this book was not written by A.I.. It is the result of my research into SQL and SQLite and the words are my own.

“I do use A.I. as an assistant. At times, during the writing process, I have consulted with ChatGPT and other tools for answers on specific technical questions as it’s often easier than going down the rabbit hole of modern search engine results.

“I have asked it to suggest SQL exercises based on the sample databases shown in this book as, for me, that’s the most time consuming part of writing a book like this. I have personally tested and verified all SQL code shown here and, in most cases, I’ve written it myself or heavily modified it from that suggested by the A.I. tools.

“I have also used tools such as Google’s NotebookLM as part of the editing process to verify coverage of concepts, fact-check, check readability, etc.. I am including this statement because I believe that quality content created by humans is inherently more valuable than that generated by A.I. There is no shortcut to true quality or substitute for the willingness of an author to associate their work with their name and reputation. There are also serious issues of intellectual property, copyright and reliability in the training of A.I. tools. It is in the interest of both authors and readers to demand responsibility and transparency in the use of artificial intelligence.”

I continue to define my use of A.I. every day as the tools evolve and I face new situations but this still sums it up well. There is one thing that will not change as long as I continue to create and share content and that is that I take complete responsibility for every word and line of code that I put under my name.

You can find Self-Guided SQL: Build Your SQL Skills with SQLite on Amazon.com and LeanPub.

Sign up for our newsletter to receive updates about new projects, including the new book "Self-Guided SQL"!

We respect your privacy and will never share your information with third-parties. See our privacy policy for more information.

×