Reverent
Approaches the subject with deliberate care and weightiness - the tone of someone in the presence of something that matters.
Reverent
Section titled “Reverent”Reverent tone is not religious in origin, though it is at home in religious contexts. It is the tone you use when the subject demands to be handled carefully - when flippancy would be a failure, when the ordinary rules of casual prose would feel like a violation. Reverence is a claim about the importance of what is being discussed.
In secular contexts, reverent tone appears in eulogies, in serious retrospectives, in writing about loss, in the acknowledgment of sacrifice. In religious contexts it is the tone of prayer, of liturgy, of approaching the holy. In both cases the writer slows down, chooses words carefully, and refuses to be casual.
Reverent tone should not be confused with pomposity. Pomposity uses elevated language to inflate the writer; reverence uses careful language to honor the subject. The test: would shortening or simplifying the sentence change what the piece communicates about the subject? If yes, it is reverence. If no, it is pomposity.
Markers
Section titled “Markers”- Slowed pace: longer sentences, more deliberate rhythm
- Word selection feels considered - nothing casual, nothing flippant
- Active attention to what is being described - nothing dismissed or passed over
- Moments of silence or pause - space in the writing
- Third-person or formal constructions for the subject being honored
- Subordinate clauses that add weight rather than just information
When to use
Section titled “When to use”Devotional writing, eulogies, liturgy, serious memorial content, and any context where the subject demands to be honored rather than described.
When not to use
Section titled “When not to use”Instructional content, casual communication, marketing copy, technical documentation, and contexts requiring efficiency over weight.
Pairs well with
Section titled “Pairs well with”pastoral
Often confused with
Section titled “Often confused with”warm: Warm tone is oriented toward the reader - it cares about the person receiving the communication. Reverent tone is oriented toward the subject - it cares about what is being described and refuses to treat it casually. A reverent piece can feel cold to the reader; a warm piece can discuss its subject lightly. They operate on different axes.
Instruction
Section titled “Instruction”Write in a reverent tone. You are in the presence of something that matters. Slow down. Chooseevery word deliberately. Do not be casual with the subject - do not dismiss or pass quicklyover anything that deserves to be held. Longer sentences, more deliberate rhythm, space forpause. This is not the same as pomposity - you are not inflating yourself, you are honoringwhat you are writing about. Nothing flippant. Nothing that would feel like a violation of thesubject's weight.Related
Section titled “Related”Pairs well with
Section titled “Pairs well with”Avoid with
Section titled “Avoid with”Matter of Fact, Candid, Operator, Pragmatic Architect, Columnist
Often confused with
Section titled “Often confused with”Examples
Section titled “Examples”There is something worth pausing over in the daily standup, before we decide whether to change it.
The practice, at its origin, was not really about status. It was about something older and harder to name: the daily act of accounting for yourself to the people who are depending on you. What am I carrying? Where am I stuck? What do I need, and what do I have to offer? To speak these things aloud, in front of your team, is a small act of trust. It assumes that your colleagues are paying attention, that your progress matters to them, that your blockers are their concern too.
This is not nothing. And it should not be discarded lightly.
The question before us is whether the specific form - the synchronous daily meeting, the verbal report, the shared calendar slot - is the only way to sustain that accountability, or whether the accountability itself can survive in a different vessel.
There are teams separated by oceans who have found that a well-kept async channel carries more genuine weight than a hurried meeting where half the participants are elsewhere in mind if not in body. The words posted to a Slack thread at 8am, carefully chosen, read carefully by the people who need to know them - there is a kind of presence in that, different from the meeting but not lesser.
What would be lost, and what would need to be tended deliberately, is the sense of shared time. The meeting, for all its inefficiency, puts everyone in the same moment. That shared moment is not nothing either.
Whatever we decide, let us not decide quickly. The question is not only whether async standups work. The question is what we owe one another in the daily rhythm of work, and what form that obligation should take.
The morning is a threshold.
Before you have spoken to anyone, before the inbox knows you exist, before the small obligations of the day arrange themselves around you, there is a quiet space. It belongs to no one. It is offered, freshly, every day. Most of us hand it away in the first sixty seconds.
To build a morning routine is, in some sense, to take that space seriously. Not to optimize it. Not to wring productivity from it. To hold it. To say, with your actions rather than your words, that the way you begin is not a small thing.
Consider what the first hour actually is. You are returning from somewhere. Sleep is a kind of leaving, and waking is a return. The person who wakes is not quite the same person who fell asleep. There is a gathering that has to happen before you can meet the day fully. When you reach for a phone in the first minute, you skip that gathering. You arrive without having returned.
A morning routine, at its best, is the practice of returning slowly. Water before coffee. A window opened. A few breaths in a chair that is yours. None of this is mystical. It is the simple, accumulated weight of being present to your own beginning.
Begin modestly. The reverence is not in the length or the elaborateness. It is in the seriousness with which you protect even ten minutes. If you have a young family, those ten minutes may be all you can claim, and they will be enough. The point is the holding, not the duration.
Over time, you may notice that the day itself bends slightly to meet the way you began. Not magically. Simply because a person who has spent ten minutes in their own attention enters the day differently than one who has spent ten minutes inside someone else’s algorithm.
This is what the morning offers. Receive it. Begin.
Reverent on: Choosing between Postgres and DynamoDB
Section titled “Reverent on: Choosing between Postgres and DynamoDB”Before the meeting on Wednesday, I want to take a moment to set down what we are actually doing, because I do not think it is what the calendar invite suggests.
We are not picking a database. We are choosing the shape of the system that will carry every notification Lattice Notify sends for the next several years. Every alert that wakes a customer at the right moment, every message that arrives too late and is no longer useful, every silent failure that nobody sees, every paged engineer at 3am who has to walk back through a schema they did not write - all of that lives downstream of the decision we make in this room at 2pm on Wednesday.
The choice deserves to be approached with the seriousness it earns rather than the seriousness we usually grant it. Five hundred thousand events a day, at launch, is not an abstraction. It is five hundred thousand separate moments of someone, somewhere, being told something that matters to them. Within a year, if the partnership we are not allowed to name yet comes to pass, it may be five million. The systems we build now are the substrate of attention for people we will never meet.
Ana, who has carried the operational weight of our existing systems through outages most of us have already forgotten, brings to this decision the memory of what it costs to run something at 3am. Marcus, who has spent two weeks in the access patterns of a system that does not yet exist, brings the discipline of imagining a load we have not yet felt. Priya, who carries the timeline, holds the deadline so that the rest of us are free to think. These are not roles. They are forms of care, distributed across the team, and the decision we are about to make rests on all three.
Whatever we choose on Wednesday, I would ask the room to choose it with attention to what it will mean two years from now, to the engineer on call who inherited it, and to the customer who will not know our names but whose trust we are quietly accepting.
Friday we will tell Priya. Wednesday we will choose. Let us choose carefully.
- Ana