Blog RSS Feed

Archive for the ‘Reading’ Category

Read through Hebrews One Verse at a Time in 2023 with AI Help

Tuesday, December 27th, 2022

The 2023 Daily Cross Reference Bible Reading Plan (also an RSS feed) walks you through the 303 verses in the book of Hebrews one day at a time, six days a week, with a review every Saturday. It includes up to twelve of the most-popular cross references for each verse, as well as an AI-generated summary of how each cross reference relates to the main verse. Each day also contains an AI-written introduction and a concluding prayer that tie together the themes between the main verse and its cross references.

For example, one of the explanations for January 1 connects Hebrews 1:1 and Genesis 3:15 like this:

Both passages refer to God’s plan of salvation. Hebrews 1:1 refers to God’s promise of redemption through the prophets, while Genesis 3:15 refers to the promise of a Redeemer who would come to defeat Satan and restore humanity.

The quality of the content generated by the AI (GPT-3) feels generally comparable to the typical evangelical devotional; I review the generated content by hand before posting it.

In 2016, I proposed a digital-first Bible reading plan that goes through the Gospels in a year, including all the cross references for each verse. This reading plan is an implementation of this idea with an AI twist and exposes you to 2,295 different verses, or around 7% of the whole Bible.

If you’re looking for a full-year, brisk reading plan for 2023 that you haven’t done before, you might give the Daily Cross Reference Bible Reading Plan a try. You can bookmark that page, which will update itself every day, or subscribe to the RSS feed. To get a sense of what the content is like before committing, between now and January 1, the reading plan features some seasonally appropriate verses chosen by ChatGPT.

The four kinds of one-year Bible reading plans

Thursday, December 29th, 2016 currently has 91 yearlong reading plans. By graphing these plans with time on the x-axis (January on the left, December on the right) and verse on the y-axis (Genesis at the bottom, Revelation at the top), we can divide them into four categories, labeled below:

An 8x12 grid of 91 reading plans.

First are continuous plans, which proceed in a sequential pattern through the Bible. They’re at the top of the above chart, characterized visually by strong lines proceeding from the lower left (January / Genesis) to the upper right (December / Revelation). They tend to cover substantial portions of the Bible, usually either the whole Bible or the complete New Testament. They generally ask you to read four or fewer distinct passages per day, with each passage about a chapter long.

Next are semi-continuous plans, which are the hardest kind to define. They feature stretches of reading that immediately follow from what you’ve just read, coupled with days of reading that are… not what you just read. You can see some lines go up to the left, similar to the continuous plans, and then they stop or dissolve into smaller sections. Defining a continuous vs. a semi-continuous plan is a matter of opinion; you could argue that some of the plans I’ve classified here as semi-continuous should be continuous. The most-interesting one to me is #34, the Book of Common Prayer Daily Office, whose pattern follows the liturgical year and doesn’t resemble any other plan on the chart. (Ten years ago I plotted both years of the Book of Common Prayer on a similar chart.)

Third are chronological plans, identifiable by their unique pattern of parallel passages in Kings and Chronicles (the parallel orange lines). Not all plans in this category are strictly chronological, but they have a similar organizing principle that produces the recognizable pattern of parallel paths.

Last are selections, which follow no discernible pattern and typically involve shorter readings–a few verses from multiple places in the Bible rather than reading full chapters. This kind of plan often includes devotional content related to the selected verses. The average plan in this category covers about 1,800 verses per year, or about 6% of the Bible’s 31,000 verses.

All the plans together

Here’s what all 91 plans look like overlaid on each other:

Paths radiate from Genesis in January to Revelation in December.

Paths radiate from Genesis in January through Job later in the year, varying mostly in the pace you’re reading the bulk of the Old Testament. In other words, if your reading plan starts by reading Genesis at the beginning of the year, you’re likely to proceed sequentially through the Old Testament until you reach Psalms. Similarly, paths converge on Malachi and Revelation in December.

Where are the digital-first plans?

The similarity among these plans suggests to me that they originate from a print-first mindset: what’s convenient to read in a physical Bible. You’re not, for example, going to flip to passages all over your print Bible every day unless you have unusually strong dedication to your reading plan.

But digital reading plans don’t have this limitation. Thanks to transclusion, a digital plan can collect content from all over the Bible (and elsewhere) and show it to you in one place, which means you can read much more widely on a single day if you like.

For example: let’s read through the Gospels chronologically in one year–that’s about ten verses a day–and also include ten cross-references for each verse every day. During a year, you read 14,104 different verses, or just under half the Bible. Here’s what the plan looks like schematically; you can see the paths through the Gospels, and overall it doesn’t look like any other plan:

The chronological Gospels plan shows a different pattern from other reading plans.

And here’s what the content for a single verse from one day’s reading could look like (because there’s so much related text for each verse, this plan requires a little information design): the current Gospel verse is at the top. Below it are three columns: one for Old Testament references, one for other Gospel references, and one for non-Gospel New Testament references. I also included the same color-coding as in the other charts in this post.

Matthew 5:5 with three columns of text.

Beyond transclusion, interactivity is a key property of digital systems. You could add interactivity by allowing the plan follower (with an interactive plan, they’re not just a “reader”) to configure the number of cross-references they read. Or tapping a cross-reference could open other verses they’ve read or will read as part of the plan–letting them explore more deeply and follow patterns as they desire. Adding interactivity to a system opens new avenues for insight.

Reading plans for augmented reality or audio-only interfaces will similarly vary in form from existing print-based plans. I would suggest that they will probably be even more conversational and dynamic than what I describe here.

I don’t know what shape future digital Bible reading plans will take, and the current approach of converting print-first plans to digital will certainly persist. But new digital-first reading plans will also come into being, and it’s important to experiment with what new technologies allow.

Seasonal Interest in Bible Reading Plans

Thursday, January 1st, 2015

Just in case you wonder how seasonal people’s interest in reading the Bible is, here’s a chart from Google Trends showing five “read through the Bible”-related search terms. The peaks every January speak for themselves. You can see a secondary peak in August or September when classes get underway at many schools.

If we take some of the above data, plot it by week rather than by month, and add it together, the effect is even more vivid:

This chart shows peaks every January.
(This chart goes through December 27, 2014.)

You see huge peaks just before and after January 1 each year, along with a small bump around Easter and the aforementioned mellow spike in August or September. The interest related to the new year is almost entirely gone by February. You could interpret this drop as “Everyone who’s interested has already found their reading plan for the year,” or you could interpret it as, “Well, Genesis was interesting. Maybe I’ll read through the Bible next year.”

Inspired by Google Trends of Popular New Year’s Resolutions.

Bible Reading Tech

Saturday, May 12th, 2007

Bob Pritchett from Logos Bible Software points to Live Ink, a technology that takes normally formatted text and breaks its clauses into lines to improve reading comprehension. It looks like this:

A sports report is broken into lines: Hal Atkinson, / Mickey Walters / and rookie sensation…

Having been an English major, I keep trying to assign meaning to the line breaks—you pay close attention to line breaks when explicating poetry, and it’s hard to stop noticing them everywhere once you start noticing them in poetry. Live Ink has research to back up their reading claims; I’m not one to question their findings. So maybe I’m an anomaly, but studying the Bible in a similar format would distract me.

Speaking of things that distract me, a few years ago I came across an example (now lost on the hard drive of a deceased computer) of an interesting way of reading the Bible: one word at a time. The program cycles through the text of the Bible, showing you only one word on the screen—blink and you miss it. This Flashconverted to HTML5 in 2016 demo I just whipped up gives you the general idea:

You may need to read this post outside an RSS reader to see the demo. Not inclined? Here’s a screenshot. Picture the words rapidly scrolling upward:

The words “at my watchpost and station” are visible, with “watchpost” being the most prominent.

Honestly, I can’t decide if it’s a good idea or a bad one. The hardest part for me is that it requires more sustained concentration than I usually devote to reading. It might be useful if someone could come up with an intuitive way to control the speed and allow time to blink. Like Live Ink, it may simply take some getting used to.

(The way the demo scrolls kind of reminds me of William Shatner’s line delivery in Star Trek—it pauses slightly on longer words, which was apparently the key to Shatner’s acting in the 1960s. Actually, the line breaks in the Live Ink screenshot above remind me of how he would read a box score, too. Maybe he was just ahead of his time.)