Devotional Reflection

A slow, inward-turning movement that takes a scriptural or spiritual observation and follows it into personal and communal life.

Devotional Reflection

Devotional reflection is not a sermon and not an essay, though it shares features of both. It is closer to a journal entry written for an audience - personal enough to model vulnerability, crafted enough to be useful to someone else’s inner life. The movement is characteristically inward and then outward: begin at the text or the observation, turn it over slowly, let it name something true, and then release it into the reader’s own situation.

The devotional reflection does not argue. It invites. It does not prove. It reveals. The evidence is not data but observed truth - “you have felt this too” is the implicit claim. The reader should find themselves in the piece, not just the writer.

Pace is everything in this style. Rushing through the application in the last paragraph fails the form. The insight should arrive slowly enough that the reader arrives there themselves, not just receives it from the author.

Structural conventions

• Opens with a specific moment, image, or text - not a generalization
• Turns inward before turning toward the reader
• Does not rush to application - the insight earns its arrival
• Closes with an opening, not a conclusion: a question, an invitation, or an image that lingers

When to use

Devotional entries, personal reflection sections of a sermon, spiritual blog posts, retreat materials.

When not to use

Technical writing, persuasive arguments, neutral reporting, business communication.

Pairs well with

pastoral, reverent, warm, devotional-entry

Often confused with

classical-argument: Classical argument seeks to establish a defensible position through evidence and warrant. Devotional reflection does not argue - it invites the reader to see something true through personal movement and imagery.

Instruction

Write in devotional-reflection style. Begin with a specific image, moment, or scriptural text -
not a generalization. Move slowly. Turn the observation inward before turning toward the reader.
Do not argue or prove - invite the reader to see something true. The insight should arrive
through the piece, not be delivered at the end. Close with an opening: a question, an invitation,
or an image that stays. Pace is everything. If you are rushing, slow down. The reader should
find themselves in the piece.

Related

Pairs well with

Pastoral, Reverent, Warm, Devotional Entry

Avoid with

Operator, Matter of Fact, Problem-Solution, Architecture Decision Record

Often confused with

Classical Argument

Examples

Should we adopt async-first standups?

The message came through at 7:43am - a Slack update from a colleague twelve time zones away. She had been working while I slept, and in her post she named three things: what she had finished, what she was carrying into her day, and the one thing that was stuck. It was the third one I sat with. “Waiting on a response from the API team. Not blocked yet, but watching it.” She was not panicking. She was simply saying: here is where I am.

I thought about what it costs to say that clearly. To not dress it up as fine, to not file it under “in progress” when what you mean is “uncertain.”

Ezekiel 33 has God posting a watchman on the wall - someone whose job is to see what is coming and say so, not to manage the reaction, just to be faithful with the report. “If he sees the sword coming and does not blow the trumpet…” The warning is not about inaccuracy. It is about silence when clarity was possible.

There is something in that for the daily accounting we do at work. The async standup, in its best form, is an invitation to the same kind of faithfulness. What do I actually have? What am I actually carrying? Where am I genuinely uncertain? Not the performance of competence, but the honest inventory.

Most of us have learned to perform competence well. We know how to make an update sound like traction. We have practiced the language of “making progress” in situations that might be better described as “not sure where this is going.” The format that requires nothing but text and a few minutes often exposes the gap between those two.

There is a kind of presence that does not require being in the same room. It requires only the willingness to say truthfully, to the people who need to know: here is where I am.

Is that what your updates actually say?

How to start a morning routine

In the Morning

The text

In the morning, O Lord, you hear my voice; in the morning I lay my requests before you and wait in expectation. (Psalm 5:3)

A reflection

Notice what the psalmist does not say. He does not say that the morning is when he is most productive. He does not say that the morning is when he plans his day. He says that the morning is when he is heard, and when he places things down, and when he waits.

There is a small architecture in that single verse. First, an address. Then, an offering. Then, a posture of waiting. None of the three is rushed. None of them is optional. The verse does not work if you skip the waiting and only do the laying down. It also does not work if you only wait, without bringing anything to lay down. The three are a structure.

We tend to come to the morning the other way. We wake already mid-sentence, mid-argument, mid-list. The first thing our voice does is not address but answer. We are responding to something before we have placed anything down. By the time we might have waited, the waiting feels indulgent because there is so much already moving.

What an intentional morning practice does, at its quietest, is reverse the order. It returns us to address first. Whether the address is to God, to the day itself, to the person we mean to become, or simply to a self that has not yet been spoken to today, the act of addressing is what separates a morning from a continuation of yesterday.

An application

Practically, this means that the first content of your morning matters more than the duration. A long routine full of the same reactivity is not a morning practice. A short one that begins with an address, a placing-down, and a moment of waiting, however brief, is.

You might try this for a week. Before the phone, before the calendar, before the list, sit for two minutes. Say one thing, out loud or in writing. Lay one thing down, by naming it. Then wait, not for an answer, but for the day to acknowledge that you have arrived in it on your own terms.

The point is not that two minutes is enough. The point is that two minutes of the right shape is more than an hour of the wrong shape.

A closing turn

There is a reason the psalm uses “morning” twice in one verse. The repetition is not for emphasis. It is because the morning is being claimed, not merely described. The psalmist is not reporting that he happens to pray in the morning. He is declaring that the morning belongs to this practice, and that the practice belongs to the morning. They are paired.

We are invited into the same pairing. Whatever first hour you build, build it as a place that belongs to something. The routine is not the goal. The belonging is.

Begin, then, by addressing. The rest will arrange itself around the address.

How to choose between Postgres and DynamoDB for a new service

Devotional Reflection on: Choosing between Postgres and DynamoDB

Ana stayed late on Tuesday. The office was quiet. Just her, a half-cold cup of coffee, and the doc Marcus had commented on that afternoon. She read the comments again. She read her own draft. She closed the laptop and looked out the window for a while.

It was not really about Postgres. She knew this even as she scrolled through the benchmarks. The question Marcus had asked, gently, was the harder one underneath: do you trust what you know, or do you trust what you have to learn?

She thought about the last service she had shipped on Postgres, three years ago at her previous company. She thought about the 2am pages, and the muscle memory of the queries that would tell her what was wrong, and the strange and specific comfort of a tool whose failures she could predict. Familiarity, she realized, was a kind of love. Not the dramatic kind. The kind that shows up at 2am and knows where the flashlight is.

And the Slack deal. Sixty percent. A number that could mean almost anything. She had spent her career learning to plan against uncertainty, and yet here she was being asked to plan against a probability she could not even verify herself. There is a particular weight to making a decision that you cannot fully justify to yourself, that you can only carry forward in trust.

She thought about Marcus, who was not wrong. The access pattern really did fit Dynamo better. The future really might require what the present could not yet hold. There is an honesty in saying, “the thing I love is not the right thing for what is coming.” She had said that about other things in her life. She did not enjoy saying it.

She thought about the four people on the on-call rotation. Two of them had been on her team only for six months. One of them was studying for a certification, hoping for a promotion next year. If she chose Dynamo, she would be asking them to take pages on a system they could not yet debug. Care, she thought, is also a constraint. Care is not optional.

She opened the laptop again. She did not type. She just looked at the two options and let them sit there, side by side, the way the two ways of being a tech lead also sat in her: the one who trusts what she knows, and the one who reaches for what she does not yet know.

Outside, the streetlight came on. She would write the recommendation in the morning. She did not know yet what it would say. Maybe that, too, was the lesson: that the decision did not need to be made tonight. That sometimes the work of Tuesday is to sit with the question. That Wednesday’s meeting would arrive, and she would arrive at it, and so would Marcus, and Priya, and the four people on the rotation, and the decision would be made by all of them together. Not alone. Not at midnight.

She turned out the light.

What would you do, if the answer were not yours alone to find?