Research · reading

Reading

Short reviews of books and papers that bear on technology for faith: what each argues, what it means for design decisions, where we differ, and how far its evidence goes. Read them before you buy, or after, to connect a book to the work in front of you.

13 reviews
70 sources in our library, 13 read
Updated 10 November 2026

How we read

We read as Christians who build and review technology for faith. That shapes the questions we bring: what does this mean for the person on the other side of the screen, for the practice the product serves, and for the team’s responsibility before God and others? It doesn’t mean we only read Christian authors, or read others as opponents. Many of the most useful books here are written from outside the faith, and we try to state their case as they would.

What every review does

Says what the book argues in one paragraph, in the author’s terms, before we respond.
Connects it to decisions. Each review names the patterns and principles it bears on, with links.
Names where we differ, theologically and in method, and credits where the author sees further than we do.
Separates kinds of evidence: interviews and anecdote, the author’s own research, cited studies, vendor surveys and argument.
Lists the studies we have not checked. A figure reported in a book is not cited as a finding until we have read the original.
Quotes sparingly. At most three short quotes per review, checked word for word against the text, with chapter or page.

Limits

Our reading, not a verdict. We don’t score or rank books. A review says what a source helps with and where to be careful.
Dated. Each review says when and how much we read. Books about AI date quickly; models quoted in them have changed.
No affiliate links. Links go to the publisher, and we receive nothing from them. Book covers are shown small, for review, and credited to the publisher.
Not on our list yet means unread. Items marked “to read” carry no judgement.

Reviewed