Following Jesus ✝️𓅦𓅦𓅦

The Case for a Conservative Bitcoin Client

You Don’t Rise Into Clarity, You Build Into It

Clarity is not discovered in abstraction. It is formed through the act of building—over time, through resistance, iteration, and commitment.

Building Without Applause

The absence of recognition is not a signal to stop. It is often the condition required to build something that lasts.

Building Is a Form of Stewardship

Building is not just creation—it is stewardship. It reflects how we manage time, responsibility, and what has been entrusted to us.

Why is a literal interpretation of Genesis Important? Part 6: Repost

How our understanding of Genesis affects our understanding of the rest of Scripture

Sabbath Is Not a Break. It’s Alignment.

Sabbath is not a recovery mechanism for exhaustion—it is a return to alignment with God as the true source. This article explores how rest reframes work, exposes hidden dependencies, and reshapes the way we build, write, and live.

You Cannot Build What You Refuse to Leave

Sabbath reveals whether we are building in trust or in control. This article explores how our attachment to work exposes hidden dependencies, and why true durability requires the ability to step away.

🔒 Book 2 - Building Local-First Systems - Chap. 9 - Separation of Authoring and Distribution

Most systems tightly couple the act of creating content with the act of publishing it. This creates dependency on networks, platforms, and infrastructure at the moment of creation. Local-first systems must separate these concerns. This chapter defines the distinction between authoring and distribution and explains how decoupling them enables durability, flexibility, and true sovereignty.

🔒 Book 2 - Building Local-First Systems - Chap. 8 - Identity as a First-Class Primitive

Most systems treat identity as an afterthought — something layered on top of functionality through accounts and authentication. Local-first systems cannot. Identity must be foundational, shaping how data is created, signed, verified, and distributed. This chapter defines identity as a first-class primitive and outlines the design implications of building systems around it.

🔒 Book 2 - Building Local-First Systems - Chap 7 - Determinism Over Dynamism

Local-first systems prioritize determinism — predictable, reproducible behavior — over dynamic, server-driven state. This chapter explains why determinism is essential for trust, recoverability, and durability, and how it shapes system design choices around state, execution, and synchronization.

🔒 Book 2 - Building Local-First Systems - Chap 5 - Why SaaS Became the Default

Software-as-a-Service did not become dominant because it was inherently better for users. It became the default because it aligned with the economic incentives of companies and the operational realities of the web. This chapter explores the forces that led to SaaS dominance and why those forces continue to shape modern software architecture.

🔒 Book 2 - Building Local-First Systems - Chap 4 - Data Ownership vs Data Access

Ownership is often confused with visibility. Many systems allow users to see and interact with their data, but stop short of granting true control over it. This chapter clarifies the distinction between owning data and merely accessing it, and explains why local-first systems must prioritize ownership at the structural level.

🔒 Book 2 - Building Local-First Systems - Chap 3 Authority vs Access

Modern software gives users access to data without granting authority over it. This distinction is subtle but foundational. This chapter explores how systems can feel usable and even empowering while still being controlled elsewhere — and why true local-first design requires shifting from access-based models to authority-based systems.

🔒 Book 2 - Building Local-First Systems - Chap 2 - The Illusion of 'Offline Support'

Many applications claim to support offline usage, but what they actually provide is temporary caching layered on top of a fundamentally network-dependent system. This chapter examines why most “offline modes” fail under real-world conditions and clarifies the difference between cache-based resilience and true local-first architecture.

🔒 Book 2 - Building Local-First Systems - Chap 1 - What Is Local-First, Really?

Local-first is often reduced to “apps that work offline.” That definition is incomplete. Local-first is about authority — where the system of record lives, who controls it, and what persists when the network disappears. This chapter reframes local-first as a shift from access-based systems to authority-based systems.

"There is mourning, and there is rejoicing, all the way through Lent" Wednesday of Laetare 2026

There is mourning, and there is rejoicing. Both. All the way through Lent. Not mourning for six weeks and then a gasp of relief on Easter morning. Both. The question is where you are looking. Look at yourself, and you can only mourn. Look at Him — and rejoicing is already there underneath everything, because of what He is doing.

Why is a literal interpretation of Genesis Important? Part 5: Repost

Using what the Bible says about itself to defend a literal understanding of Genesis 1-11.

Quiet Completion vs Public Validation

This piece contrasts the internal act of finishing meaningful work with the external desire for validation, and why the former must come first.

Systems That Outlast Attention

Attention is fleeting, but systems endure. This article reflects on the difference between producing content for visibility and building structures that persist beyond the moment.

Finishing Without Applause

What does it mean to complete something without recognition? This piece explores the discipline of finishing work in silence, where validation is absent and conviction becomes the only guide.