Generative AI for Software Development

Chapter 2. Bug Detection and Code Review

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 3rd chapter of the final book. Please note that the GitHub repo will be made active later on.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

Imagine paying the highest salaries in a company to software engineers to develop a product that will be responsible for the company’s revenue, only to lose that revenue due to costly bugs in production. This is any business owner’s worst nightmare, and sadly it happens every day. Software has automated whole industries, replacing lengthy manual processes and creating new ways to do previously impossible things. However, automation can’t be effective when bugs detract from the underlying products’ key functionalities.

To mitigate this fundamental concern, several job titles have been created over the years to guarantee proper quality assurance (QA), such as QA Engineer, QA Analyst, and Test Engineer, etc. Processes, too, have been developed to detect bugs before they get deployed to production. Those processes boil down to two main categories:

Code reviews

This process is done during development, ...