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.

Tells

• Opens with a specific moment, image, or text rather than a generalization
• Moves inward first - turning the observation over - before turning outward toward the reader
• Does not rush to application; the insight is given room to earn its arrival
• Closes with an opening - a question, an invitation, or a lingering image - rather than a conclusion
• Invites and reveals rather than arguing or proving; the implicit claim is “you have felt this too”
• The reader is meant to find themselves in the piece, not only the writer

Anti-patterns

• Constructing a defensible claim with evidence and warrant and working to prove it - Arguing a position is classical argument, a confusable neighbor; devotional reflection invites the reader to see something true rather than establishing it by proof.
• Rushing the application into a brisk final paragraph - Pace is the form; delivering the insight quickly at the end means the reader receives it from the author instead of arriving there themselves.
• Opening on an abstraction or a general truth rather than a concrete moment or text - The inward-then-outward movement needs a specific starting point; a generalization gives the reflection nothing particular to turn over.

Failure modes

• Over-sentimentalizes, leaning so hard on emotional language and the slow reveal that the feeling reads as manufactured rather than observed and the reader senses they are being worked on - Let the concrete moment and the shared experience carry the emotion; trust the reader to feel it, rather than instructing them how to feel through swelling language.
• Slows the pace until the inward turn becomes self-absorbed, lingering on the writer’s own interior so long that the reader is never released into their own situation - The movement is inward then outward; once the observation has named something true, turn it toward the reader so they find themselves in the piece.

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?

Telling stakeholders a committed feature is being cut this quarter

The moment it became clear was not dramatic. Someone pulled up a spreadsheet of remaining engineering weeks, and the numbers simply did not close. There was no argument to be had. The quarter had made its own decision.

We had promised you Insights. We said it plainly, and we meant it. The analytics dashboard was real to us - not as a feature on a list, but as the thing that would finally let you see your data the way you have been asking to see it. We had planned it. Prototyped it. Talked about it with you, some of us, over calls where you described exactly what you needed. We carried that weight with us.

There is something particular about the moment when a commitment you made in good faith runs into something you did not foresee. You have probably been in a version of this yourself - not necessarily a software feature, but something you promised and believed you could keep, and then watched a circumstance arrive that the promise had not accounted for. The right action becomes clearer than it was a moment before. You can deliver something half-built, which satisfies neither the promise nor the person you made it to. Or you can say the thing you do not want to say: not this quarter.

The billing migration was not optional, and it consumed the engineering capacity that Insights needed. We made a choice to let that run through cleanly rather than stitch two incomplete things together. That choice came at a cost, and the cost was yours to bear as much as ours. We do not say that lightly.

What we can give you before September is a CSV export of the underlying data - not the dashboard we promised, but the data itself, accessible, ready for the spreadsheet or BI tool you already use. It is not what we said. It is what we can stand behind right now.

Insights is scheduled for Q1. We will bring it forward as soon as the ground is clear.

We are not asking you to make peace with this today. We are asking only: can you stay with us until January? The work has not been abandoned. It has been held.

Getting a new engineer productive in their first two weeks

She arrived at nine on Monday with a laptop bag and a careful smile.

I watched her scan the room - the way new arrivals always do - counting chairs, finding the coffee, locating the one face she had spoken with before. She did not yet know where the bathroom was. She did not know that the ticket tracker fills up fast on Monday mornings, or that the on-call engineer always looks slightly haunted by ten.

I noticed the smile first, though. Careful. A smile that does not ask too much, that has learned not to assume warmth will be returned.

There is something in that particular expression - the one that says “I hope I belong here” while performing a confidence it does not yet feel - that I have seen on my own face in mirrors, in other buildings, on other first days. The pretense of readiness. The hunger to be useful quickly enough that someone will want you to stay.

We sometimes call this an onboarding problem. We build checklists for it. Access provisioning, codebase walkthroughs, pairing sessions - all good, all necessary. But the checklist does not address what Priya was actually asking when she scanned the room: not “where is the coffee” but “is there a place for me here?”

The access gets set up. The codebase gets walked through. She pairs on a small change by Thursday of week two, and it ships, and it is real, and she is briefly thrilled and briefly afraid. These things happen with process.

What does not happen with process alone is belonging. That is slower work, and it does not live in the wiki or the ticket tracker or the pairing session, though all of those carry it when done with attention. It lives in the moment someone says, “That’s a good question” and means it, or “Here’s why we do it this way” instead of just “This is how we do it.” It lives in the difference between being shown a codebase and being let into one.

Priya will learn to read the deployment logs. She will learn the unspoken rules about who handles which incidents. But will she learn that this team considers her an engineer and not yet another new hire to ramp?

That is the question worth sitting with, before any checklist begins.

Writing to thank a mentor who shaped your career

There is an afternoon I have carried without knowing I carried it.

I was sitting at my desk when the email arrived - your name in the sender field, a thread I hadn’t known you were composing. I read it twice before I understood what you had done. You had introduced me, to the whole team, as the lead for the Caldwell project. Not “will be working closely with,” not “has been helping to shape” - lead. Present tense. Already decided.

I want to tell you that I felt ready. I didn’t. I felt the way you feel when someone calls your name from across a room and every head turns - a sudden, clarifying awareness of where your hands are.

What you did next is the part that took me a decade to see. You didn’t rescue me. You didn’t take back the introduction or soften it into something smaller. You also didn’t disappear. You appeared in my doorway that week and the week after, asking questions I could answer and questions I couldn’t, and when I couldn’t, you waited. You had patience of a particular kind - not the patience of someone who expects you to fail and is bracing for it, but the patience of someone who has seen something in you that you have not yet seen in yourself and is simply waiting for you to catch up.

I understand now what that cost. The project could have run faster without me learning on it. You had things to do. The patience wasn’t free.

Last month I found myself writing an email introducing someone I manage to a set of stakeholders she didn’t know. A project larger than she had run before. I felt you in my hands as I typed. I hadn’t been thinking about you. I didn’t plan it. But the sentence came out the way yours did - certain, clean, no hedge - and I realized I had been taught something I didn’t know I had learned.

I don’t know if gratitude like this lands right when it arrives ten years late. I suspect you would say something quiet about how it was never late, only timed. But I wanted to say it plainly: what you made possible wasn’t just the project. It was the person I would become in the years after, every time I chose to trust someone the way you trusted me.

I keep wondering who taught you.

Reflecting on keeping a discipline of rest

The first Saturday I tried it, I made it until about nine in the morning.

I had told myself the night before that this day would be different. I would not open my laptop. I would not check the notifications stacking up from the project, would not scroll through the messages I had already seen twice. I had said these things before, of course. But this time I meant them.

By nine, I was sitting at the kitchen table with my coffee gone cold, watching my phone face-down on the counter. It was there, just there, and it seemed to be humming slightly - the way a thing hums when you are trying very hard not to think about it.

I turned it over. Just to check.

I have done this enough times now to know something about myself: I am a person who has learned to measure worth by output. Not a failing, exactly, just a shape I have taken from the work, the way water takes the shape of what holds it. And the Sabbath - if I want to use that word, and I think I do - the Sabbath asks me to take a different shape for one day.

What I did not expect was how anxious stillness could feel. Not boredom, exactly, but something more exposed. As though busyness had been, among other things, a form of shelter.

I have been trying this practice for several months now, in a halting way. Some weeks I hold it. Some weeks I fold it into something useful and call that rest. But on the weeks I actually keep it, something happens that I cannot fully explain and do not want to reduce: the rest of the week moves differently. The clarity that arrived out of nowhere on a Tuesday morning, the decision I had been circling that finally became obvious - I have started to wonder whether these were partly the product of that day. Not earned, exactly. Received.

There is an old phrase about the day of rest being a foretaste - a rehearsal for something larger, a kind of trust that the world does not actually require you to hold it together. I am not sure I believe that yet, not fully. But I notice I am less certain it is wrong than I used to be.

What would it mean to stop, not because you have finished, but because the stopping itself is the practice? And what might return to you in the days after, if you let it?

Marking a long-serving colleague's departure

The sticky note was still on his monitor when we cleaned out his desk. It read, in Howard’s careful block letters: “Friday - budget meeting. Bring the Q3 numbers and the old contract from ‘08.” He had written it three weeks before his last day, not knowing then that it would be the last note he ever posted there, and it struck me that this was exactly who he was: always leaning a little forward, holding both the present need and the history of the thing.

I have been turning that note over since.

There is a kind of faithfulness that does not announce itself. It shows up in the way a person answers the same question for the fourteenth time without any trace of impatience. It shows up in the handwritten annotation on a folder that nobody asked for but that someone, years later, will find exactly when they need it. Howard practiced this faithfulness the way a craftsman keeps a bench: not showy, not self-promotional, just maintained, day after day, because it was right to do so.

He was in the same role for twenty-six years. I have heard people mention this as if it were a kind of stillness, a stasis. But watch what happens in a room when a crisis arrives and someone turns, without thinking, toward a particular corner. That turning is itself a kind of testimony. You do not turn toward stillness. You turn toward bedrock.

Several people who work here - people who now lead teams, who now know what they are doing - might pause, if they were honest, and name the afternoon Howard sat with them and did not rush, did not give the quick answer, but asked the better question. They carry something of him. They may not always know it.

What do we do with a person who gave without keeping score? We are left, when they go, holding something we did not know we were receiving.

Howard’s last day was a Wednesday. Someone brought a cake. He laughed at the card. He shook hands at the door and then he was gone, and the hallway was a little different than it had been, in a way that is hard to name precisely but that everyone who was there will recognize when they try.

I wonder if you know who your Howard is. I wonder if you have told them.

Marking the team shipping a hard, long project

Priya did not say anything when the second launch date slipped. She closed her laptop, stood at the window for a moment, and came back to the keyboard. The team had been watching.

That is the kind of thing you do not forget. Not the date itself, not the fourteen months, not the two near-misses that took weeks off the schedule. The thing you carry is smaller and harder to name: that small returning. The choosing to come back.

For over a year, this team carried two systems. The old checkout flow served customers every day, every peak hour, while an entirely new one was built alongside it. There is a word for this kind of work: hidden. Not secret - but hidden. Below the waterline. The kind of labor that keeps the ship moving precisely because it does not call attention to itself. You cannot point to it easily from outside. The dashboard stays green, which looks like nothing happening, which is exactly what the work required.

I have been thinking about what it costs to do invisible work well. The patience it demands is not the ordinary patience of waiting out a delay. It is something more active than that - the patience of holding tension without releasing it. Of saying, every morning, both systems matter today. The old one because people are depending on it now. The new one because the old one’s days are numbered and you are the ones doing the counting.

You know something about this. If you have ever maintained a thing while building its replacement, you know how often that task goes unnamed. How often the hard call - the one that protects what is running even when everything in you wants to move faster - happens in a meeting no one outside the team will ever read the notes from.

The final rollout held under peak load. This is the sentence that matters. Not the slipped dates, not the near-misses - though both are part of the story. Customers moved through checkout. The door opened.

What good infrastructure looks like from outside is nothing. A path that is clear. The problem that does not happen.

Whether we know how to see that - whether we have learned to read the absence as evidence of what the team carried - is the question I keep returning to. Priya came back to the keyboard. Marcus stayed on the dashboards until the small hours. Fourteen months of both systems, two near-misses, a final rollout that held.

That is what it means to finish something hard.

Arguing a public position on return-to-office

The last time I saw Marcus was in a parking lot. We had both walked out of the building at the same time, and we stood there for a few minutes, neither of us quite ready to go. He mentioned something offhand about a project, I said something back, and somewhere in that conversation - I still cannot say exactly when - we solved a problem that had been sitting in the ticket tracker for three weeks.

We would not have done that on a video call. Not because video calls are inferior. But because we were not trying to solve anything. We were just standing there, in the late afternoon, letting the day unspool.

I have been turning that moment over since the return-to-office debates began in earnest at our company. The office-first voices say it plainly: you cannot manufacture serendipity. The fully-remote voices say it just as plainly: you cannot manufacture focus in an open floor plan, and you cannot hire Marcus at all if he lives in a city where you have no office.

Both of these things are true. I have felt the truth of both on the same afternoon.

What I am less sure of is whether we are asking the right question when we ask “office or not.” The choice presented as binary carries a hidden assumption: that one default fits the work, the worker, and the relationship at the same time. It rarely does.

There was a retreat I attended years ago where the leader said something I have never quite shaken: “Community is not the same as proximity. But proximity is one of the few environments where community has room to surprise you.” She was talking about something else entirely. But I find myself returning to it when I sit in this debate.

The hybrid model I am asking us to consider is not a compromise in the sense of everyone getting less than they wanted. It is closer to a rhythm - a few shared anchor days where we can be surprised by a parking lot conversation, and the rest of the week given back to the kind of focused work that asks the world to leave you alone for a while.

The office-first leaders will hear this as surrender. The fully-remote advocates will hear it as encroachment. I understand both readings. But I wonder if what we are really negotiating is not a policy at all. We are negotiating what kind of organization we want to be, and what kinds of moments we are willing to protect.

What would it mean for us to choose a rhythm rather than a rule?

Announcing a new product to an outside audience

There is a particular kind of stillness that settles after a long sprint review. The retro is done. The tickets are closed. And then someone asks, quietly, what should we work on next - and the room goes soft with that question.

You have been here. You know the way the roadmap decision feels in that moment: like reaching for something solid and finding instead a collection of signals. The feedback that arrived through the chat tool, three weeks ago. The complaints scattered through the support queue. The note in the shared spreadsheet that someone marked “to review” and then never quite returned to. Each one partial. None of them arranged into anything you could hold up and say with confidence: this is what we heard, and this is what it means.

What you are sitting with in that moment is not only a process problem. It is something closer to a question of faithfulness. Your customers have spent the small currency of their attention on typing out what matters to them. They have trusted that you were listening. The scattered state of the feedback is a kind of debt - not a moral failure, but an incompleteness. You gathered the signal. You have not yet honored it by making it coherent.

This is the moment Tidemark was made for.

It gathers the feedback from wherever it already lives - the queue, the spreadsheet, the notes from conversations - and surfaces what rises to the top across all of it. It produces a ranked, shareable roadmap: not a project for next quarter, but something you could put in front of a stakeholder, or a customer, today. It is not a replacement for judgment. It is a structure that makes sure the signal does not stay silent just because it arrived in pieces, on different days, through different channels.

Tidemark opens to anyone next week. If you have been sitting with that quiet question at the end of your sprints - the one that keeps returning, the one your team already knows how to ask - you are the person it was built for.

The question is a good one. It means you are listening. The next question is: what would it mean to answer it?

A personal year-end reckoning with a difficult year

There is a notebook on my desk - one of those thick ones with the elastic band across the cover. I bought it at the start of the year for a project I was certain would work. The name “Aldercroft Initiative” is written inside the front cover in my own hand, and I keep meaning to put it away somewhere. I have not put it away.

That project ran for nine months. Marcus, who led alongside me, worked in a way I have rarely experienced with another person - finishing each other’s thinking, catching each other’s mistakes, caring about the same things. By November, the people who had commissioned the work decided to discontinue it. Not because the work was bad. Because the conditions had changed.

That is the kind of ending that leaves you with nothing particular to argue against.

What I did not expect was how loss compounds. By the time the project ended, Marcus and I had also grown distant in a way I cannot fully account for. I want to assign fault, and some of it is mine - I became absorbed, I made assumptions, I let silences go longer than I should have. But I cannot draw a clean line. I do not think clean lines are usually available.

There is an old prayer that speaks of asking for “the grace to see clearly what is, and the courage to stop calling it something else.” I have been sitting with both of those tasks, and I am not done with either. The year was hard. The relationships it touched were real. The grief is real too.

I wanted, by now, to be able to say: this is what the year meant. This is what it taught me. The loss was preparation for something. But I do not believe that right now. And I think it matters not to pretend.

What I am choosing to carry forward is harder to name. Not a lesson. More like a posture - a decision to let what mattered, matter, without needing it to have earned its cost in some way I can calculate. I gave myself to something that genuinely mattered. That it ended badly does not make it false. It was real. I was present for it.

I wonder if you have been in a year like this. Whether you, too, are sitting with something that did not resolve - something you cannot quite put away. I do not have easy comfort to offer. But I notice I still have the notebook. And I notice I have not crossed the name out.

Appears in diff-pairs

• devotional-reflection vs classical-argument (varies style)