person.dev / anglicanism

What It Means if Your Developer Is Anglican

People do not build things from nowhere. They carry habits with them: assumptions about time, or what words are for.

You probably do not spend much time wondering about your developer's spiritual background. Good. Spirituality, noticed as spirituality, may signal something that is not yet fully embodied, not fully embedded.

And software should communicate that it can stand on its own. A notes application should help you write, whoever you are. The worldview behind a tool may shape certain design decisions while not constantly pointing back to the person who made it.

Still, people do not build things from nowhere. They carry habits with them. Assumptions about time, or what words are for.

So if your developer happens to be Anglican, you may notice a few things under the surface. I just want to suggest some ways to talk about those submerged things. You do not need to be Anglican or call yourself religious for any of this to matter.

A Preference for Rhythm

Anglican life moves through repeated forms.

Morning prayer returns. Evening prayer returns. Repetition can become dead habit. Everyone who has attended church long enough knows that.

Still, there is often an assumption underneath the repetition that people need help returning to things that matter. A developer formed by those rhythms may feel uneasy with software that never seems to end and therefore can never truly be "returned to".

Sometimes we want a tool to simply wait quietly until we need it again.

A Certain Care With Language

Anglican tradition spends a great deal of time around old prayers and carefully repeated texts.

Tiny wording changes can matter. That does something to a person after a while. You may notice a little more hesitation around language. Labels chosen slowly.

Plenty of people outside Anglicanism care deeply about words. Everyone who does has their reasons. One reason, among many, might be that repeated exposure to careful language can train someone to notice how tone accumulates over time.

Some Patience With Silence

Not everything needs immediate resolution.

Anglicanism has regularly acted as if that were true.

Some things become clearer slowly. Some questions remain partly unanswered for a long time. Long traditions have their own way of noticing that.

Software culture rightly rewards speed and clarity, but maybe at the cost of something. Liturgical traditions tend to stop short of explaining everything or removing all uncertainty, which of course can have its own cost.

Confusion is often just bad design. Human beings are also not perfectly legible to themselves all the time.

The Body Is Usually Involved

Anglican worship has always involved physical practices.

Standing. Kneeling. Bread. Wine. The body participates in meaning.

That may shape the way someone thinks about software too.

Not only:

"Can the user complete the task?"

Also:

"What kind of posture does this tool encourage over time?" "Where and how will they be standing or sitting?" "What else will their body need to be doing at the same time?"

Or does it occasionally leave a little room to breathe?

The Tool Is Not the World

Liturgical traditions tend to assume that no single environment should consume the whole person.

Prayer ends for the day. Church ends for the day.

Even meaningful things eventually make room for ordinary life again.

That instinct may appear in software shaped by someone formed in those traditions.

Perhaps the tool stores things locally, as if people are situated in a place, not under the dominion of the software. Perhaps it simply lets you, and expects you to, leave without punishing your absence.

You Do Not Need to Share the Formation

None of this requires agreement.

You do not need to become Anglican to appreciate software that leaves a little room for quiet. Or software that does not constantly demand your attention. Many Anglican developers build loud and exhausting systems. Tradition is not magic.

Yet formation has a way of appearing downstream in unexpected places. Sometimes in an application in the Terminal. Sometimes in a small web app.

Sometimes in a tool that opens, does one thing carefully, and lets you leave in peace.