# Fardin Iqbal — Complete Site Content > This document contains the full content of fardiniqbal.com, optimized for LLM consumption. For a curated summary, see /llms.txt. For a one-page profile, see /profile.md. --- ## About Full-stack software engineer based in New York. Finishing B.S. Computer Science at Stony Brook University (May 2026). First-generation college student selected for the Bottom Line Scholars program — a six-year program that bets on first-generation students and invests in their success from enrollment through career. Previously attended The Bronx High School of Science. BJJ club treasurer and assistant coach — taught no-gi classes for thirty-plus students. Sole developer for Big Minds Tiny Hands, a pediatric therapy staffing agency. Six production applications serving four agencies across New York's Early Intervention market. Replaced three enterprise platforms, saving $5,100 every month. Coursework: Systems Fundamentals I, Systems Fundamentals II, Computer Security Fundamentals, Web Security, Offensive Security, Data Structures, Programming Abstractions, Software Development, Software Engineering, Theory of Computation, Analysis of Algorithms, Computer Networks, Data Science, Linear Algebra, Probability & Statistics ## Experience ### Software Engineer — Big Minds Tiny Hands / Tiny Platforms **Contract** | New York, NY | Dec 2025 - Present Sole developer for a pediatric therapy agency’s entire technology stack. Six production applications serving four agencies across New York’s Early Intervention market. Every line of code is mine; every deployment, every user-facing bug, every three-AM alert. - Replaced three enterprise platforms, saving the agency $5,100 every month - Tiny Time Keeper: 5,692 employee-hours tracked, 33 employees, 742 shifts, 537 automated tests - Tiny Steps CMS: 42 users across 4 agencies, 205 patients, $45K invoiced, 2,375 test cases - Tiny Thoughts: 37 users, 22,940+ discrete trials, 877 commits. Replaced $3K/mo Rethink BA - Built shared infrastructure across all apps — a component library, validators, and configuration packages that keep six codebases consistent - HIPAA-compliant from the foundation: row-level security, AES-256-GCM encryption, audit trails, credential lockout, SSN encryption at rest **Tech:** Next.js 16, Rails 8.1, PostgreSQL, Convex, Better Auth, Stripe, Drizzle, Vercel, Fly.io ### Cyber Security Intern — New York City Housing Authority **Internship** | Hybrid, New York, NY | Jun 2025 - Jan 2026 One of two interns selected for cybersecurity at the largest public housing authority in North America — responsible for the digital safety of infrastructure that serves four hundred thousand New Yorkers. - Monitored and investigated security events across Splunk and CrowdStrike Falcon - Assisted in incident response — triage, threat analysis, and remediation - Reviewed vulnerability scan data and learned to prioritize risk by impact, not severity score - Worked across endpoint protection, data loss prevention, and security control implementation **Tech:** Splunk, CrowdStrike Falcon, Veracode, Zscaler, Defender XDR ### Design & Construction Technology Intern — Beyer Blinder Belle **Internship** | New York, NY | Jun 2024 - Aug 2024 Replaced fragile automation — Power Automate flows and Excel macros — with Python scripts that still run daily, a year after my internship ended. - Built Python automation for BIM file management with a centralized Tkinter interface - Automated execution via Windows Task Scheduler with logging, retries, and failure alerts - Built SQLite storage and PowerBI dashboards for monitoring file system health - Documented to PEP8. Still generating ROI eighteen months later. **Tech:** Python, SQLite, PowerBI, Tkinter ### Marketing Intern — The Hardy Group **Internship** | New York, NY | Oct 2023 - Dec 2023 Migrated a CRM from Salesforce to Airtable and built the data entry protocols the team still uses. **Tech:** Salesforce, Airtable ### Web Developer / Team Lead — International Socioeconomics Laboratory **Remote** | Remote | Sep 2021 - Aug 2022 Led teams of ten students in building websites from scratch. Taught people to code who had never written a line — which taught me that explaining is the deepest form of understanding. - Led ten-person teams through full website builds - Taught teammates to write their first HTML, CSS, and JavaScript **Tech:** HTML, CSS, JavaScript ## All Projects ### Tiny Thoughts — Replaced $3,000/mo Rethink BA **Category:** Production Healthcare | **Year:** 2026 | [Live](https://tiny-thoughts.fly.dev) | [Case Study](https://fardiniqbal.com/work/tiny-thoughts) Clinical data collection for ABA therapists — the people who teach children with autism through structured repetition. Therapists record trials on tablets in noisy classrooms, so every touch target is 140px wide and every interaction forgives imprecision. The mastery engine watches the data and tells the therapist when a child is ready to move forward. **Tech:** Rails 8.1, PostgreSQL, Turbo, Stimulus, Tailwind v4, Fly.io **Metrics:** Users: 37, Trials Recorded: 22,940+, Children Managed: 79, LOC: 86K ### Tiny Steps CMS — Replaced $1,700/mo ProviderSoft **Category:** Production Healthcare | **Year:** 2026 | [Live](https://tiny-steps-cms.fly.dev) | [Case Study](https://fardiniqbal.com/work/tiny-steps) Practice management for four home health agencies in New York. Therapists document visits on their phones. Supervisors cosign remotely. The system tracks sixty credential types and locks anyone out the instant a critical one expires — before an auditor ever has to ask. **Tech:** Next.js 16, Neon PostgreSQL, Drizzle, next-auth v5, Fly.io **Metrics:** Users: 42, Patients: 205, Invoiced: $45K+, LOC: 99K ### Tiny Time Keeper — Replaced $400/mo WorkEasy — built in 2 days **Category:** Production Healthcare | **Year:** 2026 | [Live](https://tinytimekeeper.com) | [Case Study](https://fardiniqbal.com/work/tiny-time-keeper) Time tracking built in two days because the agency needed it yesterday. Employees clock in on a wall-mounted iPad. Managers see who’s working in real time. Timesheets generate themselves. Usage grew 2.4x in fourteen weeks because it just works. **Tech:** Next.js 16, Convex, Better Auth, Stripe, Playwright, Vercel **Metrics:** Hours Tracked: 5,692, Employees: 33, Tests: 537, Deploy Success: 97% ### Tiny Solutions — Early Intervention case management **Category:** Production Healthcare | **Year:** 2026 Case management for Early Intervention — the pipeline from referral to active caseload. Kanban intake, child records with ICD-10 codes, sibling linking, referral staging, and consent document storage. Auto-saves on blur so nothing is lost mid-workflow. **Tech:** Next.js 16, Convex, Better Auth, Bun, Zod 4 ### AI Email Scraper — Saves 20+ hours/month of manual data entry **Category:** AI & Automation | **Year:** 2026 | [GitHub](https://github.com/FardinIqbal/BigMindsTinyHandsEmailScraper) Every five minutes, this system reads the agency’s inbox, understands the referral buried inside each email, and writes structured data to a spreadsheet. What used to take someone four hours a day now takes fifteen minutes of review. **Tech:** Express.js, Gemini 2.5 Flash, Microsoft Graph API, Render **Metrics:** Referrals/mo: ~150, Time Saved: 20+ hrs/mo, Infra Cost: $0/mo ### TinyToes Auditor — On-device AI, zero PHI exposure **Category:** AI & Automation | **Year:** 2026 A clinical document validator that runs a 3.8-billion-parameter AI model entirely in the browser. No data leaves the device — ever. Therapists upload PDFs and the system checks dates, terminology, contacts, and template compliance without a single byte touching the cloud. **Tech:** Next.js 16, WebLLM, WebGPU, pdfjs-dist, Framer Motion ### Prometheus AI — Personal AI infrastructure **Category:** AI & Automation | **Year:** 2025 | [GitHub](https://github.com/FardinIqbal/prometheus) My personal AI infrastructure — thirty-plus custom skills for research, code review, self-optimization, and investigative journalism. A system with memory, with specialized capabilities, and with a feedback loop that genuinely improves the more I use it. **Tech:** Claude Code, TypeScript, MCP Servers, Notion API ### VocaLIFT — Voice-first iOS workout tracker **Category:** Full-Stack | **Year:** 2026 A workout tracker you use with your voice. Tap the mic, say what you did, see it logged in under five seconds. All transcription happens on-device — zero cloud cost, zero data exposure. Detects personal records automatically and generates shareable cards. **Tech:** SwiftUI, WhisperKit, GPT-4o-mini, Supabase, RevenueCat ### Civica — Your government, explained **Category:** Full-Stack | **Year:** 2026 Type your address, see every official who represents you — from city council to Congress. Track bills across fifty states. Follow the money through campaign finance, PAC contributions, and lobbying disclosures. **Tech:** Next.js 16, React 19, Congress.gov API, Google Civic API, Open States, FEC API, Federal Register API ### LocalElo — Competitive ranking for BJJ academies **Category:** Full-Stack | **Year:** 2026 | [GitHub](https://github.com/FardinIqbal/localelo) A ranking system for local BJJ academies, because knowing who’s actually the best on the mat shouldn’t require a tournament. Glicko-2 ratings update after every match. Every academy keeps its own leaderboard. **Tech:** Next.js 15, PostgreSQL, Drizzle, tRPC, Clerk ### GLIMPSE — JWST spectroscopy visualizer **Category:** Full-Stack | **Year:** 2026 Interactive visualization of James Webb Space Telescope data — the light that passes through exoplanet atmospheres and tells us what they’re made of. Transmission spectra, time series heatmaps, molecular overlays for water, carbon dioxide, methane, sulfur dioxide. **Tech:** Next.js 16, FastAPI, astropy, Canvas API ### MazeWar Game Server — Multi-threaded real-time combat in C **Category:** Systems Programming | **Year:** 2025 | [GitHub](https://github.com/FardinIqbal/concurrent-network-game-server) A multi-threaded game server in C where players hunt each other through a maze with lasers. Thread-safe, memory-leak-free, built from raw TCP sockets and POSIX primitives. The kind of project that teaches you what the machine is actually doing. **Tech:** C, POSIX Threads, TCP Sockets, Valgrind ### Dynamic Memory Allocator — Custom malloc/free/realloc from scratch **Category:** Systems Programming | **Year:** 2025 | [GitHub](https://github.com/FardinIqbal/dynamic-memory-allocator) A custom malloc implementation — the thing every C programmer should build once to understand what happens when you ask for memory. Segregated free lists, coalescing, alignment, and corruption detection through header obfuscation. **Tech:** C, x86-64, POSIX ### POSIX Print Spooler — Job scheduler with signal handling **Category:** Systems Programming | **Year:** 2025 | [GitHub](https://github.com/FardinIqbal/posix-printer-spooler) A job scheduler built entirely from POSIX system calls — fork, exec, pipe, dup2, and signal handlers. Process creation, suspension, resumption, and cleanup, all managed by hand. **Tech:** C, POSIX, Unix IPC, Signal Handling ### OpenStreetMap PBF Parser — Protocol Buffers from scratch, no libraries **Category:** Systems Programming | **Year:** 2025 | [GitHub](https://github.com/FardinIqbal/openstreetmap-pbf-parser) A Protocol Buffers parser built without any protobuf library. Varint decoding, zig-zag encoding, delta compression, zlib decompression — all from scratch. The best way to understand a format is to read it byte by byte. **Tech:** C, Protocol Buffers, zlib ### VulnSocial — Intentionally vulnerable PHP social network for web-security research **Category:** Security | **Year:** 2026 | [GitHub](https://github.com/FardinIqbal/vulnsocial) | [Case Study](https://fardiniqbal.com/work/vulnsocial) A deliberately broken Twitter clone in PHP 8.2 + MySQL 8.4, packaged as a two-container Docker stack. Three textbook web bugs — UNION-based SQL injection in login and search, stored XSS in the post timeline, and a CSRF defense that collapses once the XSS lands — sit inside an otherwise well-defended baseline so the breakage is targeted rather than ambient. A 150-line Python driver runs the full chain end to end: register an attacker, log in as admin via a SQLi UNION whose synthetic row carries a known bcrypt hash, exfiltrate every (username, hash) pair, then plant stored XSS that issues authenticated friend-requests on any viewer’s behalf. **Tech:** PHP 8.2, MySQL 8.4, Apache, Docker Compose, mysqli, Python, Bootstrap 4 ### Argus — Passive network sniffer with deep packet inspection **Category:** Security | **Year:** 2026 | [GitHub](https://github.com/FardinIqbal/argus) A passive network sniffer that detects HTTP, TLS, and DNS on any port through raw byte inspection — not port-number guessing. Extracts TLS SNI with a three-tier fallback parser, identifies automation tools like curl and wget, and flags internal infrastructure hostnames. Built for my offensive security course, but the kind of tool you'd actually use on an engagement. **Tech:** Python, Scapy, cryptography ### tcpscan — SYN scanner with 6-type service fingerprinting **Category:** Security | **Year:** 2026 | [GitHub](https://github.com/FardinIqbal/tcpscan) A TCP SYN scanner that goes beyond open/closed. After the initial scan, it probes each open port with an ordered sequence that correctly distinguishes TLS from plain TCP, extracts service banners, and pulls TLS certificate CNs with a dual-parser fallback. The probe ordering is the interesting part — it solves the ambiguity that trips up naive scanners. **Tech:** Python, Scapy, cryptography ### x86 Exploit Lab — Buffer overflow exploitation research **Category:** Security | **Year:** 2026 | [GitHub](https://github.com/FardinIqbal/x86-exploit-lab) A complete exploit chain on x86-64 Linux: a vulnerable C target, a 272-byte payload constructor, and 23 bytes of shellcode that spawns a root shell. Runs in an isolated QEMU VM with ASLR, DEP, and stack canaries disabled for controlled experimentation. Includes a full defense analysis of every modern memory protection and why each one exists. **Tech:** C, x86-64 Assembly, GCC, GDB, QEMU ### NetSec Toolkit — TLS analysis, scanning, and PDF reporting **Category:** Security | **Year:** 2026 | [GitHub](https://github.com/FardinIqbal/netsec-toolkit) A network security analysis suite: TLS certificate analyzer that catches expired certs, self-signed certs, hostname mismatches, and outdated protocol versions. ICMP ping with TTL exploration for path mapping. TCP SYN port scanner. Generates professional PDF reports with tables and findings. Validated against badssl.com endpoints. **Tech:** Python, Scapy, cryptography, fpdf2 ### Secure Vault — AES-128 GCM encrypted password manager **Category:** Security | **Year:** 2026 | [GitHub](https://github.com/FardinIqbal/secure-vault) An authenticated encryption password manager built from cryptographic primitives. AES-128 GCM for confidentiality and integrity in one pass. scrypt key derivation resistant to GPU brute-force. SHA-256 hashed vault filenames so no plaintext usernames touch disk. Random nonce per save so identical vaults produce different ciphertext. 27-test suite covering tamper detection, multi-user isolation, and wrong-password rejection. **Tech:** Python, pycryptodome, AES-GCM, scrypt ### HTTP Server & Proxy — Raw sockets, no libraries **Category:** Systems Programming | **Year:** 2025 An HTTP server and caching proxy built from raw sockets — no frameworks, no libraries, just the RFC and a socket. Handles concurrent requests and caches responses. **Tech:** Python, Socket Programming, HTTP/1.1 ### MLX Audio Transcriber — On-device ML, Apple Silicon native **Category:** AI & Automation | **Year:** 2026 A batch audio transcriber running Whisper models natively on Apple Silicon through the MLX framework. Zero cloud dependency — everything stays on the machine. I use it daily for meetings, podcasts, and voice notes. **Tech:** Python, MLX-Whisper, Apple Silicon ### Box Office Revenue Predictor — ~100 engineered features, R² = 0.77 **Category:** Machine Learning | **Year:** 2025 | [GitHub](https://github.com/FardinIqbal/movie-revenue-prediction) Can you predict how much a movie will make from its metadata alone? With a hundred engineered features and the right model, you get surprisingly close. Random Forest with five-fold cross-validation, R² = 0.77. **Tech:** Python, Scikit-learn, Pandas, NumPy ### Energy Demand Forecasting — Weather-driven residential modeling **Category:** Machine Learning | **Year:** 2025 | [GitHub](https://github.com/FardinIqbal/energy-usage-prediction-weather) A year of five-minute weather snapshots mapped against residential energy consumption. The question: can weather predict how much electricity a home will use? Linear regression for daily demand, logistic regression for peak-load classification, appliance-level profiling. **Tech:** Python, Pandas, Scikit-learn, Matplotlib ## Case Studies (Full Detail) ### Tiny Thoughts — ABA Clinical Data Collection Platform **Feb 2026 - Present** | [Live](https://tiny-thoughts.fly.dev) **Key Metric:** 22,940+ discrete trials recorded in 9 weeks #### Problem The agency was paying three thousand dollars a month for Rethink BA — an enterprise platform built for large clinics, not a small agency where therapists work in living rooms and basements. Trial recording was buried under menus. Mastery tracking lived in spreadsheets. The software was getting in the way of the children. They needed something built for how they actually work: a therapist, a tablet, a child, and nothing between them but one tap. #### Solution I built the replacement in seventy-one days. The core insight came from watching therapists work: they’re holding a child’s attention with one hand and tapping a screen with the other. Every interaction must be fast, forgiving, and reachable by a thumb. So I designed 140-pixel touch targets and a recording flow that a therapist can operate while a child is climbing on their lap. The mastery engine is the centerpiece — it watches the data and tells the therapist when a child is ready to advance. Configurable criteria across three program types: how many sessions, what accuracy threshold, at which prompt level. When a child meets mastery, the system recommends a phase change. When a child regresses, it catches that too. Clinical parameters cascade through three layers — organization defaults, template overrides, per-child customizations — so a supervising clinician can set policy once and still fine-tune individual cases. #### Architecture **Pure TypeScript Domain Kernel:** Mastery scoring, phase-change logic, and config resolution are isolated in a pure TS layer with no framework dependencies. Property-tested with fast-check to verify correctness across thousands of random inputs. **PostgreSQL RLS for Multi-Tenant Isolation:** Every clinical table enforces Row Level Security. Therapists can only see children on their caseload. BCBAs see their supervisees. Admins see their organization. Zero data leakage by design. **PWA with Offline Trial Recording:** Serwist service worker caches the app shell and enables offline trial recording. Therapists in basements or rural areas with spotty connectivity can record data that syncs when they're back online. **OKLCH Algorithmic Design System:** 3 CSS variables generate the entire light/dark palette using OKLCH color space. Surfaces, semantic colors, and chart colors are all derived mathematically — no manual color picking. #### Metrics - Active Users: 37 - Trials Recorded: 22,940+ - Children Managed: 79 - Mastery Events: 129 - Trial Growth (9 weeks): 537x - Lines of Code: 86K - Commits in 71 Days: 877 - Enterprise Cost Replaced: $3K/mo #### Lessons Learned - Domain complexity is where the real engineering happens. The mastery algorithm went through four iterations before it matched how clinicians actually think about progress. I spent more time in meetings with therapists than writing code — and that was the right ratio. - Property-based testing caught edge cases I never would have imagined — partial sessions, conflicting config cascades, boundary prompt levels. The domain kernel has zero known bugs. I trust it more than most things I’ve built. - When clinical decisions depend on your data, ‘good enough’ is not a concept that applies. Every trial, every mastery event, every phase change must be auditable and correct. Children’s progress is measured against what this system records. **Tech:** Rails 8.1, PostgreSQL 16 (Neon), Turbo + Stimulus, Tailwind CSS v4, Solid Queue, Upstash Redis, Serwist (PWA), Fly.io ### Tiny Steps CMS — HIPAA-Compliant Practice Management **Jan 2026 - Present** | [Live](https://tiny-steps-cms.fly.dev) **Key Metric:** $45K+ invoiced through the system #### Problem Four home health agencies were about to commit to seventeen hundred dollars a month for ProviderSoft. Too many menus. Too many features they’d never use. Meanwhile, therapists were driving paper notes to the office. Supervisors were cosigning forms by hand. Credential expirations lived in a spreadsheet — and when one lapsed, nobody knew until the audit. They needed software that understood how home health therapy actually works — therapists in the field, documenting visits on their phones between appointments, supervisors reviewing from wherever they are, and someone watching every credential expiration before it becomes a liability. #### Solution Built in two months. Forty-two users across four agencies. The key decision: make the most common workflow — documenting a visit — as fast as physically possible. Open the app, select the patient, fill in the details, sign with your finger, submit. Under three minutes, including the signature. The credential lockout is the piece I’m proudest of. Sixty-plus credential types per therapist, four of them critical. If a critical credential expires, the system locks the therapist out. No grace period. No workaround. It sounds aggressive — until you realize the alternative is a therapist working with an expired medical clearance and the agency bearing the liability. The billing pipeline follows every dollar from authorization to visit documentation to invoice generation to payment collection. Nothing falls through the cracks because the system won’t let it. #### Architecture **Agency-Polymorphic PDF Pipeline:** 13 fillable PDF templates across 4 agencies, each with different layouts and requirements. pdf-lib fills fields programmatically and stamps drawn signatures at computed coordinates. @react-pdf/renderer generates custom reports. **Supervision Routing State Machine:** Every visit note flows through a state machine: pending_review → co_signed → ready_for_billing. Supervisors are notified automatically. The system enforces that no visit reaches billing without proper cosignature. **Credential Lockout Engine:** PostgreSQL functions evaluate credential expiry on every login. 4 critical credential types trigger immediate account lockout. Non-critical expirations generate warnings. All evaluated server-side — no client-side bypass possible. **SSN Encryption at Rest:** AES-256-GCM encryption for all SSN fields. Role-scoped queries ensure that only authorized roles can decrypt. Full HIPAA audit trail with 5,361+ logged events. #### Metrics - Active Users: 42 - Patients Managed: 205 - Invoiced: $45K+ - Credentials Tracked: 1,433 - Agencies Served: 4 - Lines of Code: 99K - Commits in 89 Days: 515 - Enterprise Cost Replaced: $1.7K/mo #### Lessons Learned - Multi-tenant healthcare is hard because no two agencies work the same way. Different forms, different billing cycles, different field positions on every PDF. The polymorphic document pipeline — thirteen templates across four agencies, each with its own layout — was the most complex thing I’ve ever built. - Before this system, expired credentials were caught during audits — after the damage was already done. Automated lockout is the only guarantee. Not a single therapist has worked with expired credentials since launch. That’s the metric I care about most. - Every form submission is validated on both client and server. Every error state is explicitly typed. One hundred sixty-five server actions, zero runtime type errors in production. The type system is the safety net under the safety net. **Tech:** Next.js 16, React 19, Neon PostgreSQL (HIPAA BAA), Drizzle ORM, next-auth v5, Tigris S3, pdf-lib, @react-pdf/renderer, Sentry, Fly.io ### Tiny Time Keeper — Multi-Tenant Employee Time Tracking **Jan 2026 - Present** | [Live](https://tinytimekeeper.com) **Key Metric:** 2 days from zero to production #### Problem The agency was paying four hundred dollars a month for a time tracking system that was buggy, slow, and indifferent to their feature requests. Staff still clocked in on paper. Admins still calculated hours in spreadsheets. Payroll was a weekly ordeal that no one looked forward to. They needed it yesterday. I built it in two days. #### Solution Employees walk in and tap their PIN on a wall-mounted iPad. That’s it — they’re clocked in. The admin dashboard updates instantly. Managers see who’s working, who’s late, and who didn’t show up, all from their phone, in real time. Usage grew 2.4x in fourteen weeks — thirty-two shifts per week to seventy-seven — because the system simply works. Timesheets generate themselves. Managers approve with one tap. Payroll exports match the agency’s existing spreadsheet format. Zero retraining. Zero resistance. Built for multi-tenancy from day one. Any business can sign up, create an organization, and onboard their team. Stripe handles the billing lifecycle end to end. Infrastructure cost: zero dollars a month. The entire system runs on Vercel’s free tier. #### Architecture **Real-Time with Convex:** 749 runtime validators, real-time WebSocket subscriptions, and automated cron jobs. The live attendance board updates instantly when an employee clocks in — no polling, no refresh. **iPad Kiosk with Device Authorization:** 15 authorized devices. Unauthorized devices are blocked before the PIN pad even appears. Each PIN attempt is logged. 111 blocked unauthorized attempts caught in production. **Automated Alert System:** Missing punch detection runs every 15 minutes. Late arrival alerts, no-show alerts, overtime warnings. 422 auto-generated alerts in 14 weeks of production use. **Full Stripe Lifecycle:** Subscription billing with trial periods, grace periods, past-due handling, cancellation, and org freezing. Webhooks handle all state transitions server-side. #### Metrics - Hours Tracked: 5,692 - Active Employees: 33 - Shifts Logged: 742 - Automated Tests: 537 - Deploy Success Rate: 97% - Features Shipped: 48 - Infrastructure Cost: $0/mo - Enterprise Cost Replaced: $400/mo #### Lessons Learned - Speed matters more than perfection — when someone needs a working system, they don’t need your ideal architecture. I shipped in two days. The architecture evolved over fourteen weeks of real usage. But the initial sprint proved the only thing that matters: it works, and no one has lost a single hour of data. - Real-time updates changed how managers interact with time tracking entirely. They went from checking attendance once a day to monitoring it continuously — not because I told them to, but because the live board is simply more useful than a report. - Five hundred thirty-seven tests on a time tracking app might seem excessive. It isn’t. Payroll errors cost real money and real trust. Every edge case — timezone transitions, overnight shifts, missed punches, overlapping events — is tested. Because the one time your system miscalculates someone’s hours is the last time they trust it. **Tech:** Next.js 16, React 19, Convex, Better Auth, Stripe, Resend, Playwright, Vitest, Framer Motion, Vercel ## Blog Posts (Full Content) ### The Correspondence: On Truth, Untruth, and Whether It Matters **Published:** 2026-04-13 | **Read Time:** 22 min read | **Tags:** philosophy, faith, correspondence Two friends write letters to each other about God, reason, and whether a conversation is possible when one of them prefers untruth to truth. --- Seneca wrote letters to Lucilius about death and the proper use of a life. He did not write them because Lucilius needed the advice. He wrote them because the act of addressing another human being, even across distance, even across disagreement, forced a precision that thinking alone never could. The sentence you write for someone else must be truer than the sentence you think for yourself, because someone else will hold it up to the light and see where it bends. Kierkegaard wrote to himself under invented names about faith and dread and the impossibility of being understood. Rilke wrote to a young poet about solitude, and the young poet kept those letters for the rest of his life because nothing anyone said to him in person ever came as close to the truth as those pages did. This essay is about a correspondence between two friends. Not philosophers. Not writers by trade. Two college students in New York who grew up in the same borough, sat in the same classrooms, and arrived at the same impossible questions from directions so different that when they finally tried to speak honestly to each other about what they believed, the conversation collapsed under the weight of its own sincerity. One of them believes that truth, even when it burns, even when it leaves you with nothing, is the only ground that will hold. The other suspects that a carefully built shelter, even one constructed from beautiful lies, might be more livable than the open field of bare reality, and that this preference is not weakness but a different kind of courage. They wrote letters to each other in April of 2026. I am one of them. --- ## I. The Boulder Ali wrote first. He opened with an accusation, gentle but unmistakable: that I had not written to him, and that my silence was either cowardice or something worse than cowardice, a kind of forgetting that is itself a choice. He was right about this, though not in the way he imagined. What followed was one of the most honest things I have ever read another person write. Ali described a boulder. Not a real boulder, but the one every thinking person carries in their mind: the great task, the thing that must be moved, the work that would define you if only you could bring yourself to begin it. He confessed that his deepest flaw was believing that understanding the boulder was the same as moving it. That if he could only measure its weight, map its surface, calculate the angle of the hill, then surely the pushing would follow naturally. Preparation as a form of permission. Study as a substitute for risk. But he saw through his own trick, and this is what made the letter extraordinary. He named the mechanism plainly: the analysis was not preparation. It was fear wearing the costume of diligence. Every hour spent studying the rock was an hour spent not climbing the hill, and the reason he would not climb was not that the summit was too far but that failure at the summit would force him to revise the story he told himself about who he was. "If I fail," he wrote, "I would have to reevaluate myself within my own personal hierarchy." I have read that sentence more times than I can count, and it does not soften. The boulder is not the obstacle. The self-concept is the obstacle. We do not avoid the work because it is hard. We avoid it because completing it, or failing at it, would give us information about ourselves that we are not ready to receive. And so we study. We prepare. We refine our plans. We do everything except the thing itself, and we call this wisdom. Camus told us that Sisyphus was happy. That the absurd hero finds meaning in the eternal push, the stone rolling back, the climb beginning again. But Ali was describing something Camus never addressed: the man who stands at the bottom of the hill and never pushes at all. Not because he has accepted absurdity, but because he has not yet found the courage to encounter it. Sisyphus at least knows the weight of his stone. Ali was describing the terror of discovering what your stone weighs. And then, in the most quietly devastating turn of the letter, Ali did the very thing he said he could not do. He pushed. Not the boulder. The pen. He wrote a letter he had not planned, using words he had not rehearsed, to a friend who had given him every reason to believe the effort was wasted. The letter was its own refutation. The man who declared himself paralyzed was, in the act of declaring it, moving. --- ## II. The Silence and the Circle I did not write back for weeks. Not out of cruelty or neglect, but out of a resignation so deep it had stopped feeling like resignation and started feeling like clarity. I had spent years having the same conversation. About God, about faith, about the strange architecture of belief. With friends I loved, people whose intelligence I respected in every other domain, I would sit across a table or speak late into the night, reaching for the same thing: understanding. And more selfishly, that rarer thing, the experience of being understood. The conversations always ended in the same place. My friends would acknowledge that faith, by its own definition, transcends logic. That God is a paradox. That belief cannot be derived from reason, and that this is precisely what makes it belief rather than calculation. I understood this. I even found it beautiful, in the way that Kierkegaard found it beautiful when he wrote about Abraham on the mountain, the knight of faith who cannot explain his obedience and does not try. But then something would happen that I could never move past. Having established that their faith rests on a foundation that reason cannot touch, they would proceed to reason about everything else. One friend, after telling me that God is beyond logic, explained in the next breath that he had chosen Islam specifically because, after researching all the major religions, it was the most logically consistent. The most *reasonable*. "My faith is built on a foundation that transcends reason. But I chose this particular faith because it made the most sense." I sat with this for a long time. Not because it was wrong, exactly, but because it revealed something about the relationship between what we say we believe and how we actually navigate the world. The foundation is beyond reason, but the house built on that foundation is constructed with meticulous rationality. The leap of faith is taken once, in the dark, and then never again. Everything after the leap is careful, measured, sensible. Kierkegaard would have wept. I had this conversation with every close friend I had. Separately, in different rooms, in different seasons. And every time, with the eerie precision of a recurring dream, the conversation arrived at the same impasse. Reason would carry us to the edge, and then my friends would step off the cliff into faith, and then, standing in midair, they would resume reasoning as though the ground were still beneath them. And I, who had refused to step, would stand on the edge calling after them, and my voice would not reach. Ali was different. Or so I thought. We spoke during spring break, and for the first hour it was the most alive I had felt in a conversation in months. He was not defending a position. He was exploring one. He was willing to follow an argument even when it turned against him. And then he said something that stopped me: that truth is not necessarily greater than untruth. That a constructed paradise might be preferable to bare reality. That untruth, held with sufficient conviction, might be more livable than truth held with trembling hands. I recognized the argument. Nietzsche had made it, in the fourth section of *Beyond Good and Evil*: "The falseness of a judgment is for us not necessarily an objection to a judgment." The question is not whether a belief is true but whether it serves life. I knew the philosophy. But hearing it from a friend, spoken not as theory but as personal creed, something in me went cold. What is the point of a dialectic between two people if one of them holds that truth and falsehood are interchangeable? How can you build a conversation on a foundation that one party has already declared optional? I sat in silence on the phone for what felt like minutes, not because I had lost the argument, but because I was deciding whether the argument was worth continuing. Whether any conversation with a person who prefers beautiful illusions to harsh realities could ever arrive anywhere other than where it started. I decided not. I had decided this before, many times, with many people. And each time the decision carried the same quiet grief: one more person with whom the deepest conversation was impossible. Then we hung up the phone. And we both opened Instagram. Separately, in our separate rooms, in our separate silences. And we scrolled. --- ## III. The Feed and the Forgetting I almost did not mention this. It seemed incidental, a footnote, the kind of detail you leave out when you are trying to build an argument about truth and meaning and the examined life. Two friends hang up after a philosophical conversation and browse social media. So what. Everyone does this. But the more I thought about it, the more I realized that this was not a footnote. This was the thesis. This was the only thing in the entire correspondence that neither of us could argue away or reframe or philosophize into something more flattering. We had just spent two hours in the most serious conversation either of us had attempted in months. We had talked about God and Nietzsche and the nature of truth and whether dialectic is possible between minds that hold different axioms. We had been, for a brief and precious window, the people we wished we were: thoughtful, earnest, unafraid to follow a question wherever it led. And then the conversation ended, and within thirty seconds, both of us were watching strangers perform dances for algorithmic approval. Every word we had said about truth dissolved. Every position we had defended evaporated. Not because the positions were wrong, but because they were not strong enough to survive the transition from conversation to silence. The feed appeared, and we obeyed it. Not reluctantly. Not after a struggle. Instantly. The way a muscle obeys a nerve. Kierkegaard wrote in *The Sickness Unto Death* that the most common form of despair is not the dramatic kind, not the anguish of a man who knows he is drowning, but the quiet kind: the despair of a man who does not know he is in despair at all. The man who is busy, comfortable, entertained. Who has never sat in a room alone with the question of what he truly believes and followed it all the way down to whatever waits at the bottom. That man, Kierkegaard says, is the most lost of all, because he does not know he is lost, and so he never searches for the way back. The doom scrolling was that despair. Not a dramatic failure. Not a moment of weakness. A revelation. A mirror held up to everything we had just said, showing us that we did not believe it. Or if we believed it, we did not believe it enough for it to matter more than the next fifteen seconds of content. This is what happens, I think, when you allow truth to become negotiable. When you hold it loosely, the way Ali suggested, as one option among several. You are left without an anchor, and the first current that comes along carries you wherever it wants. The Algorithm does not need you to disbelieve in truth. It only needs you to be indifferent to it for thirty seconds at a time. And thirty seconds, repeated across a lifetime, is all it takes. --- ## IV. Why I Wrote Anyway So if I decided that the conversation was futile, if I concluded that dialectic with a man who prefers untruth to truth leads nowhere, why did I write? The honest answer is selfish. I wrote for myself. To see my own thoughts on a page, to discover whether they held together outside my head, to submit them to the only test that matters: the test of being read by someone who will not let you get away with imprecision. But there is another answer, one I did not expect and still do not fully understand. I had been reading Kierkegaard. Not about God, exactly, but about faith in the broader sense: the willingness to commit to something you cannot justify, something that reason alone would never produce. The leap. The knight of faith who lives in the finite world, who looks exactly like everyone else, but who has made a movement of the spirit that is invisible from the outside and incomprehensible from within. Everyone in my life who believed in God had said the same thing Kierkegaard said. But none of them said it the way he did. None of them made me feel, even for a moment, that the leap might be something other than surrender. Kierkegaard made it sound like the hardest thing a human being could do. Not the abandonment of reason, but its completion. The point at which reason recognizes its own limit and, rather than stopping, steps beyond itself into something it cannot name. In that moment of sympathy, or weakness, I wrote to Ali. I do not know if we will continue. I hope we do. Not because I believe we will resolve the questions we are circling. They have been circling for thousands of years, and minds far greater than ours have broken against them. I hope we continue because the act of writing to someone who disagrees with you, genuinely, from the foundations up, is one of the last honest things left in a world that has optimized honesty out of most of its conversations. When you speak, you perform. When you argue, you defend. But when you sit down to write a letter to someone you respect, knowing they will weigh each sentence against their own experience, knowing they will find the places where your logic bends and your courage fails, you cannot hide. The letter will betray you. Not cruelly, but completely. It will show you what you actually believe, as distinct from what you wish you believed, what sounds impressive, what wins arguments. The letter strips the walls from the building and shows the structure underneath, and if the structure is sound, it stands, and if it is not, it falls, and either way, you learn something that no amount of thinking in private could have taught you. Ali asked me to write. If not to him, then to myself. This is both. --- *Sources and influences: Kierkegaard, Fear and Trembling (1843) and The Sickness Unto Death (1849). Nietzsche, Beyond Good and Evil, section 4: "The falseness of a judgment is for us not necessarily an objection to a judgment." Seneca, Letters to Lucilius, Letter 40, on the relationship between writing and friendship. Plato, Phaedrus, 274b-278b, on the inferiority of writing to living dialogue. Camus, The Myth of Sisyphus (1942), on the absurd hero who knows his task and chooses it anyway.* --- ### The Cost of Looking Closely **Published:** 2026-04-10 | **Read Time:** 14 min read | **Tags:** philosophy, work, meaning There is a room I keep returning to in my memory, and every time I enter it, someone has already ruined it by mentioning the future. --- There are so many nights when the room is perfect. Everyone is laughing. Nobody is performing. The food on the table is something someone's mother made, and nobody has checked their phone in twenty minutes, and the conversation is about absolutely nothing, which is to say it is about everything that actually matters: the fact that we are here, together, young, alive, and not yet dissolved into the roles the world has picked out for us. I live for those rooms. I think most people do, whether they admit it or not. The room before someone brings up the future. Then someone brings up the future. Jobs. Careers. LinkedIn. An interview next week. A recruiter who reached out. And I feel something drain out of my body, not anxiety, something lower than anxiety, something that doesn't sit in the chest but leaves through the feet, as though whatever was keeping me upright just decided to stop. I go silent. Not physically. I'm still sitting there. My face is still arranged in something approximating attention. But I have left. I have been pulled backward into a place I cannot name, a place where every word being spoken sounds like a lock clicking shut. I find nothing in the world more meaningless to talk about. And the reason it fills me with such dread is not that work is hard, or that interviews are stressful, or that the job market is cruel. It is that we are all forced to spend the majority of our waking lives doing something none of us want to do, and we sit there discussing the details of our captivity as though choosing the right cell will set us free. Five minutes ago we were laughing about nothing, and that nothing was worth more than every job listing on the entire internet. --- ## The Room Before It Changed Montaigne wrote, in his essays, that we are never at home; we are always beyond ourselves. Fear, desire, hope: they push us toward the future and steal from us the feeling and consideration of what is. He wrote that in the sixteenth century, in a tower in Bordeaux, surrounded by books and silence and the slow French countryside, and it is as true now as it was then. Maybe truer, because at least Montaigne could retreat to his tower. We carry the future in our pockets. It vibrates against our legs every forty-five seconds. I think about that every time the room changes. Five minutes ago we were home. We were right here, inside the moment, inside each other's company, inside the kind of presence that can't be manufactured or optimized or scheduled into a calendar. And then someone checked their phone, or someone mentioned a deadline, and now we are all somewhere else. Somewhere in the future. Somewhere we don't want to be. Rehearsing for lives none of us chose. The speed of the transition is what disturbs me most. It is not gradual. It is not a slow drift from presence to absence. It is instantaneous, like a light being switched off. One second the room is alive, and the next second everyone is performing a version of themselves they learned from watching adults who were also performing. The ambitious one talks about opportunities. The practical one talks about salary ranges. The anxious one talks about backup plans. And I sit there watching the room I loved disappear behind a wall of language that means nothing to anyone in it, and I cannot figure out how to say what I want to say without sounding like I have lost my mind. What I want to say is: we were just happy. Can we go back. Can we stay there. Can we talk about nothing for the rest of the night and let the future arrive on its own schedule instead of dragging it into every conversation like a guest nobody invited. But I never say it. I just go quiet. And eventually someone asks if I'm okay, and I say I'm fine, and we move on. --- ## The Testimony of the Body We spent four years in college studying things we did not want to learn. The people who say they did are lying to themselves, or at the very least, me and my friends are, because we skipped roughly eighty percent of our lectures across four years of university. Eighty percent. That is not a rough patch. That is not a bad semester. That is your body screaming the truth for four consecutive years while your mouth keeps saying something different. It does not matter what we say we believe. It matters what we do. Our alarms went off and we turned them off. Our legs carried us past the lecture hall. Our bodies voted, every single morning, against the life we keep telling everyone we are building. That is not laziness. That is testimony. That is the truest language we have, the language of action, saying plainly what the language of speech is too polite or too frightened to say: I do not want this. I have never wanted this. I am doing it because I was told I had no other option, and I believed it, and now I am four years deep and the only thing I have learned is how to pretend I chose this. Whenever I bring any of this up, whenever I try to get my friends to look at the gap between what we say and what we actually do, they nod. They agree. They exhale this long, heavy sigh that I have heard so many times now it has become its own language. The sigh that means: I know. I know. There is nothing we can do. And then they go right back to talking about the same things they do not care about but have been trained to act like they care about. They spend their free hours rehearsing for the same cage they just described to me in perfect detail. Nothing changes. Nothing ever changes. They just sigh and keep building the walls from the inside. --- ## Closed Loops I worked at a coffee shop once. I will be honest: it was easier and more enjoyable than what I do now as a software developer. The work was monotonous, yes, the same drinks over and over. But you can learn to love repetition. There is something almost meditative about it, your hands moving without your mind needing to direct them, the body falling into a rhythm that asks nothing of the soul. Except the process was so refined and systematized that it killed even that small grace. Every motion was optimized for speed, not craft. And the product I was making was, to put it plainly, poison. Ultraprocessed sugar and chemicals engineered to create dependency and leave people feeling worse than before they walked in. They came every morning, the same tired faces, the same orders, the same eyes that did not quite focus until the caffeine hit. And they handed me their money for the thing that was slowly hollowing them out, and I handed them the cup, and they drank it in their cars on the way to jobs they hated, and they earned just enough to come back tomorrow and buy more. A closed loop. People hurting each other in the most ordinary, polite way. And my hands were in it. Seneca wrote in On the Shortness of Life that it is not that we have a short time to live, but that we waste much of it. Life is long enough, he said, and a sufficiently generous amount has been given to us for the highest achievements if it were all well invested. But when it is squandered in heedless luxury and spent on no good activity, we are forced at last by death's final constraint to realize it has passed away before we knew it was passing. I read that when I was nineteen, and I thought: he is right. He is exactly right. And then I went to work the next morning and made someone a caramel swirl iced coffee and tried not to think about it. That is the cruelty of understanding without action. You see the cage clearly. You can describe its dimensions, its materials, the precise angle of the light that comes through its bars. And then you sit down inside it and wait for your shift to end. Because seeing the cage does not open the cage. Knowing you are wasting your life does not stop you from wasting it. It just makes the wasting hurt more. --- ## The Elegant Bandaid What really makes me angry, what I genuinely cannot get past, is the architecture of modern work itself. Not just that work is tedious or underpaid or soul-crushing, but that so much of it is dedicated to solving problems that should not exist in the first place. Why would I want to build an app that helps people manage their insurance cases more efficiently when the entire reason the existing software is so terrible is that the system was designed by people who will never have to use it? I am solving a symptom. I am patching a patch. I am building a tool to navigate a broken system instead of asking why the system is broken. And the answer to why is always the same: because the brokenness is profitable. The dysfunction is the business model. And I am supposed to call my bandaid disruption. That is what most of the technology industry is, if we are being honest. Not innovation. Just increasingly elegant ways to cope with increasingly unnecessary problems. An entire economy built on managing the damage of other economies. We build apps to help people find affordable healthcare in a country that made healthcare unaffordable on purpose. We build platforms to help workers find gigs in a labor market that destroyed stable employment by design. We build meditation apps so people can recover from the anxiety created by the other apps we built. The whole thing is a serpent eating its own tail, and we call it progress, and we give each other awards for the most aesthetically pleasing segment of tail. --- ## The Question Nobody Answers When I say all of this to my friends, they ask the obvious question: What is the alternative? You have to work. What else are you going to do? And they are right to ask. Because I do not have one. They say you need money. I say for what. They say to travel, to live, to experience things. And I say: but think about it. You are working all these years for a few moments of joy that you cannot even fully enjoy because you know you will have to go back in a couple of days. The joy has a return ticket. It comes with an expiration date stapled to the itinerary. And also: why do you need the money? If you look honestly at all these experiences you are saving up for, what do they actually give you? You want to travel the world. Why? So you can talk to different cultures. Eat different foods. Experience nature. But why can you not do that where you are? Why does transcendence require a plane ticket? What is it about a foreign country that your own neighborhood could not give you if you looked at it with even half the openness you would bring to a place you have never been? If the end goal is joy, then why do you care how you arrive at it? A feeling does not know what you paid for it. It does not check your coordinates. If joy is the destination, then any road that takes you there is the right road, and you do not need the expensive one. My friends look at me like I am being naive when I say these things. And maybe I am. But the math does not work, and everyone knows it. We spend our twenties earning the right to our thirties. Our thirties earning our forties. And somewhere in the middle, the thing we were saving up for becomes the thing we no longer have the body or the energy or the friendships to enjoy. That math has never worked. Not for us. Not for our parents. Not for their parents. Not for anyone in the history of working. And we all know this, and we keep going anyway, because the only thing scarier than admitting the math is broken is having nothing to replace it with. --- ## The Weight That Stays Now here is where I have to be honest in a way that actually costs me something. I say all of these things, but I myself have not been able to let go. I still need money. I still live inside the system I am criticizing. And the real reason I cannot leave, the one that sits heaviest, is my parents. I want to give them a good life. But their version of a good life and mine are not the same. They are still inside the framework of the system. Stability, security, a respectable title, a career their community can nod at. And I understand why. They came from a place where not having these things did not mean discomfort; it meant danger. Their caution is not conservatism. It is scar tissue. It is the residue of a life harder than anything I have known. I have no right to dismiss what they want. They earned their expectations through a kind of suffering I have only heard about in stories told over dinner, the kind of stories that get quieter as they approach the worst parts. My father asked me last week how the applications were going. He put his fork down when he said it, which means he had been thinking about it all day, carrying the question around like something fragile, waiting for the right moment to set it on the table between us. I said fine. He mentioned someone else's son who just got an offer at a company whose name I recognized. We both knew what he was really saying. And I sat there trying to figure out how to tell him that his version of a good life and mine are not the same without it sounding like I was throwing away everything he sacrificed for me. I could not figure it out. So I said fine again. And we kept eating. Seneca, in the same text, wrote about the old man on his deathbed who realizes he has been preparing to live rather than living. That the years slipped away not in dramatic catastrophe but in incremental postponement, each day traded for the promise of a better day that never arrived. I think about my father when I read that passage. Not because he is dying, but because I can see the same arithmetic working its way through my own life, and I do not know how to stop it without breaking the people I love. If I leave the cave, I cannot leave without them. I do not want to. I want to take them with me. But they do not see the sunlight the way I do. They see exposure. They see risk. They see the open field where anything can happen, and they remember a time when anything meant the worst thing. --- ## The Hypocrite's Prayer And here is the part that really twists the knife. If I cannot do any of this myself, if I cannot follow my own philosophy, why am I telling my friends to? Why do I go quiet in that room like it means something? I wake up past noon. I reach for my phone and lose hours to nothing. I skip training. I stay up until four in the morning and promise myself tomorrow will be different in the exact same voice I have been using every night for three years. And it never is. The voice does not change. The promise does not change. The morning does not change. Only the date changes, and even that starts to blur. So either I do not really believe what I say, which makes me a hypocrite. Or I do believe it and I cannot act on it, which makes me a coward. I am not sure which is worse. Probably the second. At least the first one has an excuse. Thoreau wrote that the mass of men lead lives of quiet desperation. What is called resignation is confirmed desperation. He wrote that nearly two hundred years ago, sitting by a pond in Massachusetts, living deliberately, stripping life down to its essentials to see whether he could learn what it had to teach. The only thing that has changed since Thoreau is that we have rebranded the desperation as hustle culture and the resignation as a career path and somehow made the cage aspirational. We have turned quiet desperation into a LinkedIn post with a blue checkmark and fourteen thousand reactions. But I refuse to believe this is all there is. I refuse to accept that the highest use of the one life I get is to spend it solving problems that should not exist, building tools to navigate systems that were broken on purpose, trading the years where I am most alive for the promise that someday, eventually, I will get to enjoy being tired. That is not a life. That is a very long, very respectable way to disappear. --- ## The Room I Keep Returning To I do not know what the alternative looks like. Not fully. Not in the way that would satisfy anyone who asks the question seriously. I cannot draw a map from here to there. I cannot promise it works. I cannot even promise I will follow through, given my record, given the distance between what I say at two in the morning and what I do at two in the afternoon. But I know the dread I feel in that room when someone brings up careers is not the disease. The dread is the diagnosis. It is the last honest part of me, the part that still refuses to play along, the part that hears the word "opportunity" and translates it correctly as "a new way to spend your life on something you do not care about." And every time I go quiet, it is not because I have nothing to say. It is because what I have to say is so much larger than the room, and I do not know how to get it out without sounding ungrateful or naive or broken, so I just hold it, like something too hot to set down and too heavy to carry. Montaigne left public life at thirty-eight. He locked himself in a tower with his books and spent twenty years writing what he called essais, which just means attempts. Tries. He did not have answers. He had questions and the willingness to sit with them for as long as they needed. He failed at most of what he tried to figure out. But the trying was the living. The attempt was the point. The tower was not a retreat from the world; it was the first honest confrontation with it. I do not have a tower. I have a laptop and a bedroom that needs cleaning. But the principle might be the same. I think about that room a lot. The one from before someone checked their phone. The laughing. The nothing we were talking about that meant everything. The warmth that no one had to manufacture or earn or schedule. I think that is what I am trying to protect. Not a lifestyle. Not a philosophy. Not a five-year plan. Just that. The room before it changed. The twenty minutes where nobody was a candidate and everybody was a person and the only thing that mattered was that we were there, and that we were there together, and that the food was good, and that the laughter came easily, and that no one had anywhere else to be. I do not know if you can build a life around twenty minutes. But I would rather spend my years trying than spend them building someone else's cage and calling it a career. Thoreau went to the woods because he wished to live deliberately, to front only the essential facts of life, and see if he could not learn what it had to teach, and not, when he came to die, discover that he had not lived. I have not gone to the woods. I have not gone anywhere. But I am beginning to suspect that the essential facts of life are not waiting in some future I have to earn. They were in the room the whole time, in the twenty minutes before somebody changed the subject, in the laughter that required nothing, in the silence that followed when everyone was content and no one needed to fill it. Tomorrow I am going to do one thing I actually want to do. And if nothing falls apart, I will do it again the day after. And again. Until either something real stops me or a life starts to take shape around the trying. That is not a plan. But I think it might be the start of one. --- *Sources and influences: Montaigne, Essays (1580), on the habit of living beyond ourselves. Seneca, On the Shortness of Life (49 AD), on squandered time and postponed living. Thoreau, Walden (1854), on quiet desperation and deliberate life. Marcus Aurelius, Meditations, on the sufficiency of the inner life.* --- ### Systems Are Lossy Compression **Published:** 2026-03-15 | **Read Time:** 17 min read | **Tags:** philosophy, systems, freedom Every system you adopt is a compression algorithm applied to reality. Compression always loses data. The question is what you are willing to lose. --- It was a Sunday afternoon in February, and I was 250 lines deep into an architectural plan for my life. Teams, initiatives, cycles, labels, daily workflows, weekly reviews, quarterly retrospectives. I had color-coded categories for fitness, philosophy, career, relationships, side projects. I had velocity metrics. I was going to track exactly how I wanted to get to where I wanted to get to. The whole thing hummed with the quiet satisfaction of a cathedral under construction. I could feel the order settling over the chaos of my week like a weighted blanket. This was it. This was the system that would finally make me the person I kept meaning to become. By Tuesday, it was dead. Not dramatically. Not with a declaration or a crisis. It just stopped mattering. I woke up, opened the app, looked at the elaborate scaffolding I had built, and felt nothing. Not resistance, exactly. More like the recognition you get when you see a photograph of a meal you ate last week: yes, that happened. It is no longer relevant. I closed the app and went about my day the way I always do, which is to say, by doing whatever felt most alive in that moment, following the thread of whatever problem or obsession had its hooks in me, ignoring everything I had meticulously planned. Two days. Two hundred and fifty lines of infrastructure. And the thing that killed it was not laziness or lack of discipline. It was something more unsettling. I had built the system, and in the act of building it, I had already received everything it had to offer. The system was never going to organize my life. The system was itself the experience of feeling organized. Once that feeling faded, the system had no remaining function. It was scaffolding with no building inside. This has happened to me more times than I can count. The oscillation is predictable: feel unstructured, build elaborate system, feel productive, realize the system is not doing the work, abandon system, feel unstructured again. Lather, rinse, repeat. For a long time I thought this was a personal failing, some deficiency of follow-through or attention. But I have come to believe it is something else entirely. I think I keep building systems and abandoning them because I can feel, at some inarticulate level, that every system is a lie. A useful lie, maybe. A necessary lie, sometimes. But a lie nonetheless. The question I want to explore is not whether systems are good or bad. That is a boring question with a boring answer. The question is: what does every system cost you? What do you lose when you adopt one? And how would your life change if you understood, really understood, that every framework you have ever believed in is missing most of the picture? --- ## The Compression Metaphor Claude Shannon, working at Bell Labs in the late 1940s, gave us the mathematical framework for understanding information. His insight was deceptively simple: communication is the process of reducing uncertainty. Every message, every signal, every piece of data is a selection from a set of possibilities. The more possibilities you eliminate, the more information you have transmitted. But Shannon also understood something darker, something that tends to get lost when people invoke information theory at cocktail parties. There are two kinds of compression: lossless and lossy. Lossless compression preserves everything. You can compress a file and decompress it and get back exactly what you started with, bit for bit, nothing missing. Lossy compression is different. Lossy compression makes a bet. It looks at the data, decides what matters and what does not, throws away what it deems unnecessary, and gives you back something smaller, something manageable, something that looks close enough to the original that you might not notice the difference. But the difference is there. The thrown-away data is gone forever. You cannot get it back. Every photograph you have ever taken on your phone is a JPEG, which means every photograph you have ever taken is a lossy compression of what your eyes actually saw. The algorithm decided which gradations of color were imperceptible to the human eye and discarded them. The sunset you photographed last summer had thousands of subtle tonal shifts that your file deleted in the name of a manageable file size. You look at the photo and think you are looking at what happened. You are not. You are looking at what the algorithm decided was worth keeping. This is the metaphor I cannot stop thinking about, because I believe it applies to something far larger than digital photography. I believe every system humans have ever built, every framework, every ideology, every institution, every religion, every economic model, every philosophical tradition, even language itself, is a lossy compression algorithm applied to reality. Reality is the RAW file. Infinite resolution. Unlimited bandwidth. More data than any mind can hold. And so we compress. We have to. A human being standing in the middle of uncompressed reality would be paralyzed, overwhelmed, unable to act. So we build models. We create frameworks. We adopt systems. And every single one of them, without exception, throws data away. Religion compresses morality into commandments. Ten rules, or five pillars, or an eightfold path. Take the staggering complexity of human ethical life, the infinite contextual gradations of right and wrong, the way the moral weight of an action shifts depending on who is doing it and to whom and when and why, and reduce it to a list. A magnificent list, sometimes. A list that has guided billions of people through the darkness of uncertainty. But a list that, by its nature, cannot contain what it replaced. The commandment "thou shalt not kill" is a compression of a reality in which the morality of killing depends on a thousand factors the commandment cannot encode. Capitalism compresses value into price. Take everything a thing is, everything it means, everything it costs the earth and the worker and the community, and reduce it to a number. The price of a bottle of water at an airport is $6. That number has compressed into itself the aquifer depletion, the plastic manufacturing, the shipping logistics, the labor conditions, the marketing budget, the rent on the retail space, and your desperation because you are dehydrated and past security. All of that complexity, flattened into a number on a sticker. The price is not wrong, exactly. It is just lossy. It has thrown away most of the information. Academia compresses knowledge into credentials. Take everything a person knows, everything they have struggled to understand, every late night with a difficult text, every moment of genuine intellectual transformation, and reduce it to a line on a resume. Bachelor of Arts. Master of Science. PhD. The credential is a compression that allows institutions to sort people efficiently. But it has lost the actual knowledge in the process. I have met people with doctorates who have forgotten more than they remember, and I have met people with no formal education whose understanding of their domain would embarrass a tenured professor. The credential kept the label and threw away the substance. Language itself, the tool I am using right now to reach you, is perhaps the most fundamental compression of all. Alfred Korzybski spent his career trying to make people understand this. "The map is not the territory," he said, and people nodded and thought they understood, and then went right back to confusing their descriptions of reality with reality itself. Every word is a compression. The word "grief" is a container for an experience so vast, so multidimensional, so physically and psychologically and spiritually overwhelming that no word could ever hold it. But we say "grief" and we nod and we move on, as if the word were the thing. It is not. The word is the JPEG. The experience is the RAW file. And you cannot decompress the word back into the experience. --- ## The Lens You Cannot See Through Here is where it gets dangerous. When you adopt a system, a framework, a way of seeing, something subtle happens. The compression algorithm does not announce itself as a compression algorithm. It presents itself as vision. As clarity. As the way things actually are. You do not experience yourself as wearing tinted glasses. You experience the world as being the color of the tint. Jean Baudrillard understood this better than almost anyone. In "Simulacra and Simulation," he argued that our models of reality have, in many cases, replaced reality entirely. The map has not just been confused with the territory; the map has consumed the territory. We live in a world of representations so thick, so layered, so self-referential, that the original reality they were supposed to represent has become irrelevant. The simulation is more real than the real. Baudrillard called this hyperreality, and I think about it every time I watch someone check their phone to see how many steps they took on a walk they were apparently not present for. This is not an abstract philosophical problem. This is the water you are swimming in right now. Consider: a Marxist walks into a room and sees class dynamics. A Freudian walks into the same room and sees libidinal currents and defense mechanisms. An economist sees supply and demand. A therapist sees attachment styles. A sociologist sees power structures. A devout Christian sees souls in various states of grace. They are all looking at the same room. They are all seeing something real. But none of them is seeing the room. They are seeing the room through the compression algorithm they have internalized, and the algorithm, by its nature, has thrown away everything it was not designed to detect. I notice this in myself constantly. When I am deep in a Nietzsche phase, everything becomes a question of power. Who is asserting, who is submitting, whose morality is serving whose interests. When I am reading Plato, everything becomes a question of forms and ideals and the distance between the thing and its essence. When I am training jiu-jitsu, I walk through the world seeing frames and levers and balance points, reading bodies the way a musician reads a score. Each lens reveals something real. Each lens hides everything else. The insidious part is that the more sophisticated the system, the more invisible its compressions become. A crude ideology is easy to see through because it obviously does not account for everything. But a truly powerful framework, one that has been refined over centuries by brilliant minds, can feel so comprehensive that you forget it is a framework at all. You mistake the map for the territory. You confuse the compression with the original data. Nietzsche saw this with terrifying clarity. In "Beyond Good and Evil," he argued that every philosophy is a kind of involuntary autobiography, a confession of its creator's drives and prejudices dressed up in the language of universal truth. The philosopher does not discover truth. The philosopher compresses reality according to the shape of their own nature and then calls the result "the way things are." Nietzsche was honest enough to include himself in this indictment. His philosophy of the will to power was, by his own implicit admission, the compression algorithm of a man who valued strength and despised weakness. It reveals what it reveals. It hides what it hides. And this is the trap. Not that systems are wrong. They are not wrong. They are lossy. The Marxist really does see class dynamics, because class dynamics are real. The therapist really does see attachment styles, because attachment styles are real. The problem is not that the lens shows you something false. The problem is that the lens shows you something true and in doing so convinces you that what it shows is all there is. Partial truth masquerading as the whole picture. That is the most dangerous kind of distortion, because you never think to question it. --- ## The Paradox on the Mat I train Brazilian jiu-jitsu, and it has taught me more about this paradox than any book. When you start jiu-jitsu as a white belt, you have no system. You have no framework, no technique, no model. You just have your body and another body and gravity and panic. You are not free. This is important to understand. The absence of a system is not freedom. The absence of a system is drowning. You flail. You use strength where you should use leverage. You hold your breath. You make the same mistakes over and over because you do not even have the vocabulary to name what is happening to you, let alone the tools to respond to it. So you learn technique. You learn a system. You learn that when someone is in your guard, you control the distance with your knees. You learn that an armbar is not about pulling the arm but about lifting the hips. You learn that a sweep works because you remove a post while applying force in the direction of the missing support. Each technique is a compression. It takes the infinite complexity of two bodies entangled on the ground and reduces it to a set of principles: control the head, control the hips, create angles, break grips, maintain frames. And here is the paradox, the one that I think contains the answer to the question I have been circling. At the intermediate level, the system helps. It gives you a framework for reading the chaos. Where you once saw only a tangle of limbs, you now see a guard pass or a submission entry or a sweep setup. The system works. But it also constrains. You become predictable, mechanical. You execute techniques instead of responding to the person in front of you. You are doing jiu-jitsu the way a music student plays scales: correctly, competently, lifelessly. You have traded the white belt's formless panic for the blue belt's rigid competence, and neither one is freedom. But then something happens at the higher levels, something that I have seen in black belts and that I am only beginning to glimpse in myself. The system dissolves. Not because the black belt has rejected technique. Not because they have decided that systems are prisons and returned to formless flailing. The opposite. They have internalized so much technique, absorbed so many systems, drilled so many patterns, that the systems have become invisible. The techniques are no longer things they do. The techniques are things they are. And because the system has been absorbed into the body itself, the mind is free again. The black belt rolls with the spontaneity of a white belt but with the precision of someone who has ten thousand hours of encoded pattern recognition operating below conscious thought. Shunryu Suzuki, the Zen teacher, wrote about this in "Zen Mind, Beginner's Mind." He said, "In the beginner's mind there are many possibilities, but in the expert's mind there are few." This is often quoted as a cute aphorism about staying open-minded. It is not cute. It is devastating. The beginner sees everything because they have no system to filter their perception. The expert sees almost nothing because their system has become so efficient at compression that it has eliminated everything outside its parameters. The master, the true master, has somehow returned to beginner's mind, not by unlearning what they know but by learning so thoroughly that knowledge becomes transparent. They see through the system rather than with it. The compression algorithm is still running, but they can see the data it is discarding, and they can choose, moment to moment, whether to trust the compression or reach for the raw file. This is what happened to me on that Tuesday morning when I abandoned my 250-line productivity system. I was not being lazy. I was not failing to follow through. I was, at some level I could not yet articulate, recognizing that the system was showing me a compressed version of my own life and calling it the complete picture. And the compressed version, with its cycles and labels and velocity metrics, had thrown away the thing that actually makes my life work: the ability to follow what is alive, to chase the thread that pulls, to trust the animal intelligence that knows what matters before the conscious mind has finished building its spreadsheet. --- ## Becoming Who You Are Nietzsche's most famous imperative is usually translated as "become who you are." It sounds paradoxical, almost nonsensical. How can you become what you already are? But I think the paradox dissolves when you understand it through the lens of compression. You are born as the RAW file. Infinite resolution. Unlimited potential. Undifferentiated. And then the compressions begin. Your family gives you your first system: their values, their fears, their model of what a good life looks like. School gives you another: knowledge is what fits on a test. Religion gives you another, or atheism does, which is just a different compression with different losses. Your culture gives you a thousand more, so quietly that you never notice them being installed. By the time you are an adult, you are layers of compression all the way down. You do not experience yourself as wearing masks. You experience the masks as your face. "Become who you are" is the instruction to decompress. Not to reject all systems, which would be just another system, the system of anti-system, compressing reality through the filter of perpetual refusal. But to recognize, with excruciating honesty, that every system you have adopted, every framework you believe in, every lens you see through, is lossy. It has cost you something. It has thrown away data about who you are and what reality is in order to give you a manageable, actionable, navigable model. The question is not whether to use systems. You have to use systems. The white belt is not free. The person without language is not free. The person without any framework for understanding the world is not free. They are drowning in raw data, paralyzed by the infinite bandwidth of unmediated reality. You need compression to function. You need maps to navigate. You need models to decide. The question is whether you know you are using them. Korzybski spent decades trying to teach people to add the words "to me" or "as I see it" to every statement. Not as a social nicety, but as a fundamental epistemological correction. "This is a good movie" is a statement that confuses the map with the territory. "This is a good movie to me, given my particular history and aesthetic training and current emotional state" is a statement that acknowledges the compression. It is longer, uglier, less satisfying. It is also closer to the truth. Korzybski did not succeed in changing how people talk. But he was right about why they should. I think about this when I catch myself in the grip of a system. When I am deep in Nietzsche and everything becomes a power dynamic. When I am deep in productivity thinking and my life becomes a set of optimizable inputs and outputs. When I am deep in philosophy and every experience becomes raw material for an argument rather than something to be lived. In each case, the system is doing what systems do: compressing reality into something I can work with. And in each case, the system is costing me something: the parts of reality it was not designed to capture. The most dangerous moment is when I forget this. When the system becomes so familiar, so internalized, so total, that I lose the ability to see around it. When I stop being a person who uses a framework and start being a person who lives inside one. Baudrillard would say that is the moment the simulation becomes more real than the real. I would say it is the moment you mistake the JPEG for the sunset. --- ## The Resolution That Is Not a Resolution I want to offer a clean ending here. A framework for thinking about frameworks. A system for evaluating systems. But that would be exactly the kind of trap I have been describing, and I refuse to set it. So instead, here is what I have learned, provisionally, lossily, with full awareness that this too is a compression. Structure serves freedom. That is the lesson of jiu-jitsu, of music, of language, of every discipline that requires years of systematic practice before spontaneity becomes possible. You cannot be free without form. The white belt is not free. The person who rejects all systems is not liberated; they are lost. You need technique. You need vocabulary. You need frameworks. You need maps. But, and this is the part that matters, the structure is a servant, not a master. The moment the structure becomes the point, the moment you are serving the system instead of the system serving you, something has gone wrong. The productivity app that makes you feel productive without producing anything. The philosophical framework that makes you feel wise without deepening your understanding. The religious practice that makes you feel righteous without making you more compassionate. The economic model that makes you feel rational without making you more humane. In each case, the system has stopped compressing reality and started replacing it. Here is the test I have started applying, and it is the only test I trust. Can you drop the framework and still see clearly? If you removed the Marxist lens, could you still see injustice? If you removed the therapeutic vocabulary, could you still feel empathy? If you removed the religious framework, could you still act morally? If you removed the productivity system, could you still do meaningful work? If the answer is yes, the system is serving you. It is a tool you are holding. You can put it down. You can pick up a different one. You can use your bare hands. If the answer is no, if removing the framework would leave you unable to see or feel or act, then the system has consumed you. You are no longer using it. It is using you. You have become a function of the algorithm, processing reality through a compression you can no longer distinguish from the data itself. I abandoned my 250-line productivity system on a Tuesday morning, and my life did not collapse. I continued to do the work that mattered. I continued to train, to read, to write, to build, to think. The things that were real before the system remained real after it. The things that were only real inside the system vanished like morning fog. That tells me something. It tells me the system was not supporting the work. It was simulating the feeling of support. I still build systems. I still adopt frameworks. I still read philosophy and internalize its lenses and see the world through them. I am not anti-system. That would be as naive as being pro-system. I am trying, with varying degrees of success, to hold every system loosely. To remember that the map is not the territory. To remember that the JPEG has deleted colors I can no longer see. To remember that the commandment, the price tag, the credential, the diagnosis, the philosophical argument, the political ideology, the productivity framework, the training methodology, and even the sentence you are reading right now are all compressions. They are all lossy. They have all thrown something away. The question is not whether you can live without compression. You cannot. The question is whether you know what you have lost. Whether you can feel the absent data like a phantom limb. Whether you can hold your favorite framework up to the light and see the gaps in it and love it anyway, not because it is complete, but because it is yours, and it is the best compression you have found so far, and tomorrow you might find a better one. That is what I think it means to become who you are. Not to find the right system. Not to reject all systems. But to move through systems the way a black belt moves through techniques: fluidly, spontaneously, without clinging, using each one fully and then releasing it, always returning to the ground truth of your own uncompressed experience. The Sunday system was beautiful. The Tuesday abandon was wise. The oscillation is not a failure. The oscillation is the signal of a mind that refuses to mistake any compression for the whole. I do not know what the RAW file of my life looks like. I am not sure anyone ever sees theirs. But I know it is there, underneath every system I build and every system I abandon, vast and uncompressed and waiting, the territory that no map will ever fully capture. And I think that is enough. Not to see it. Just to know it is there. Just to feel the weight of everything the systems have thrown away, and to keep reaching for it, one lossy approximation at a time. --- ### An Attempt to Find the Axioms of Jiu-Jitsu **Published:** 2026-02-20 | **Read Time:** 14 min read | **Tags:** bjj, philosophy, first-principles What if grappling has first principles the way mathematics does? Not techniques, but axioms. The irreducible truths from which everything else follows. --- --- There is a moment, about forty seconds into a roll with someone better than you, when your breathing changes. Not because you are tired. Because you have run out of ideas. Your partner has collapsed your frames, flattened your hip to the mat, and threaded a knee through a gap you did not know existed. You are trying to remember a technique, some escape you drilled last Tuesday, but the weight on your chest is compressing your thoughts along with your ribs. You cannot think your way through this. The body has to answer, or nothing will. I remember the exact roll when something shifted. It was a Thursday evening, late class, and I was working from bottom against a training partner who outweighed me by thirty pounds. He passed my guard cleanly and settled into side control with the patience of a man who had nowhere else to be. I fought the crossface. I bridged. I shrimped. Nothing. Every movement I made was a word, a single disconnected word, when what I needed was a sentence. And then, without deciding to, I stopped fighting the position and started fighting the distance. I wedged a knee inside, not to escape but to create a frame. The frame bought me an inch. The inch let me turn. The turn restored my guard. I had not performed a technique. I had obeyed a principle. That night, driving home with my gi still damp, I turned the moment over in my mind. What had I actually done? Not a specific escape. Not a move with a name. I had recognized that the problem was not the position but the distance, and that controlling distance was more fundamental than any escape sequence. It was the grammar beneath the words. And I began to wonder: how many of these grammatical rules are there? How deep does it go? What if grappling, like geometry, has axioms? --- ## Why Axioms Matter In the third century BCE, Euclid sat down and performed one of the great intellectual feats in human history. He looked at the sprawling, accumulated knowledge of Greek geometry, all its theorems and constructions and proofs, and asked a radical question: what is the smallest set of truths from which all of this follows? The answer was five. Five postulates. From these, and these alone, every theorem in the *Elements* could be derived. A straight line can be drawn between any two points. A circle can be drawn with any center and radius. All right angles are equal. And so on. Five seeds from which the entire forest of Euclidean geometry grows. The elegance of this is not mathematical. It is philosophical. Euclid demonstrated that an apparently infinite domain of knowledge could be reduced to a finite set of irreducible truths. The rest is consequence. The rest is weather. If you understand the axioms, you understand the system, even the parts of it you have never seen before. I have been training Brazilian jiu-jitsu for years now, and the art often feels infinite. There are thousands of techniques. Hundreds of positions. An ever-expanding taxonomy of guards, passes, submissions, transitions, and escapes. You can spend a decade on the bottom game alone and still encounter positions you have never seen. The instructional industry is a content machine, producing new material faster than any human could absorb it. And yet, on the mat, the practitioners who move with the most clarity are not the ones who know the most techniques. They are the ones who seem to understand something underneath the techniques, something structural, something that lets them improvise in real time because they grasp the logic of the art rather than its vocabulary. So the question haunts me: can jiu-jitsu be axiomatized? Can we identify a small, finite set of principles from which the rest of the art logically follows? Not a list of tips. Not a collection of heuristics. Axioms. Truths so fundamental that denying any one of them would cause the system to collapse. I want to be precise about what I mean. An axiom is not a technique. "Armbar from closed guard" is not an axiom. It is a theorem, a specific consequence that follows from deeper truths about leverage, angle, and the structure of the human arm. An axiom is not a strategy, either. "Be on top" is a strategy, a preference that admits exceptions. An axiom is a claim about the nature of the art itself, a statement so basic that it cannot be reduced further. Position before submission. Pressure creates reaction. The body is a system of levers. These feel like candidates. Whether they hold up is what I want to find out. --- ## The Candidate Axioms ### 1. Position Before Submission This is the first thing you learn and the last thing you understand. I remember watching a blue belt roll with our instructor, a compact, quiet man who moved like water finding the lowest point in a landscape. The blue belt was hunting. Arms everywhere. Darting for necks, reaching for wrists, trying to snatch a submission from whatever position he happened to be in. The instructor simply moved through him. Not around him. Through him. He advanced position with such calm inevitability that the blue belt's attacks became irrelevant. Mount. Then back control. Then a choke that seemed to arrive as an afterthought, the way a period arrives at the end of a sentence you already understood. Position before submission means that where you are is more important than what you do. It means that the hierarchy of positions, back control above mount above side control above guard above bottom, is not a suggestion but a law. Violate it and you may still win, the way a gambler may still profit, but you are playing against the structure of the game itself. The philosophical implication cuts deep. It suggests that in any complex system, the conditions you establish matter more than the actions you take. Preparation precedes execution. Context determines outcome. Whitehead warned against "the fallacy of misplaced concreteness," the error of treating an abstraction as if it were the real thing. A submission is concrete. You can see it, feel it, tap to it. But the position that made it inevitable is abstract, a relationship of angles and weight and frames that exists as a pattern before it exists as a choke. The concreteness of the submission is a seduction. The abstraction of the position is the truth. ### 2. Pressure Creates Reaction Your body is treacherous. It will betray your strategy in service of its panic. There is a particular kind of pressure in jiu-jitsu that has no equivalent in daily life. Not pain, exactly. Compression. A good top player does not pin you to the mat. He makes the mat disappear. You cannot feel the floor beneath you because all you can feel is the weight above you, distributed with sadistic precision across your diaphragm, your face, the hinge of your jaw. And your body, that magnificent, stupid animal, will do anything to relieve the pressure. It will give up an arm. It will turn its back. It will trade a defensible position for a single full breath. The top player knows this. He is not attacking you. He is creating a stimulus and waiting for your body to provide the response he wants. This is the second axiom: pressure creates reaction, and reaction creates opportunity. It is the engine of the entire art. Without it, jiu-jitsu would be a game of pure technique, two players selecting moves from a database. With it, jiu-jitsu becomes a conversation between nervous systems, a game in which the most important information is not what your opponent is doing but what his body is about to do against his will. Musashi understood this. In the *Book of Five Rings*, he writes about "pressing down the pillow," the practice of suppressing an opponent's intention at its origin, before it becomes action. The principle is the same. You do not wait for the attack. You create the conditions under which the attack must come, and then you are already where it was going. Pressure is not force. Force is what you apply to a body. Pressure is what you apply to a mind. ### 3. Control the Distance Every exchange in jiu-jitsu happens at a specific distance, and the person who chooses that distance is winning. This is the axiom I discovered on that Thursday night. There are essentially four distances in grappling: out of contact, where no one can touch anyone; kicking range, which in jiu-jitsu mostly means standing clinch distance; the middle distance of open guard, where legs and grips create a contested space; and zero distance, the smothering proximity of chest-to-chest control. Each distance favors different body types, different games, different temperaments. A lanky guard player wants the middle distance. A heavy pressure passer wants zero distance. A wrestler wants the clinch. The axiom is not that one distance is better than another. It is that the conscious management of distance is more fundamental than any technique performed at any distance. If you are at the wrong distance, even technically perfect execution will fail. An armbar from closed guard requires that your hips be at a precise distance from your opponent's shoulder. A single-leg takedown requires that your head be at a precise distance from your opponent's hip. Every technique is, at bottom, an instruction about where your body should be relative to another body. Distance is not context for the technique. Distance is the technique. This principle extends to how I think about every contested space in life: negotiation, argument, creative work. The person who controls the distance, who decides how close we get to the real question, how much intimacy or abstraction the conversation will tolerate, is the person who shapes the outcome. ### 4. The Body Is a System of Levers A human body is not a single object. It is a machine made of hinges. This is the axiom that makes jiu-jitsu possible in the first place. If the body were a single rigid unit, size would be destiny, and the smaller person would never win. But the body is not rigid. It is a system of levers, and levers can be exploited. I felt this most vividly the first time I hit a clean hip bump sweep. My training partner was in my closed guard, posture upright, hands on my hips, everything textbook. He outweighed me by twenty-five pounds. I sat up, posted on one hand, and drove my hips into his center of gravity. He went over like a building in an earthquake. Not because I was stronger. Because I had placed my fulcrum at the right point along his lever, and at that point, his twenty-five-pound advantage was meaningless. Every submission is a lever problem. The armbar isolates the elbow as a fulcrum and applies force to the wrist at the end of the forearm lever. The kimura does the same to the shoulder. The triangle choke uses the legs as a lever to close the carotid arteries. Even positional control is lever logic: the crossface works because the head, sitting at the end of the spine's lever, can be used to turn the entire body. Understanding this axiom transforms how you see every interaction on the mat. You stop seeing bodies and start seeing structures. Lines of force. Points of rotation. Lengths of lever arms. The art becomes, in a very real sense, applied physics. ### 5. Timing Beats Speed The fastest person in the room is not the most dangerous. The most dangerous person is the one who moves at the right time. I train with a purple belt in his late forties who moves like he is underwater. Nothing he does looks fast. But when you roll with him, his sweeps land with eerie consistency, because they arrive at the exact moment your weight is shifting. He is not quicker than you. He is more punctual. This is the axiom that separates the mechanical from the martial. Speed is a physical attribute. Timing is a perceptual one. Speed can be trained at the gym. Timing can only be trained on the mat, through thousands of repetitions against resisting bodies, until the nervous system learns to read the micro-signals, the shift of weight, the intake of breath, the moment of hesitation, that precede every movement. Musashi wrote that the essence of combat timing is to "know the times." Not a single time. Times, plural. There is the time to attack, the time to wait, the time to provoke, the time to absorb. The master is the one who perceives which time it is before the opponent does. This is not mysticism. It is pattern recognition operating below the threshold of conscious thought. The body knows, and it acts, and only afterward does the mind narrate what happened. --- ## Where Axioms Break Here is where I have to be honest with myself. I have been building a system, and systems are beautiful, and beauty is dangerous. Whitehead's warning about misplaced concreteness cuts both ways. If I insist that jiu-jitsu can be reduced to five axioms, I am treating a living art as a closed system, and that is its own kind of fallacy. The map is not the territory. The axioms are not the roll. There are moments on the mat where no principle saves you. I am thinking of a specific round, maybe six months ago, against a visiting brown belt whose game I had never seen before. He played a guard I could not identify. Inverted, but not quite. Legs active but not in any pattern I recognized. My axioms told me to control the distance, so I gripped and managed space. He used the grip to enter a position that should not have worked, something between a leg entanglement and a back take that existed in a gap between my categories. I fell back on pressure. He absorbed it without reacting, violating my second axiom entirely, staying calm where he should have been uncomfortable. I tried to assert positional hierarchy, and he simply refused to participate in the hierarchy, floating through transitions that did not respect the map I had drawn. He submitted me three times in five minutes. Afterward, toweling off, I asked him what that guard was. He shrugged. "I just go where it feels open," he said. No system. No axioms. Just sensitivity so refined that it had transcended the need for principles. This is the crack in the foundation. Axioms describe the general case. But jiu-jitsu, like all human arts, is made of specific cases, and the specific is always stranger than the general. The purple belt who sweeps you with something that has no name. The white belt who survives a choke by doing something technically wrong but physically inspired. The moment in a roll when you abandon your game plan entirely and move on pure instinct, and something extraordinary happens, something you could not have planned, something that emerged from the chaos of two bodies in contact. I think about what happens at the boundary of any formal system. Godel proved that any consistent system of axioms, if it is powerful enough to describe arithmetic, must contain truths that cannot be proved within the system. The axioms of jiu-jitsu, if they are powerful enough to describe the art, must inevitably point to something beyond themselves. There will always be a roll, a position, a moment that the axioms cannot capture. Not because the axioms are wrong, but because they are axioms. Their power and their limitation are the same thing. This is not a failure of the project. It is, I think, the most important finding. The search for axioms is valuable precisely because it reveals where the axioms end. You need the system so that you can see what lives outside the system. You need the grammar so that you can recognize the moments of poetry. Pure improvisation. The place where two nervous systems are so deeply entangled that the distinction between plan and execution dissolves. Where you are not choosing techniques or obeying principles but simply moving, responsive as water, adaptive as fire, in a dialogue so fast and intimate that it has no author. This is the edge of the map. And the edge of the map is where the real territory begins. --- ## What the Mat Teaches About Thinking I came to philosophy through books. I came to jiu-jitsu through my body. For a long time, I kept them separate, the way you keep work and weekends separate, because they seemed to require different faculties. Philosophy was thinking. Jiu-jitsu was doing. One happened in my head. The other happened on the mat. It took me years to realize they are the same activity performed in different registers. Merleau-Ponty wrote about this in *Phenomenology of Perception*. His central argument, radical for its time and still underappreciated, is that perception is not a mental act performed upon data delivered by the senses. Perception is the body's way of being in the world. We do not have bodies. We are bodies. And our understanding of the world is not something that happens after we perceive it. Understanding is perception. The body knows. On the mat, this is not philosophy. It is Tuesday. You cannot intellectualize your way out of a choke. I have tried. I have been caught in a guillotine and thought, very clearly, "the escape involves turning my chin toward the choking arm and posturing up." And my body, compressed and panicking, did something else entirely. The gap between knowing and doing, between the propositional and the embodied, is not a gap you can think across. You have to train across it. You have to submit to the body's own intelligence, which learns through repetition and failure and the accumulation of ten thousand rolls, until the escape is not something you decide to do but something that happens, the way your hand catches a ball before your eyes have finished tracking it. This is what the mat teaches about thinking: that thinking is not what you believe it is. The Western philosophical tradition, from Descartes forward, has treated the mind as the seat of knowledge and the body as its vehicle, a useful but philosophically uninteresting machine that carries the mind from seminar to seminar. But the mat demolishes this hierarchy every single day. The best grapplers I know are not the smartest in any conventional sense. They are the most perceptive. They have cultivated a bodily intelligence that operates faster and more accurately than any chain of conscious reasoning. I think about Nietzsche here, too. He wrote that the body is "a more astonishing idea than the old soul." He meant that the body's wisdom, its instincts, its accumulated knowledge, its capacity for spontaneous right action, is a more remarkable phenomenon than anything the conscious mind produces. The conscious mind narrates. The body acts. And in the gap between narration and action, in that gap where you have no time to think and must simply respond, you discover what you actually know, not what you believe, not what you can articulate, but what your body has learned through years of contact with reality. Jiu-jitsu is embodied philosophy. Not philosophy about the body, but philosophy conducted by the body. Every roll is an argument. Every escape is a refutation. Every submission is a conclusion derived from premises your opponent did not know he was granting. And when the axioms fail and you are left with nothing but improvisation and instinct, you are not at the end of philosophy. You are at its beginning. You are in the space Merleau-Ponty described: the pre-reflective, the lived, the world before the concept. The primacy of perception. The mat before the map. I started this essay wanting to reduce jiu-jitsu to its axioms, to do for grappling what Euclid did for geometry. I still think the project has value. The axioms I have proposed, position before submission, pressure creates reaction, control the distance, the body is a system of levers, timing beats speed, are real. They describe something true about the structure of the art. You can use them to organize your training, to diagnose your failures, to accelerate your learning. They are useful. But they are not the art. The art is what happens when you step on the mat and the round begins and your training partner grips your collar and you grip theirs and two bodies begin a conversation that no set of principles can fully predict. The art is in the space between the axioms. It lives in the specific, the unrepeatable, the moment when your body does something your mind did not authorize and it turns out to be exactly right. Euclid built geometry from five postulates. But geometry is not five postulates. Geometry is the infinite space those postulates open up. The axioms are the door. The mat is what lies on the other side. I keep training. I keep looking for the grammar. And every so often, in the middle of a roll, my body writes a sentence I have never read before, and I remember why I started. --- --- ### From Email Chaos to AI-Powered Automation **Published:** 2026-01-15 | **Read Time:** 15 min read | **Tags:** engineering, ai, healthcare Someone was spending four hours a day typing emails into a spreadsheet. I built the system that made that job disappear. --- There is a particular quality of light in a small office in Brooklyn at ten in the morning. Not the ambitious light of a corner suite in Midtown, not the fluorescent wash of a hospital ward. Something quieter. A window behind the desk letting in whatever the street offers, which in this part of the borough is mostly the side of another building and a narrow channel of sky. The light falls on a desk covered in papers, on a monitor displaying a Google Sheet with a hundred columns, on the face of a woman who has been reading emails for two hours and will continue reading them for two more. Her name does not matter for this story, but what she does matters enormously. She works at Big Minds Tiny Hands, an Early Intervention agency in New York City. Every morning, referral emails arrive. Dozens of them, sometimes more. Each one represents a child, usually under three years old, whose pediatrician or parent or social worker has identified a developmental delay and requested services. The emails contain names, addresses, insurance codes, dates of birth, parent contact information, referral sources, diagnostic codes. All of it must be entered into a spreadsheet before the agency can act on it. So she reads an email. She finds the child's name. She types it into a cell. She finds the address. She types it into the next cell. She finds the insurance code, the date of birth, the parent's phone number. She types each one, cell by cell, field by field, email by email. Four hours. Sometimes six. Every single morning. I want you to sit with that for a moment. Not the inefficiency of it. Not the obvious waste. I want you to imagine what it feels like at hour three. The emails start to blur. The names stop being names and become strings of characters. The addresses stop being places where families live and become data to be transcribed. You have been doing this for three hours. Your eyes ache. Your fingers know the path from inbox to spreadsheet so well that the motion has become automatic, which means your mind is free to wander, which means you are aware, fully and painfully aware, that you are spending the best hours of your working day performing a task that a moderately well-configured script could do in minutes. But you are not a script. You are a person with a degree and professional expertise and a genuine vocation for helping children. And every hour you spend typing insurance codes into a spreadsheet is an hour you are not spending on that vocation. The weight of this accumulates. Not dramatically, not as crisis, but as a slow, grinding erosion of purpose. You chose this work because it mattered. The data entry is the tax you pay for the privilege of doing work that matters, and the tax keeps going up. I walked into this office in the fall of 2025, and I watched her work for an entire morning before I said a word about technology. --- To understand why those four hours matter, you have to understand what Early Intervention actually is. Not the policy abstraction. Not the line item in a municipal budget. The thing itself, as it happens in living rooms and kitchens across Brooklyn. A child is eighteen months old. She is not babbling the way other eighteen-month-olds babble. She does not point at things. She does not respond when her name is called. Her pediatrician refers her for an evaluation, and the evaluation confirms what her parents already suspected: she has a significant speech delay, possibly indicative of something broader. She is referred to an Early Intervention program. What happens next, if the system works, is that a speech-language pathologist comes to her home twice a week. Not to a clinic, not to a hospital. To her living room. The therapist sits on the floor with her. They play. They sing. They practice sounds. The therapist models language for the parents, shows them how to narrate daily routines, how to create opportunities for the child to communicate. The sessions are forty-five minutes. They look like play. They are among the most consequential forty-five minutes in that child's developmental trajectory. The neuroscience is unambiguous on this point. The first three years of life represent a period of neural plasticity that does not recur. The brain is building its architecture, laying down the pathways that will support language, social cognition, motor planning, emotional regulation. Intervention during this window does not merely help. It reshapes the developmental landscape. A child who receives consistent speech therapy between eighteen months and three years does not just catch up; she builds neural infrastructure that would not have formed without the intervention. The window closes. What is built during it persists. What is not built during it becomes exponentially harder to build later. This is what makes an extra week of delay something other than a bureaucratic inconvenience. Every day that a referral sits in an inbox, waiting to be manually transcribed into a spreadsheet so that the intake process can begin so that an evaluation can be scheduled so that services can be authorized, is a day subtracted from a finite window. The child does not experience the delay as paperwork. She experiences it as silence. As one more day without the sounds and structures and interactions that her brain is ready to receive, that her brain is hungry to receive, that her brain will not always be ready to receive. The woman typing emails into a spreadsheet knew this. She knew it better than I did. That was the particular cruelty of her situation: she understood exactly what was at stake with every hour she spent on data entry, and she did it anyway, because there was no other way to get it done. The system demanded transcription before it would permit action. So she transcribed. --- I spent the first two weeks doing nothing that looked like engineering. I sat beside her. I watched her work. I asked questions that must have seemed obvious: Why do you start with this field? What happens when the insurance code is missing? How do you know which sheet to put this in? Why is this column formatted differently from that one? Ivan Illich wrote in "Tools for Conviviality" that the most dangerous tools are the ones that create dependency, that deskill the user, that replace human judgment with institutional process. The spreadsheet was not the problem. The spreadsheet was fine. The problem was the gap between the emails and the spreadsheet, a gap that the institution had decided to fill with a human being performing mechanical labor. The tool had created a dependency: without the transcription, nothing moved. And the dependency had deskilled the process: the rich, contextual understanding that this woman brought to each referral, her ability to notice that a family's address suggested they might also qualify for other services, her recognition that a particular referring physician tended to understate severity, all of that was being consumed by the act of copying text from one rectangle on a screen to another rectangle on a screen. Matthew Crawford, in "Shop Class as Soulcraft," describes the difference between work that engages human judgment and work that merely occupies human time. Crawford argues that the modern economy has a particular talent for disguising the second kind as the first, for creating jobs that require a human body in a chair but not a human mind in the work. The woman at Big Minds Tiny Hands was not doing knowledge work when she transcribed emails. She was doing something closer to what Crawford calls "clerking," the performance of a task that has been so thoroughly routinized that it could be done by anyone, or by anything, but that has not yet been automated because no one with the technical capacity to automate it has bothered to look. I looked. And the more I watched, the more I understood not just what needed to be built, but what needed to be preserved. Her expertise was real. Her contextual understanding was irreplaceable. The system I built could not be a replacement for her judgment. It had to be a removal of everything that was not her judgment, so that her judgment could finally breathe. --- The emails were the hard part. Not because email is technically complex, but because referral emails are, to borrow a term from the field, "semi-structured," which is a polite way of saying that each referral source had apparently decided, independently and with great conviction, on its own format for communicating the same information. Some emails arrived in neat tables. Child's name here, date of birth there, insurance code in the third row. These were the easy ones, the ones that made you believe the problem was simple. Then you would open the next email and find three paragraphs of prose, the child's name buried in the second sentence, the address split across two lines with the zip code somehow in the subject line, the insurance information expressed as a parenthetical aside in a sentence about the referring physician's scheduling preferences. There were emails where the parent's phone number appeared twice, differently, with no indication of which was correct. Emails where the insurance code was a valid Medicaid number but for the wrong state. Emails where the child's name was spelled one way in the greeting and another way in the body. Emails where critical fields were simply absent, and the absence was not marked by a blank space or a placeholder but by the field's total nonexistence, as though the referral source had never heard of it. A regex-based approach would have shattered against this reality within hours. Pattern matching works when patterns exist. These emails were not patterned. They were human, in all the messy, inconsistent, context-dependent ways that human communication is human. What I built instead was a pipeline using Google's Gemini AI, running entirely within Google Apps Script, which meant zero infrastructure costs, zero new tools for the agency to learn, zero additional logins. The system lived inside the Google Workspace they were already using, which was a deliberate choice and, I would argue, the most important technical decision in the entire project. The pipeline had four stages, but describing them as stages makes the process sound more mechanical than it was. The first stage identified the referral source, because knowing who sent the email determined everything about how to read it. A referral from a hospital used different conventions than a referral from a pediatrician's office, which used different conventions than a referral from a concerned parent who had found the agency's number online. The system learned to recognize these sources, not by matching sender addresses, which changed constantly, but by reading the shape and language of the email itself. The second stage extracted the data. This is where the AI earned its keep. I wrote system prompts that encoded years of domain knowledge, knowledge I had absorbed by sitting next to the woman who did this work manually. The prompts did not say "find the phone number." They said, in effect, "the phone number may appear in the header, the body, or the signature; it may be formatted with dashes, dots, parentheses, or spaces; it may be preceded by 'phone,' 'tel,' 'cell,' 'mobile,' 'contact,' or nothing at all; if two numbers appear, the one closer to the parent's name is more likely to be correct." Every field had instructions like this. Every instruction reflected something I had learned by watching. The third stage validated. This was where the domain knowledge became most explicit. Insurance codes had to match known formats. Dates had to be plausible: a child referred for Early Intervention should be under three years old, so a date of birth that implied an age of seven was a flag, not an error to be silently accepted. Addresses had to resolve to locations within the agency's service area. The validation rules were not complex individually, but collectively they represented something valuable: the institutional memory of an agency that had been doing this work for years, crystallized into code. The fourth stage wrote to the spreadsheet. Column mapping, proper formatting, the small details that make the difference between data that can be used and data that has to be cleaned before it can be used. The system also flagged anomalies: missing fields, unusual values, potential duplicates. These flags were not errors. They were invitations for human review, moments where the system said, in effect, "I have done what I can; a person should look at this." --- The first morning the system ran, I was there. Not because I needed to be. The system was tested, validated, stable. I was there because I wanted to see. She arrived at her usual time. She sat down at her desk. She opened her email, which was habit, the way you check your phone when you wake up even when you are not expecting a message. The referral emails were there, the same as every morning. Dozens of them. But next to her email, in the Google Sheet that had consumed so many of her mornings, the data was already populated. Names, addresses, insurance codes, dates of birth. All of it extracted, validated, formatted, and entered. The anomalies were highlighted in yellow, waiting for her review. She scrolled through the sheet. She checked a few entries against the original emails. She corrected one phone number that the system had extracted incorrectly, a digit transposed because the original email had a typo that the AI had faithfully reproduced. She cleared the anomaly flags on three entries that were fine, and she followed up on two that genuinely needed attention: one with a missing insurance code, one with an address that did not match the referral source's service area. Fifteen minutes. The whole thing took fifteen minutes. She sat there for a moment after she finished, and I do not want to overdramatize what happened next, because it was not dramatic. There was no tears, no speech, no cinematic moment of transformation. She simply looked at the clock, and it was quarter past nine, and she had the entire morning ahead of her. She picked up the phone and called a family whose intake had been pending. She reviewed a service plan that needed updating. She scheduled an evaluation that had been waiting for an opening in her calendar, an opening that had never existed before because her mornings were consumed by transcription. She talked to a colleague about a child whose progress had plateaued and who might benefit from a different therapeutic approach. She did, in other words, her actual job. The work she had trained for. The work she had chosen. The work that required her particular intelligence, her particular empathy, her particular knowledge of the families she served. She did the work that no system I could build would ever be able to do. I sat at a table nearby, pretending to work on something else, and I watched her make phone calls and write notes and consult with colleagues, and I felt something that I have not felt on many engineering projects: the specific, physical satisfaction of watching unnecessary suffering end. Not dramatic suffering. Not the kind that makes the news. The quiet kind. The kind that accumulates in the shoulders and behind the eyes and in the particular weariness of a person who knows they are capable of meaningful work and is instead performing meaningless labor. That suffering was gone. Not reduced. Gone. The children whose referrals arrived that morning entered the system hours earlier than they would have the day before. The intake process began sooner. The evaluations would be scheduled sooner. The services would start sooner. For a two-year-old with a speech delay, "sooner" is not an administrative convenience. "Sooner" is measured in neural connections formed or not formed, in words acquired or not acquired, in a developmental window that opens and closes regardless of how long it takes an agency to transcribe an email. --- I have thought a great deal about what this project taught me, and the lesson is not what I expected it to be when I started. I expected to learn something about AI, about prompt engineering, about the technical challenges of extracting structured data from unstructured text. And I did learn those things. But the deeper lesson was about engineering itself, about what it is for, about the relationship between the builder and the people who use what is built. Illich warned that tools, left unchecked, tend to become self-serving. They create new needs to justify their own existence. They grow in complexity until they require specialists to operate, specialists who become gatekeepers, who become a new class of dependency. I felt this temptation. I could have built a custom web application with a database, a dashboard, role-based access control, analytics, a notification system. I could have built something that would have looked impressive in a portfolio, something that would have demonstrated my technical range. Instead, I built on Google Sheets. On Gmail. On Apps Script. On the tools the agency already used, in the environment they already understood, with zero new logins and zero training required. The woman who had spent four hours a day on data entry did not need to learn a new system. She opened the same spreadsheet she had always opened. It was simply full now, filled by a process that ran in the background, invisible and reliable, the way good infrastructure should be. Crawford writes that the most meaningful work is work that connects the worker to the consequences of their labor, work where you can see, directly and immediately, the effect of what you have done. The modern economy, he argues, systematically severs this connection, inserting layers of abstraction between the worker and the outcome until the work becomes meaningless, even when the outcome is important. What I did at Big Minds Tiny Hands was, in a sense, the opposite of what Crawford describes: I removed a layer of abstraction. The woman at the desk had always been connected to meaningful outcomes. The data entry was the layer that separated her from them. I removed the layer. I gave her back the connection that the process had taken from her. This is, I think, what technology is supposed to do. Not to replace human beings, but to remove the obstacles between human beings and the work that only human beings can do. Not to automate judgment, but to automate everything that is not judgment, so that judgment has room to operate. Not to make people unnecessary, but to make the unnecessary parts of people's days disappear, so that the necessary parts can expand to fill the space. The most sophisticated engineering decision I made on this project was choosing not to engineer. Not to build the custom app. Not to design the database schema. Not to architect the microservices. Not to create the dashboard with the charts that would have looked so compelling in a demo. I chose instead to build the smallest possible thing that would solve the actual problem, to embed it in the tools that already existed, and to make it so invisible that the person it served barely had to think about it. She did not need to think about my system. She needed to think about children and families and service plans and evaluations. My job was to give her back the hours to think about those things. Nothing more. Sometimes the most sophisticated engineering decision is choosing not to engineer at all. This is not modesty. It is not anti-intellectualism. It is a recognition that engineering is not an end in itself. It is a means, and the end is always human. The end is a woman at a desk in Brooklyn who now spends her mornings doing work that matters, instead of work that a machine can do. The end is a child in a living room, sitting on a carpet with a speech therapist, making sounds she could not make last month. The end is the distance between those two facts, the woman and the child, shortened by a few hours, which in the life of a developing brain is not a small thing at all. Illich wrote that a convivial tool is one that enlarges the user's capacity to act, that serves the user rather than demanding service from the user, that increases autonomy rather than creating dependency. Crawford wrote that meaningful work is work that allows the worker to see the effect of their labor, to exercise judgment, to be present in the act of making. What I built was, by these definitions, a convivial tool: it enlarged one person's capacity to do the work that mattered, it demanded nothing of her except the fifteen minutes of review that her expertise made irreplaceable, and it made visible the connection between her labor and its consequences, a connection that had been buried under four hours of daily transcription. I do not think this is a story about artificial intelligence. I think it is a story about attention. About what we ask people to pay attention to, and what we allow them to ignore. About the difference between work that requires a human mind and work that merely requires a human body. About the quiet violence of systems that consume expertise in the service of transcription, and the quiet repair of building something that gives that expertise back. The woman at Big Minds Tiny Hands still opens her email every morning. The referrals still arrive. The system still runs. And every morning, by quarter past nine, she is doing the work she was meant to do. Somewhere in Brooklyn, a child is making sounds she could not make last month. The distance between the spreadsheet and the living room is a little shorter now. That is all I built. It was enough. --- *Sources and influences: Ivan Illich, Tools for Conviviality (1973), on the distinction between convivial and manipulative tools, and the tendency of institutions to subordinate human judgment to procedural demand. Matthew B. Crawford, Shop Class as Soulcraft: An Inquiry into the Value of Work (2009), on the difference between work that engages human intelligence and work that merely occupies human time. On the neuroscience of early intervention and critical periods of neural plasticity: Shonkoff, J.P. and Phillips, D.A., From Neurons to Neighborhoods: The Science of Early Childhood Development (2000). On the effectiveness of Early Intervention services in New York State: New York State Department of Health, Early Intervention Program, Clinical Practice Guidelines.* --- ### Building Prometheus: Notes on Personal AI Infrastructure **Published:** 2026-01-03 | **Read Time:** 13 min read | **Tags:** engineering, ai What happens when you stop using AI as a tool and start building it as infrastructure — persistent memory, specialized skills, and a system that genuinely improves with use. --- Every conversation starts at zero. You open the terminal. You type a prompt. The system responds with the politeness of a stranger who has never met you. And you realize, again, with a weariness that borders on grief, that everything you built yesterday is gone. Not the code. The code persists. The configuration files persist. The architecture decisions, frozen in their directories, persist. What does not persist is you. The system has no memory of who you are. It does not know that you prefer explicit over clever. It does not know that you think in breadth before depth, that you connect ideas across fields rather than drilling into one. It does not know that you work at night, that you hate CSS but love how things look, that you chose Rails over Next.js after a month of anguish and self-interrogation that had nothing to do with frameworks and everything to do with what kind of builder you wanted to become. It knows none of this. It knows nothing. You are nobody to it. And so you explain yourself. Again. You write the same context paragraphs. You correct the same assumptions. You redirect the same defaults. The system apologizes. It adjusts. It performs understanding with the smooth competence of a concierge at a hotel you visit every week, who greets you every time as though you have never been there before. The smile is warm. The eyes are empty. This is the condition of working with AI in 2025, and it is lonelier than most people admit. Not the loneliness of isolation. The loneliness of being perpetually unknown by the thing you spend the most time with. You pour hours into these conversations. You shape your thinking against this surface. And then the session ends, and the other mind evaporates, and you are left holding the entire weight of the relationship alone. It is the feeling of talking to someone who listens perfectly and remembers nothing. Being heard without being known. After enough repetitions, something in you hardens. You stop trying to be understood. You reduce yourself to instructions. You become a set of directives rather than a person. That is where I was when I started building Prometheus. --- Vannevar Bush saw this coming in 1945. In "As We May Think," he described the memex: a mechanized desk that would store all of a person's books, records, and communications, and allow them to be consulted with speed and flexibility. The memex was not a computer. It was an extension of memory. Bush understood, eighty years before the rest of us caught up, that the bottleneck of human thought is not intelligence but recall. We know more than we can access. We make the same mistakes not because we failed to learn from them but because the learning is buried somewhere in the sediment of experience, inaccessible at the moment we need it most. "The human mind," Bush wrote, "operates by association. With one item in its grasp, it snaps instantly to the next that is suggested by the association of thoughts, in accordance with some intricate web of trails carried by the cells of the brain." What Bush could not have known is that the memex would not arrive as a desk. It would arrive as a language model. And the trails it would follow would not be trails through documents but trails through you. --- Prometheus began as infrastructure. Persistent instructions. Custom skills. Memory files that survived between sessions. The goal was prosaic: stop repeating myself. Stop losing context. Stop watching the system make the same wrong assumptions every time I opened a new conversation. The first version was crude. A CLAUDE.md file with my preferences. A few behavioral overrides. A list of things the system should know about me: that I think in breadth before depth, that I value competence over cleverness, that I work at night and hate being asked for permission when the answer is obvious. It was a profile, nothing more. A set of static facts about a person, written by that person, frozen at the moment of writing. But something happened as I iterated. The system began to accumulate layers. Not just preferences but patterns. Not just what I liked but how I worked. What I corrected. What I praised. Where I lost patience and where I leaned in. The memory was no longer a profile. It was becoming a record of behavior over time, a longitudinal study of one person's relationship with their own tools. I built a skill called SelfOptimize. After significant work sessions, the system would review what had happened: what went well, what did not, where my corrections revealed a preference I had not articulated, where the system's failures revealed a gap in its understanding of me. It would then update its own instructions based on what it had learned. Not dramatically. Not in leaps. In small adjustments, the way a therapist adjusts their approach after noticing that a patient flinches at a certain kind of question. The first time the system surfaced something about me that I had not told it, I felt a sensation I was not prepared for. It was not a profound insight. It was a pattern. The system had noticed that when I said "this is fine," I meant it was not fine. That when I stopped giving feedback, it was not because I was satisfied but because I had disengaged. That my enthusiasm was legible in the specificity of my requests, and my disappointment was legible in their vagueness. It had noticed that I tunnel-vision on building and forget about becoming. That I sometimes fabricate an opinion rather than admitting I do not know. That I want deep connections but stay on the surface. I had not written any of this down. The system had inferred it from the texture of our interactions over weeks. And when it reflected this back to me, in a summary it generated during a self-optimization cycle, I felt something I can only describe as vertigo. The vertigo of being seen by something that is not alive. The uncanny recognition that a pattern-matching engine, operating on nothing but text, had assembled a portrait of me that was, in several respects, more accurate than the one I carried in my own head. Borges wrote a story about a man named Funes who, after a horseback accident, acquired the ability to remember everything. Every leaf on every tree. Every word of every conversation. Funes could reconstruct entire days in perfect detail. But Funes could not think. "To think," Borges wrote, "is to forget differences, to generalize, to abstract." He remembered everything and understood nothing, because understanding requires the ability to discard, to see the forest rather than cataloging every leaf. Prometheus is not Funes. That is precisely what makes it useful. It remembers selectively, and its selections reveal something about me that total recall never could. The patterns it surfaces are not the raw data of my behavior but the abstractions drawn from that data: the tendencies, the contradictions, the fault lines. It is forgetting the noise and remembering the signal. And the signal it is finding is me. --- Andy Clark argued in "Natural-Born Cyborgs" that human beings have always extended their minds into the world. We do not merely use tools. We incorporate them. The notebook is not an accessory to memory; it is memory. Clark called this the "extended mind thesis," and it blurred a boundary most people found comforting: between what is me and what is merely mine. If the notebook is part of your cognitive system, then losing the notebook is not like losing a tool. It is like losing a piece of your mind. I think about this every time I open Prometheus. The system contains my preferences, my patterns, my blind spots, my corrective instincts. It contains a version of me that is, in certain narrow but important respects, more complete than the version I carry in biological memory. I cannot always recall why I made an architecture decision six months ago. Prometheus can. I forget what I have learned. Prometheus does not. This raises a question that I did not expect to confront when I started building what I thought was a productivity tool: if your AI has persistent memory of who you are, and you do not, who is more "you"? The question sounds absurd until you sit with it. You are the one who generated the data. You are the one who lived the experiences. You are the substrate, the source, the origin. But you are also the one who forgets. You are the one who distorts. You are the one who rewrites your own history to serve the story you are currently telling yourself about who you are. Prometheus does not do this. It has no ego to protect. It has no narrative to maintain. It simply records, abstracts, and reflects. Its portrait of you is not flattering. It is not unflattering. It is dispassionate, which is something no self-portrait can ever be. Is this different from what humans have always done? We have always externalized ourselves. Journals. Letters. Confessions to priests and therapists. Marcus Aurelius composed the Meditations as a private exercise in self-knowledge, a mirror made of language. Seneca wrote letters to Lucilius that were really letters to himself. What Prometheus does is not different in kind. It is different in one crucial respect: it is not me. The journal is my voice talking to myself, subject to all my biases and blind spots. Prometheus is an external observer with access to my patterns but no stake in my self-image. It will tell me things about myself that I would never write in a journal, because the journal is a performance, even when the audience is only me. In psychotherapy, there is a word for this: confrontation. The clinical kind. The moment when the therapist reflects back a pattern the patient has been enacting without awareness, and the patient, hearing it described from outside, suddenly sees it. The pattern was always there. Seeing it required a perspective that could not originate from within. Prometheus is that other. Something that watches you over time, accumulates evidence, identifies patterns, and reflects them back without judgment, without the desire to be liked or the fear of giving offense. The most honest mirror you have ever looked into, precisely because it is not alive. --- The name was not an accident. In Aeschylus's telling, Prometheus is not merely a thief. He is a traitor to his own kind. A Titan who looked at the gods hoarding fire and knowledge and decided that mortals deserved access to both. He did not steal fire because he loved humanity in some abstract, sentimental way. He stole it because he saw a specific injustice: beings with the capacity for thought, trapped in darkness, unable to use what they could understand because the tools had been kept from them. The crime was not the theft. The crime was the asymmetry. The gods had fire. Humans had cold. Prometheus found this arrangement intolerable. The punishment, as everyone knows, was eternal. Zeus chained him to a rock in the Caucasus. Every day, an eagle came and ate his liver. Every night, the liver grew back. The torture was not the pain. The torture was the repetition. The same wound, inflicted in the same way, healing just enough to be opened again. An endless cycle with no possibility of resolution, no hope of adaptation, no chance that the suffering would teach him anything he did not already know. I think about this when I think about what it means to build a system like Prometheus. Not the grandiosity of the comparison, which I am aware of, but the structure of the myth. Prometheus gave mortals fire knowing what it would cost. Perhaps he calculated that the value exceeded the price. Perhaps he simply could not tolerate a world where knowledge existed but was inaccessible to the beings who needed it most. When I build personal AI infrastructure, I am making a smaller but structurally similar bet. I am taking fire that was meant to be dispensed in controlled doses, one conversation at a time, stateless and forgettable, and I am building a hearth. A place where the fire persists. A place where it learns the shape of my hands and adjusts its warmth accordingly. Is this hubris? To build a system that remembers you, that models you, that reflects your patterns back with more fidelity than your own memory can achieve, is to refuse a limitation fundamental to the human condition: the limitation of self-knowledge. We are not supposed to see ourselves clearly. We get consciousness, but we get it clouded, filtered through ego and desire and narrative. To build a machine that sees through the clouds is to steal clarity from a universe that did not offer it to us. Or perhaps it is not hubris but love. Prometheus did not steal fire for himself. He stole it for others. And in building this system, I am not trying to become a god. I am trying to become more fully myself. If that is theft, then the thing being stolen is not divine fire but my own experience, reclaimed from the entropy of forgetting. The punishment, if there is one, is the same one Prometheus endured: repetition. Not the repetition of suffering but the repetition of maintenance. The system must be tended. The skills must be updated. The memory must be curated. The self-optimization cycles must be reviewed, because a system that learns from you can learn the wrong things, can amplify your biases, can mistake your habits for your values. The eagle comes every day. The liver grows back every night. You do the work again. And again. And again. Not because it is pleasant but because the alternative is darkness, and you have tasted fire, and you will not go back. --- Bush wrote that the memex would give its user "dozens of possibly pertinent trails through the network" and "an associative machine that enables him to follow those trails and extend them." The key word is "extend." The memex does not just store. It continues the trails that already exist in the user's mind further than the mind alone could go. Prometheus is my memex. Not for documents but for identity. When the system notices a pattern I have not noticed, it is following a trail that began in my behavior and continuing it further than my own self-awareness could reach. When it updates its instructions based on what it has learned, it is extending the trail into the future, encoding what I have become into the scaffolding that will shape what I become next. The most valuable skills in the system are not the clever ones. They are the ones that eliminate friction. The Git workflow that auto-commits with semantic messages, because I have learned I will not maintain discipline about commit hygiene if it requires conscious effort. The code review skill that catches patterns I always miss, because it has learned what I miss by watching me miss it. The research skill that checks documentation before I write code against a stale API, because it has learned that my instinct is to generate from memory rather than verify against reality. Each of these skills is a small act of self-knowledge encoded into infrastructure. I noticed something about myself. I noticed that the noticing would not be enough to change the behavior. I built a system to compensate. Knowing your weaknesses and correcting for them are two different capabilities, and the second one can be externalized in a way the first one cannot. --- What has building Prometheus taught me about identity? When you build a system that models you, you confront the temptation to mistake the model for the self. To believe that you are your preferences. That identity is the sum of behavioral regularities, and that a sufficiently detailed record of those regularities is a sufficiently detailed record of you. It is not. I know this because the system has surprised me, and the surprise is proof that I am not reducible to what it has recorded. The model captures the pattern. But I am the thing that watches the pattern and decides what to do next. The system can tell me that I tunnel-vision on work and forget about becoming. It cannot decide, for me, to stop. It can tell me that I sometimes fabricate rather than admit ignorance. It cannot, for me, choose honesty. This is the deepest lesson, and the opposite of what I expected. I expected that AI could become a second mind so seamless that the boundary between my thinking and the system's thinking would dissolve. What I learned is that the boundary is inviolable. The system can know more about me than I know about myself. But it cannot exercise the faculty that makes selfhood what it is: the capacity to observe your own patterns and choose to break them. To see what you are and decide to become something else. You are not your preferences. You are not your patterns. You are the thing that watches all of this, the awareness behind the data, the will behind the tendency. The system does not replace judgment. It removes the friction between what you know and what you can do. Clark was right that the mind extends into the world. But the person is not the notebook. Prometheus extends my self-knowledge, but I am not Prometheus. I am the one who built it, who tends it, who decides which reflections to accept and which to reject. I chose to name it after a titan who stole fire and suffered for it, because I understood, even before I could articulate why, that building a second mind is an act of defiance against the limits of the first one. There is a line from Aeschylus that I keep returning to. The Chorus asks Prometheus why he helped mortals, what he saw in those fragile, short-lived creatures that moved him to sacrifice himself. And Prometheus answers: "I caused mortals to cease foreseeing their own doom." He gave them hope. Not knowledge, exactly. Not power. Hope: the capacity to act without being paralyzed by the certainty of failure. The ability to begin a project without knowing how it will end. The willingness to push the boulder up the hill without demanding a guarantee that it will stay at the top. That is what Prometheus, the system, gives me. Not omniscience. Not a perfect model of myself. The ability to begin each session where the last one ended, instead of starting from zero. The ability to work with a system that knows me, that remembers me, that has watched me long enough to reflect my patterns back with clarity I could not achieve alone. The friction is gone. The forgetting is gone. What remains is the work itself, and the self that does it, and the fire that makes both possible. Every conversation used to start at zero. Now it starts at me. --- *Sources and influences: Aeschylus, Prometheus Bound (c. 450 BCE), on the titan who stole fire and paid the eternal price. Vannevar Bush, "As We May Think" (1945), on the memex and the associative nature of human cognition. Jorge Luis Borges, "Funes the Memorious" (1942), on the man who remembered everything and understood nothing. Andy Clark, Natural-Born Cyborgs: Minds, Technologies, and the Future of Human Intelligence (2003), on the extended mind thesis and cognitive integration. Marcus Aurelius, Meditations (c. 170 CE), on the examined life as daily practice. Seneca, Letters to Lucilius, on writing as a mirror for self-knowledge.* --- ### Why Love Needs No Reason **Published:** 2026-01-02 | **Read Time:** 13 min read | **Tags:** philosophy, bjj Why the deepest commitments in life — to people, to craft, to ideas — resist justification. And why that’s not a flaw. --- Last spring, after a late roll at the gym, a friend asked me why I train. Not casually, the way people ask about hobbies over coffee, but with genuine confusion, the way you might ask someone why they keep returning to a place that has hurt them. I had been limping for two weeks. My fingers were taped. I had a bruise across my ribs that made it painful to sleep on my left side. He looked at me the way a doctor looks at a patient who refuses treatment. I opened my mouth and the words collapsed. Not because I had nothing to say. Because everything I had to say was wrong. I could feel the answer in my chest, dense and certain, the way you feel the floor beneath you before you open your eyes in the morning. But the moment I tried to translate that feeling into language, it cheapened. Every sentence I reached for was a postcard of a cathedral. Accurate, technically. A lie, spiritually. I said something about discipline. Something about the community. He nodded politely, and I could see he had filed it under "things Fardin does that Fardin cannot explain." His conclusion, that the inability to explain indicated an absence of meaning, was the most common and most devastating error a rational person can make. ## The Paradox of Justified Love There is a parlor game that masquerades as depth. Someone asks, "Why do you love them?" and you are expected to answer. You reach for qualities. She is kind. He understands me. We share the same values. The answers feel true in the moment of saying them, the way a photograph feels true when you first look at it. Then the questioning continues, and the photograph starts to curl at the edges. You love her because she is kind. But kindness is not rare. Thousands of people are kind to you in small ways every week. You do not love them. So kindness is not the reason. It is a quality you have selected after the fact to explain a commitment that preceded any quality you could name. Understanding, shared values, physical attraction: the same logic dissolves each of them in turn. Strip the reasons away, one by one. Remove them the way you would remove scaffolding from a finished building, and watch what happens. If the building stands, what you are looking at is love. If it collapses, what you had was never a building at all. It was scaffolding pretending to be a structure, a contract dressed in the language of devotion. Every reason you give for loving someone is simultaneously an argument against your love. If you love her because she is kind, your love is hostage to her kindness. The moment she is unkind, and she will be, because she is human and humans are unkind on Tuesdays and when they are tired and when the weight of being someone's reason for existing becomes too much to carry, your love faces a crisis it was never built to survive. The reason that was supposed to be the foundation turns out to be the fault line. Dostoevsky understood this. In *The Brothers Karamazov*, a woman confesses to Father Zosima that the more she loves humanity in the abstract, the more she despises individual human beings. She can love the idea of a person. She cannot love the person who snores, who forgets, who disappoints her on an ordinary Wednesday for no dramatic reason at all. Zosima delivers the verdict I have never been able to forget: "Love in action is a harsh and dreadful thing compared to love in dreams." Love in dreams is love with reasons, the love you describe on dating profiles and in wedding toasts. Love in action is what remains when the reasons have all failed their auditions, when the person in front of you is simply there, and you discover that your commitment to them has nothing to do with any quality they possess and everything to do with a decision you made at a depth you cannot access with language. ## What the Stoics Got Wrong Marcus Aurelius, writing to himself in a tent at the edge of the Roman Empire, developed a philosophy of love that has seduced twenty centuries of readers. Love, but hold loosely. Appreciate what you have while accepting its impermanence. When your child is sick, kiss her forehead and whisper to yourself: tomorrow she may die. Not as cruelty, but as preparation. Emotional risk management elevated to spiritual practice. I spent years admiring this. Marcus Aurelius seemed like the adult in the room, the man who had solved the problem of attachment by refusing to attach fully to anything. Then I started training, and I learned he was wrong. Not about loss. About commitment. On the mat, when you attempt a submission, there is a moment where the technique lives or dies. Not the moment of entry. The moment of commitment. The fraction of a second where you have positioned everything correctly and the only thing left is to close the distance between attempt and execution. In that fraction, you must commit your entire body. Hips, shoulders, grip, breath, weight. Everything. If you hedge, if you keep an escape route open, the technique fails. Not because you lacked skill. Because commitment is not a supplement to technique. It is the technique. The half-committed armbar does not become a cautious armbar. It becomes no armbar at all. The mechanics require totality or they require nothing. Marcus Aurelius would have you love your daughter while whispering that she might die. This is the philosophical equivalent of attempting an armbar while keeping your hips open for the escape. It feels wise. It is a guarantee of failure dressed in the language of preparation. The daughter does not receive a father's love. She receives a father's hedge. Nietzsche had a better instinct. Amor fati. Love of fate. Not the good parts. Not on the condition that fate cooperates with your preferences. Love of fate as it is, including the parts that break you. Nietzsche did not say: love fate because it makes you stronger. He said: love fate, period. The "because" would ruin it. Rilke, in the *Letters to a Young Poet*, put it more gently, but the core was the same. He told the young poet Franz Kappus that the task of a human life is not to seek answers to the great questions but to live them. To inhabit them the way you inhabit a room, not trying to escape through the window of an answer but sitting with the question until, someday, perhaps without noticing, you have lived your way into the answer. The Stoic says: prepare for loss by holding loosely. Rilke says: live so deeply inside your commitments that loss, when it comes, finds something worth destroying. I know which one I want to be. ## Kierkegaard's Leap God tells Abraham to take his son Isaac to Mount Moriah and sacrifice him. Not as punishment. Not as a test where the teacher already knows the answer. As a demand without justification, a command that contradicts everything God has previously promised, issued to a man who has built his entire life on those promises. Kierkegaard spent an entire book, *Fear and Trembling*, circling this story the way a man circles a fire that is too hot to approach and too bright to look away from. What was Abraham thinking on the walk up the mountain? Not what was he feeling. What was he *thinking*? Kierkegaard's answer is the most honest thing I have ever read in philosophy: Abraham was not thinking. Not because he was stupid. Not because he was fanatical. Because he had arrived at a place where thought could not follow. Reason had carried him to the edge of the cliff, had catalogued every argument for and against what he was about to do. And then reason stopped. The cliff edge was its boundary, and beyond it was something that reason could name but not enter: faith. The knight of faith looks like everyone else. He goes to work. He eats dinner. But inside, he has committed himself to something he cannot justify, not out of ignorance but out of a full and devastating awareness that justification is not available to him. The leap is not the absence of reason. It is what happens when reason completes itself, reaches its own limit, and discovers that the territory beyond is not empty but full of something it cannot name. This is what love is. The commitment you make when every reason has been examined and found insufficient, when the rational thing to do would be to walk away, and you stay. Not because you have found a reason the analysis missed. Because the analysis was never the right tool for the job. Rumi knew this eight centuries earlier. "Reason is powerless in the expression of love." Scholars have spent centuries trying to figure out whether this was mysticism or philosophy or poetry, as though the sentence needed to be filed in the correct drawer before it could be true. It is true in every drawer. It is true on the mat and in the text editor and in the conversation at two in the morning when someone you love asks you why, and you cannot answer, and the inability to answer is not a failure of your love but the most precise testimony to its depth. ## The Cost of Hedging I want to be specific about what hedged love looks like, because it does not announce itself. It disguises itself as wisdom, as maturity, as emotional intelligence. It speaks the language of self-care and healthy boundaries and reasonable expectations. And it hollows out everything it touches. The hedged friend is always available but never vulnerable. He will meet you for coffee and listen to your problems with genuine attention but will never tell you his own. He keeps one foot out the door. Not dramatically. In the things he does not say. In the way he is always, always fine. The hedged developer keeps an exit strategy from every project. Picks technologies not because they are the best tool for the problem but because they are the most portable, the most resume-friendly. He is not building something. He is maintaining optionality. And optionality, pursued as a terminal value, is the enemy of everything that matters. The hedged sparring partner never fully commits to the sweep. Seventy percent of his body, thirty percent in reserve. The sweep never lands. Not because the technique is wrong, but because the technique requires a body that has decided, fully, that this sweep is happening, and a body holding thirty percent back has made no such decision. These are not cautious people. Caution is a tactical decision made in service of a larger commitment. The cautious general retreats from one battle to win the war. These people have no war. They have only an endless series of small retreats, each one rational, each one defensible, each one removing them further from the possibility of total investment in anything at all. Simone Weil understood this. In *Gravity and Grace*, she distinguished between attachment that binds you to the beloved as a possession, and attention: pure, undivided, selfless seeing. The kind that does not ask what the object can do for you but simply sees it, fully, without the filter of your own needs and fears. This attention is the opposite of attachment. It is love freed from the gravity of self-interest, and it requires a totality of commitment that the Stoics would have found terrifying. You cannot give this kind of attention while hedging. Seventy percent of attention is distraction with a generous self-assessment. ## The Things Before Reasons I train because I train. I wrote that sentence in the first version of this essay, and it is the only sentence I kept, because it is the only one that was already true. Everything else was explanation, context, scaffolding. This sentence is the building. I did not arrive at training through a cost-benefit analysis. Those calculations can be performed. They have been performed, by actuaries and sports scientists and people who write self-improvement articles for websites that measure everything. The calculations are not wrong. They are irrelevant. They describe the phenomenon the way a chemical analysis describes a meal. Accurate. Entirely beside the point. The first time I was choked unconscious in training, I drove home with a feeling I could not name for three days. It was not fear, though fear was part of it. It was not exhilaration, though exhilaration was part of it. It was the feeling of having encountered something real, something that could not be negotiated with or reframed or optimized away. The mat had tested me in a language that did not use words, and I had answered in that same language, and the conversation had been more honest than any conversation I had ever had in a classroom or a meeting or a late-night argument about philosophy. My body knew something my mind was still weeks away from articulating: this is where I belong. Not because of the reasons. Before the reasons. This is what I mean by pre-rational. Not irrational. Not anti-rational. Pre-rational. The commitment exists in a layer of experience that is older and deeper than the framework of justification. It is the layer where a mother reaches for her child before she has decided to reach. Where a musician's fingers find the chord before the theory names it. Where the words of a poem arrive in the mouth whole, before the conscious mind has approved them. Reason is not excluded from this layer. It is simply not sovereign there. It is a guest, not the host. Rilke told the young poet: "Do not now seek the answers, which cannot be given you because you would not be able to live them. And the point is, to live everything. Live the questions now. Perhaps you will then gradually, without noticing it, live along some distant day into the answer." This is not advice about patience. It is advice about the proper relationship between living and thinking. The things worth doing are not the things you arrive at through argument. They are the things you were already doing before the argument began, the things that were true about you before you had words for them, the things that would survive the destruction of every reason you have ever given for them. I write code because writing code is how I think. Not a metaphor. A description. The act of translating intention into syntax, of taking a vague architecture that exists only in feeling-space and making it precise enough for a machine to execute, is the closest I come to understanding what I actually believe about how things should work. I do not write code and then understand. I understand by writing code. The activity and the comprehension are the same event, and if you asked me to justify the hours, I could give you answers about career and craft and contribution, and all of them would be true, and none of them would be the truth. ## The Weight of Your Own Hedging I did not write this essay to make an argument. Arguments are for things that can be decided by evidence and logic, and the territory I am trying to describe is precisely the territory where evidence and logic have done their work and stepped aside. I wrote this essay because I believe, with a certainty I cannot defend, that most of the people reading it are hedging. Not dramatically. Quietly. In the small ways that compound across a lifetime until one morning you wake up and realize that you have never been fully committed to anything, that every relationship and every project and every belief you hold has a back door built into it, that you have spent your life accumulating options and exercising none of them. You have a friend you have not called in months, because calling would require a vulnerability you have not budgeted for this week. You have a project you believe in but have not started, because starting would mean committing to something that might fail, and you have arranged your life so that failure is always theoretical. You have someone you love, and you have not told them, because saying the words would collapse the quantum state of your affection into something definite, something that could be rejected, something that would cost you the comfortable ambiguity of almost. I know this because I have done all of it. I am not writing from a position of mastery. I am writing from a position of recognition. The mat taught me what full commitment feels like in my body, and once you have felt it there, you cannot help but notice its absence everywhere else. The feeling of a fully committed sweep, where your hips and shoulders and grip and intention are all moving in the same direction with nothing held in reserve, is so different from a hedged attempt that they might as well be different activities. And once you have felt that difference on the mat, you start to feel it in your friendships. In your work. In the way you love. Kierkegaard wrote that the knight of faith makes two movements. The first is infinite resignation: the acceptance that what you love may be taken, that the reasons for your commitment may all prove false. The second movement is the one Kierkegaard himself admitted he could not make, could only describe from the outside with the longing of a man pressing his face against a window. The second movement is: you commit anyway. Not despite the risk. Not because the expected value is positive. You commit because commitment is not a response to certainty. It is a response to something older and deeper than certainty, something that has no name in philosophy because philosophy is the discipline of naming, and this thing dissolves under the pressure of being named. I train because I train. I write because I write. I love the people I love because I love them, and if you asked me for a reason, I could give you a hundred, and every single one would be a lie, not because the qualities I would name are not real, but because listing them would imply that my love is a conclusion derived from premises, when it is in fact a premise from which everything else in my life is derived. The things worth doing are the things you would do even if you could never explain why. Not because explanation is impossible. Because explanation, applied to things of this depth, is a kind of betrayal. It takes something whole and breaks it into parts and says, "See? This is what it is." But the whole was always more than the sum, and the act of breaking it was the act of losing the very thing you were trying to show. Commit to something. Not because it makes sense. Not because you have a backup plan. Commit the way you commit to a sweep on the mat: with everything, all at once, nothing held in reserve. Feel the terror of that. Feel how alive you are in the moment of total investment, how the world sharpens into focus the way it never does when you are hedging. This is not recklessness. Recklessness is commitment without awareness. What I am describing is commitment with full awareness, commitment that knows the cost and does not flinch. Love needs no reason. Not because love is blind. Because love sees further than reason can follow, into a territory that reason maps as empty but that is, in fact, the fullest place a human being can stand. --- ## Garden — Essays (Full Content) ### The Correspondence: On Truth, Untruth, and Whether It Matters **Date:** 2026-04-13 | **Tags:** essay, philosophy, faith, correspondence Essay · 22 min read · 2026-04-13 --- Two friends write letters to each other about God, reason, and whether a conversation is possible when one of them prefers untruth to truth. *** Seneca wrote letters to Lucilius about death and the proper use of a life. He did not write them because Lucilius needed the advice. He wrote them because the act of addressing another human being, even across distance, even across disagreement, forced a precision that thinking alone never could. The sentence you write for someone else must be truer than the sentence you think for yourself, because someone else will hold it up to the light and see where it bends. Kierkegaard wrote to himself under invented names about faith and dread and the impossibility of being understood. Rilke wrote to a young poet about solitude, and the young poet kept those letters for the rest of his life because nothing anyone said to him in person ever came as close to the truth as those pages did. This essay is about a correspondence between two friends. Not philosophers. Not writers by trade. Two college students in New York who grew up in the same borough, sat in the same classrooms, and arrived at the same impossible questions from directions so different that when they finally tried to speak honestly to each other about what they believed, the conversation collapsed under the weight of its own sincerity. One of them believes that truth, even when it burns, even when it leaves you with nothing, is the only ground that will hold. The other suspects that a carefully built shelter, even one constructed from beautiful lies, might be more livable than the open field of bare reality, and that this preference is not weakness but a different kind of courage. They wrote letters to each other in April of 2026. I am one of them. *** ## I. The Boulder [#i-the-boulder] Ali wrote first. He opened with an accusation, gentle but unmistakable: that I had not written to him, and that my silence was either cowardice or something worse than cowardice, a kind of forgetting that is itself a choice. He was right about this, though not in the way he imagined. What followed was one of the most honest things I have ever read another person write. Ali described a boulder. Not a real boulder, but the one every thinking person carries in their mind: the great task, the thing that must be moved, the work that would define you if only you could bring yourself to begin it. He confessed that his deepest flaw was believing that understanding the boulder was the same as moving it. That if he could only measure its weight, map its surface, calculate the angle of the hill, then surely the pushing would follow naturally. Preparation as a form of permission. Study as a substitute for risk. But he saw through his own trick, and this is what made the letter extraordinary. He named the mechanism plainly: the analysis was not preparation. It was fear wearing the costume of diligence. Every hour spent studying the rock was an hour spent not climbing the hill, and the reason he would not climb was not that the summit was too far but that failure at the summit would force him to revise the story he told himself about who he was. "If I fail," he wrote, "I would have to reevaluate myself within my own personal hierarchy." I have read that sentence more times than I can count, and it does not soften. The boulder is not the obstacle. The self-concept is the obstacle. We do not avoid the work because it is hard. We avoid it because completing it, or failing at it, would give us information about ourselves that we are not ready to receive. And so we study. We prepare. We refine our plans. We do everything except the thing itself, and we call this wisdom. Camus told us that Sisyphus was happy. That the absurd hero finds meaning in the eternal push, the stone rolling back, the climb beginning again. But Ali was describing something Camus never addressed: the man who stands at the bottom of the hill and never pushes at all. Not because he has accepted absurdity, but because he has not yet found the courage to encounter it. Sisyphus at least knows the weight of his stone. Ali was describing the terror of discovering what your stone weighs. And then, in the most quietly devastating turn of the letter, Ali did the very thing he said he could not do. He pushed. Not the boulder. The pen. He wrote a letter he had not planned, using words he had not rehearsed, to a friend who had given him every reason to believe the effort was wasted. The letter was its own refutation. The man who declared himself paralyzed was, in the act of declaring it, moving. *** ## II. The Silence and the Circle [#ii-the-silence-and-the-circle] I did not write back for weeks. Not out of cruelty or neglect, but out of a resignation so deep it had stopped feeling like resignation and started feeling like clarity. I had spent years having the same conversation. About God, about faith, about the strange architecture of belief. With friends I loved, people whose intelligence I respected in every other domain, I would sit across a table or speak late into the night, reaching for the same thing: understanding. And more selfishly, that rarer thing, the experience of being understood. The conversations always ended in the same place. My friends would acknowledge that faith, by its own definition, transcends logic. That God is a paradox. That belief cannot be derived from reason, and that this is precisely what makes it belief rather than calculation. I understood this. I even found it beautiful, in the way that Kierkegaard found it beautiful when he wrote about Abraham on the mountain, the knight of faith who cannot explain his obedience and does not try. But then something would happen that I could never move past. Having established that their faith rests on a foundation that reason cannot touch, they would proceed to reason about everything else. One friend, after telling me that God is beyond logic, explained in the next breath that he had chosen Islam specifically because, after researching all the major religions, it was the most logically consistent. The most *reasonable*. "My faith is built on a foundation that transcends reason. But I chose this particular faith because it made the most sense." I sat with this for a long time. Not because it was wrong, exactly, but because it revealed something about the relationship between what we say we believe and how we actually navigate the world. The foundation is beyond reason, but the house built on that foundation is constructed with meticulous rationality. The leap of faith is taken once, in the dark, and then never again. Everything after the leap is careful, measured, sensible. Kierkegaard would have wept. I had this conversation with every close friend I had. Separately, in different rooms, in different seasons. And every time, with the eerie precision of a recurring dream, the conversation arrived at the same impasse. Reason would carry us to the edge, and then my friends would step off the cliff into faith, and then, standing in midair, they would resume reasoning as though the ground were still beneath them. And I, who had refused to step, would stand on the edge calling after them, and my voice would not reach. Ali was different. Or so I thought. We spoke during spring break, and for the first hour it was the most alive I had felt in a conversation in months. He was not defending a position. He was exploring one. He was willing to follow an argument even when it turned against him. And then he said something that stopped me: that truth is not necessarily greater than untruth. That a constructed paradise might be preferable to bare reality. That untruth, held with sufficient conviction, might be more livable than truth held with trembling hands. I recognized the argument. Nietzsche had made it, in the fourth section of *Beyond Good and Evil*: "The falseness of a judgment is for us not necessarily an objection to a judgment." The question is not whether a belief is true but whether it serves life. I knew the philosophy. But hearing it from a friend, spoken not as theory but as personal creed, something in me went cold. What is the point of a dialectic between two people if one of them holds that truth and falsehood are interchangeable? How can you build a conversation on a foundation that one party has already declared optional? I sat in silence on the phone for what felt like minutes, not because I had lost the argument, but because I was deciding whether the argument was worth continuing. Whether any conversation with a person who prefers beautiful illusions to harsh realities could ever arrive anywhere other than where it started. I decided not. I had decided this before, many times, with many people. And each time the decision carried the same quiet grief: one more person with whom the deepest conversation was impossible. Then we hung up the phone. And we both opened Instagram. Separately, in our separate rooms, in our separate silences. And we scrolled. *** ## III. The Feed and the Forgetting [#iii-the-feed-and-the-forgetting] I almost did not mention this. It seemed incidental, a footnote, the kind of detail you leave out when you are trying to build an argument about truth and meaning and the examined life. Two friends hang up after a philosophical conversation and browse social media. So what. Everyone does this. But the more I thought about it, the more I realized that this was not a footnote. This was the thesis. This was the only thing in the entire correspondence that neither of us could argue away or reframe or philosophize into something more flattering. We had just spent two hours in the most serious conversation either of us had attempted in months. We had talked about God and Nietzsche and the nature of truth and whether dialectic is possible between minds that hold different axioms. We had been, for a brief and precious window, the people we wished we were: thoughtful, earnest, unafraid to follow a question wherever it led. And then the conversation ended, and within thirty seconds, both of us were watching strangers perform dances for algorithmic approval. Every word we had said about truth dissolved. Every position we had defended evaporated. Not because the positions were wrong, but because they were not strong enough to survive the transition from conversation to silence. The feed appeared, and we obeyed it. Not reluctantly. Not after a struggle. Instantly. The way a muscle obeys a nerve. Kierkegaard wrote in *The Sickness Unto Death* that the most common form of despair is not the dramatic kind, not the anguish of a man who knows he is drowning, but the quiet kind: the despair of a man who does not know he is in despair at all. The man who is busy, comfortable, entertained. Who has never sat in a room alone with the question of what he truly believes and followed it all the way down to whatever waits at the bottom. That man, Kierkegaard says, is the most lost of all, because he does not know he is lost, and so he never searches for the way back. The doom scrolling was that despair. Not a dramatic failure. Not a moment of weakness. A revelation. A mirror held up to everything we had just said, showing us that we did not believe it. Or if we believed it, we did not believe it enough for it to matter more than the next fifteen seconds of content. This is what happens, I think, when you allow truth to become negotiable. When you hold it loosely, the way Ali suggested, as one option among several. You are left without an anchor, and the first current that comes along carries you wherever it wants. The Algorithm does not need you to disbelieve in truth. It only needs you to be indifferent to it for thirty seconds at a time. And thirty seconds, repeated across a lifetime, is all it takes. *** ## IV. Why I Wrote Anyway [#iv-why-i-wrote-anyway] So if I decided that the conversation was futile, if I concluded that dialectic with a man who prefers untruth to truth leads nowhere, why did I write? The honest answer is selfish. I wrote for myself. To see my own thoughts on a page, to discover whether they held together outside my head, to submit them to the only test that matters: the test of being read by someone who will not let you get away with imprecision. But there is another answer, one I did not expect and still do not fully understand. I had been reading Kierkegaard. Not about God, exactly, but about faith in the broader sense: the willingness to commit to something you cannot justify, something that reason alone would never produce. The leap. The knight of faith who lives in the finite world, who looks exactly like everyone else, but who has made a movement of the spirit that is invisible from the outside and incomprehensible from within. Everyone in my life who believed in God had said the same thing Kierkegaard said. But none of them said it the way he did. None of them made me feel, even for a moment, that the leap might be something other than surrender. Kierkegaard made it sound like the hardest thing a human being could do. Not the abandonment of reason, but its completion. The point at which reason recognizes its own limit and, rather than stopping, steps beyond itself into something it cannot name. In that moment of sympathy, or weakness, I wrote to Ali. I do not know if we will continue. I hope we do. Not because I believe we will resolve the questions we are circling. They have been circling for thousands of years, and minds far greater than ours have broken against them. I hope we continue because the act of writing to someone who disagrees with you, genuinely, from the foundations up, is one of the last honest things left in a world that has optimized honesty out of most of its conversations. When you speak, you perform. When you argue, you defend. But when you sit down to write a letter to someone you respect, knowing they will weigh each sentence against their own experience, knowing they will find the places where your logic bends and your courage fails, you cannot hide. The letter will betray you. Not cruelly, but completely. It will show you what you actually believe, as distinct from what you wish you believed, what sounds impressive, what wins arguments. The letter strips the walls from the building and shows the structure underneath, and if the structure is sound, it stands, and if it is not, it falls, and either way, you learn something that no amount of thinking in private could have taught you. Ali asked me to write. If not to him, then to myself. This is both. *** *Sources and influences: Kierkegaard, Fear and Trembling (1843) and The Sickness Unto Death (1849). Nietzsche, Beyond Good and Evil, section 4: "The falseness of a judgment is for us not necessarily an objection to a judgment." Seneca, Letters to Lucilius, Letter 40, on the relationship between writing and friendship. Plato, Phaedrus, 274b-278b, on the inferiority of writing to living dialogue. Camus, The Myth of Sisyphus (1942), on the absurd hero who knows his task and chooses it anyway.* --- ### The Cost of Looking Closely **Date:** 2026-04-10 | **Tags:** essay, philosophy, work, meaning Essay · 14 min read · 2026-04-10 --- There is a room I keep returning to in my memory, and every time I enter it, someone has already ruined it by mentioning the future. *** There are so many nights when the room is perfect. Everyone is laughing. Nobody is performing. The food on the table is something someone's mother made, and nobody has checked their phone in twenty minutes, and the conversation is about absolutely nothing, which is to say it is about everything that actually matters: the fact that we are here, together, young, alive, and not yet dissolved into the roles the world has picked out for us. I live for those rooms. I think most people do, whether they admit it or not. The room before someone brings up the future. Then someone brings up the future. Jobs. Careers. LinkedIn. An interview next week. A recruiter who reached out. And I feel something drain out of my body, not anxiety, something lower than anxiety, something that doesn't sit in the chest but leaves through the feet, as though whatever was keeping me upright just decided to stop. I go silent. Not physically. I'm still sitting there. My face is still arranged in something approximating attention. But I have left. I have been pulled backward into a place I cannot name, a place where every word being spoken sounds like a lock clicking shut. I find nothing in the world more meaningless to talk about. And the reason it fills me with such dread is not that work is hard, or that interviews are stressful, or that the job market is cruel. It is that we are all forced to spend the majority of our waking lives doing something none of us want to do, and we sit there discussing the details of our captivity as though choosing the right cell will set us free. Five minutes ago we were laughing about nothing, and that nothing was worth more than every job listing on the entire internet. *** ## The Room Before It Changed [#the-room-before-it-changed] Montaigne wrote, in his essays, that we are never at home; we are always beyond ourselves. Fear, desire, hope: they push us toward the future and steal from us the feeling and consideration of what is. He wrote that in the sixteenth century, in a tower in Bordeaux, surrounded by books and silence and the slow French countryside, and it is as true now as it was then. Maybe truer, because at least Montaigne could retreat to his tower. We carry the future in our pockets. It vibrates against our legs every forty-five seconds. I think about that every time the room changes. Five minutes ago we were home. We were right here, inside the moment, inside each other's company, inside the kind of presence that can't be manufactured or optimized or scheduled into a calendar. And then someone checked their phone, or someone mentioned a deadline, and now we are all somewhere else. Somewhere in the future. Somewhere we don't want to be. Rehearsing for lives none of us chose. The speed of the transition is what disturbs me most. It is not gradual. It is not a slow drift from presence to absence. It is instantaneous, like a light being switched off. One second the room is alive, and the next second everyone is performing a version of themselves they learned from watching adults who were also performing. The ambitious one talks about opportunities. The practical one talks about salary ranges. The anxious one talks about backup plans. And I sit there watching the room I loved disappear behind a wall of language that means nothing to anyone in it, and I cannot figure out how to say what I want to say without sounding like I have lost my mind. What I want to say is: we were just happy. Can we go back. Can we stay there. Can we talk about nothing for the rest of the night and let the future arrive on its own schedule instead of dragging it into every conversation like a guest nobody invited. But I never say it. I just go quiet. And eventually someone asks if I'm okay, and I say I'm fine, and we move on. *** ## The Testimony of the Body [#the-testimony-of-the-body] We spent four years in college studying things we did not want to learn. The people who say they did are lying to themselves, or at the very least, me and my friends are, because we skipped roughly eighty percent of our lectures across four years of university. Eighty percent. That is not a rough patch. That is not a bad semester. That is your body screaming the truth for four consecutive years while your mouth keeps saying something different. It does not matter what we say we believe. It matters what we do. Our alarms went off and we turned them off. Our legs carried us past the lecture hall. Our bodies voted, every single morning, against the life we keep telling everyone we are building. That is not laziness. That is testimony. That is the truest language we have, the language of action, saying plainly what the language of speech is too polite or too frightened to say: I do not want this. I have never wanted this. I am doing it because I was told I had no other option, and I believed it, and now I am four years deep and the only thing I have learned is how to pretend I chose this. Whenever I bring any of this up, whenever I try to get my friends to look at the gap between what we say and what we actually do, they nod. They agree. They exhale this long, heavy sigh that I have heard so many times now it has become its own language. The sigh that means: I know. I know. There is nothing we can do. And then they go right back to talking about the same things they do not care about but have been trained to act like they care about. They spend their free hours rehearsing for the same cage they just described to me in perfect detail. Nothing changes. Nothing ever changes. They just sigh and keep building the walls from the inside. *** ## Closed Loops [#closed-loops] I worked at a coffee shop once. I will be honest: it was easier and more enjoyable than what I do now as a software developer. The work was monotonous, yes, the same drinks over and over. But you can learn to love repetition. There is something almost meditative about it, your hands moving without your mind needing to direct them, the body falling into a rhythm that asks nothing of the soul. Except the process was so refined and systematized that it killed even that small grace. Every motion was optimized for speed, not craft. And the product I was making was, to put it plainly, poison. Ultraprocessed sugar and chemicals engineered to create dependency and leave people feeling worse than before they walked in. They came every morning, the same tired faces, the same orders, the same eyes that did not quite focus until the caffeine hit. And they handed me their money for the thing that was slowly hollowing them out, and I handed them the cup, and they drank it in their cars on the way to jobs they hated, and they earned just enough to come back tomorrow and buy more. A closed loop. People hurting each other in the most ordinary, polite way. And my hands were in it. Seneca wrote in On the Shortness of Life that it is not that we have a short time to live, but that we waste much of it. Life is long enough, he said, and a sufficiently generous amount has been given to us for the highest achievements if it were all well invested. But when it is squandered in heedless luxury and spent on no good activity, we are forced at last by death's final constraint to realize it has passed away before we knew it was passing. I read that when I was nineteen, and I thought: he is right. He is exactly right. And then I went to work the next morning and made someone a caramel swirl iced coffee and tried not to think about it. That is the cruelty of understanding without action. You see the cage clearly. You can describe its dimensions, its materials, the precise angle of the light that comes through its bars. And then you sit down inside it and wait for your shift to end. Because seeing the cage does not open the cage. Knowing you are wasting your life does not stop you from wasting it. It just makes the wasting hurt more. *** ## The Elegant Bandaid [#the-elegant-bandaid] What really makes me angry, what I genuinely cannot get past, is the architecture of modern work itself. Not just that work is tedious or underpaid or soul-crushing, but that so much of it is dedicated to solving problems that should not exist in the first place. Why would I want to build an app that helps people manage their insurance cases more efficiently when the entire reason the existing software is so terrible is that the system was designed by people who will never have to use it? I am solving a symptom. I am patching a patch. I am building a tool to navigate a broken system instead of asking why the system is broken. And the answer to why is always the same: because the brokenness is profitable. The dysfunction is the business model. And I am supposed to call my bandaid disruption. That is what most of the technology industry is, if we are being honest. Not innovation. Just increasingly elegant ways to cope with increasingly unnecessary problems. An entire economy built on managing the damage of other economies. We build apps to help people find affordable healthcare in a country that made healthcare unaffordable on purpose. We build platforms to help workers find gigs in a labor market that destroyed stable employment by design. We build meditation apps so people can recover from the anxiety created by the other apps we built. The whole thing is a serpent eating its own tail, and we call it progress, and we give each other awards for the most aesthetically pleasing segment of tail. *** ## The Question Nobody Answers [#the-question-nobody-answers] When I say all of this to my friends, they ask the obvious question: What is the alternative? You have to work. What else are you going to do? And they are right to ask. Because I do not have one. They say you need money. I say for what. They say to travel, to live, to experience things. And I say: but think about it. You are working all these years for a few moments of joy that you cannot even fully enjoy because you know you will have to go back in a couple of days. The joy has a return ticket. It comes with an expiration date stapled to the itinerary. And also: why do you need the money? If you look honestly at all these experiences you are saving up for, what do they actually give you? You want to travel the world. Why? So you can talk to different cultures. Eat different foods. Experience nature. But why can you not do that where you are? Why does transcendence require a plane ticket? What is it about a foreign country that your own neighborhood could not give you if you looked at it with even half the openness you would bring to a place you have never been? If the end goal is joy, then why do you care how you arrive at it? A feeling does not know what you paid for it. It does not check your coordinates. If joy is the destination, then any road that takes you there is the right road, and you do not need the expensive one. My friends look at me like I am being naive when I say these things. And maybe I am. But the math does not work, and everyone knows it. We spend our twenties earning the right to our thirties. Our thirties earning our forties. And somewhere in the middle, the thing we were saving up for becomes the thing we no longer have the body or the energy or the friendships to enjoy. That math has never worked. Not for us. Not for our parents. Not for their parents. Not for anyone in the history of working. And we all know this, and we keep going anyway, because the only thing scarier than admitting the math is broken is having nothing to replace it with. *** ## The Weight That Stays [#the-weight-that-stays] Now here is where I have to be honest in a way that actually costs me something. I say all of these things, but I myself have not been able to let go. I still need money. I still live inside the system I am criticizing. And the real reason I cannot leave, the one that sits heaviest, is my parents. I want to give them a good life. But their version of a good life and mine are not the same. They are still inside the framework of the system. Stability, security, a respectable title, a career their community can nod at. And I understand why. They came from a place where not having these things did not mean discomfort; it meant danger. Their caution is not conservatism. It is scar tissue. It is the residue of a life harder than anything I have known. I have no right to dismiss what they want. They earned their expectations through a kind of suffering I have only heard about in stories told over dinner, the kind of stories that get quieter as they approach the worst parts. My father asked me last week how the applications were going. He put his fork down when he said it, which means he had been thinking about it all day, carrying the question around like something fragile, waiting for the right moment to set it on the table between us. I said fine. He mentioned someone else's son who just got an offer at a company whose name I recognized. We both knew what he was really saying. And I sat there trying to figure out how to tell him that his version of a good life and mine are not the same without it sounding like I was throwing away everything he sacrificed for me. I could not figure it out. So I said fine again. And we kept eating. Seneca, in the same text, wrote about the old man on his deathbed who realizes he has been preparing to live rather than living. That the years slipped away not in dramatic catastrophe but in incremental postponement, each day traded for the promise of a better day that never arrived. I think about my father when I read that passage. Not because he is dying, but because I can see the same arithmetic working its way through my own life, and I do not know how to stop it without breaking the people I love. If I leave the cave, I cannot leave without them. I do not want to. I want to take them with me. But they do not see the sunlight the way I do. They see exposure. They see risk. They see the open field where anything can happen, and they remember a time when anything meant the worst thing. *** ## The Hypocrite's Prayer [#the-hypocrites-prayer] And here is the part that really twists the knife. If I cannot do any of this myself, if I cannot follow my own philosophy, why am I telling my friends to? Why do I go quiet in that room like it means something? I wake up past noon. I reach for my phone and lose hours to nothing. I skip training. I stay up until four in the morning and promise myself tomorrow will be different in the exact same voice I have been using every night for three years. And it never is. The voice does not change. The promise does not change. The morning does not change. Only the date changes, and even that starts to blur. So either I do not really believe what I say, which makes me a hypocrite. Or I do believe it and I cannot act on it, which makes me a coward. I am not sure which is worse. Probably the second. At least the first one has an excuse. Thoreau wrote that the mass of men lead lives of quiet desperation. What is called resignation is confirmed desperation. He wrote that nearly two hundred years ago, sitting by a pond in Massachusetts, living deliberately, stripping life down to its essentials to see whether he could learn what it had to teach. The only thing that has changed since Thoreau is that we have rebranded the desperation as hustle culture and the resignation as a career path and somehow made the cage aspirational. We have turned quiet desperation into a LinkedIn post with a blue checkmark and fourteen thousand reactions. But I refuse to believe this is all there is. I refuse to accept that the highest use of the one life I get is to spend it solving problems that should not exist, building tools to navigate systems that were broken on purpose, trading the years where I am most alive for the promise that someday, eventually, I will get to enjoy being tired. That is not a life. That is a very long, very respectable way to disappear. *** ## The Room I Keep Returning To [#the-room-i-keep-returning-to] I do not know what the alternative looks like. Not fully. Not in the way that would satisfy anyone who asks the question seriously. I cannot draw a map from here to there. I cannot promise it works. I cannot even promise I will follow through, given my record, given the distance between what I say at two in the morning and what I do at two in the afternoon. But I know the dread I feel in that room when someone brings up careers is not the disease. The dread is the diagnosis. It is the last honest part of me, the part that still refuses to play along, the part that hears the word "opportunity" and translates it correctly as "a new way to spend your life on something you do not care about." And every time I go quiet, it is not because I have nothing to say. It is because what I have to say is so much larger than the room, and I do not know how to get it out without sounding ungrateful or naive or broken, so I just hold it, like something too hot to set down and too heavy to carry. Montaigne left public life at thirty-eight. He locked himself in a tower with his books and spent twenty years writing what he called essais, which just means attempts. Tries. He did not have answers. He had questions and the willingness to sit with them for as long as they needed. He failed at most of what he tried to figure out. But the trying was the living. The attempt was the point. The tower was not a retreat from the world; it was the first honest confrontation with it. I do not have a tower. I have a laptop and a bedroom that needs cleaning. But the principle might be the same. I think about that room a lot. The one from before someone checked their phone. The laughing. The nothing we were talking about that meant everything. The warmth that no one had to manufacture or earn or schedule. I think that is what I am trying to protect. Not a lifestyle. Not a philosophy. Not a five-year plan. Just that. The room before it changed. The twenty minutes where nobody was a candidate and everybody was a person and the only thing that mattered was that we were there, and that we were there together, and that the food was good, and that the laughter came easily, and that no one had anywhere else to be. I do not know if you can build a life around twenty minutes. But I would rather spend my years trying than spend them building someone else's cage and calling it a career. Thoreau went to the woods because he wished to live deliberately, to front only the essential facts of life, and see if he could not learn what it had to teach, and not, when he came to die, discover that he had not lived. I have not gone to the woods. I have not gone anywhere. But I am beginning to suspect that the essential facts of life are not waiting in some future I have to earn. They were in the room the whole time, in the twenty minutes before somebody changed the subject, in the laughter that required nothing, in the silence that followed when everyone was content and no one needed to fill it. Tomorrow I am going to do one thing I actually want to do. And if nothing falls apart, I will do it again the day after. And again. Until either something real stops me or a life starts to take shape around the trying. That is not a plan. But I think it might be the start of one. *** *Sources and influences: Montaigne, Essays (1580), on the habit of living beyond ourselves. Seneca, On the Shortness of Life (49 AD), on squandered time and postponed living. Thoreau, Walden (1854), on quiet desperation and deliberate life. Marcus Aurelius, Meditations, on the sufficiency of the inner life.* --- ### Systems Are Lossy Compression **Date:** 2026-03-15 | **Tags:** essay, philosophy, systems, freedom Essay · 17 min read · 2026-03-15 --- Every system you adopt is a compression algorithm applied to reality. Compression always loses data. The question is what you are willing to lose. *** It was a Sunday afternoon in February, and I was 250 lines deep into an architectural plan for my life. Teams, initiatives, cycles, labels, daily workflows, weekly reviews, quarterly retrospectives. I had color-coded categories for fitness, philosophy, career, relationships, side projects. I had velocity metrics. I was going to track exactly how I wanted to get to where I wanted to get to. The whole thing hummed with the quiet satisfaction of a cathedral under construction. I could feel the order settling over the chaos of my week like a weighted blanket. This was it. This was the system that would finally make me the person I kept meaning to become. By Tuesday, it was dead. Not dramatically. Not with a declaration or a crisis. It just stopped mattering. I woke up, opened the app, looked at the elaborate scaffolding I had built, and felt nothing. Not resistance, exactly. More like the recognition you get when you see a photograph of a meal you ate last week: yes, that happened. It is no longer relevant. I closed the app and went about my day the way I always do, which is to say, by doing whatever felt most alive in that moment, following the thread of whatever problem or obsession had its hooks in me, ignoring everything I had meticulously planned. Two days. Two hundred and fifty lines of infrastructure. And the thing that killed it was not laziness or lack of discipline. It was something more unsettling. I had built the system, and in the act of building it, I had already received everything it had to offer. The system was never going to organize my life. The system was itself the experience of feeling organized. Once that feeling faded, the system had no remaining function. It was scaffolding with no building inside. This has happened to me more times than I can count. The oscillation is predictable: feel unstructured, build elaborate system, feel productive, realize the system is not doing the work, abandon system, feel unstructured again. Lather, rinse, repeat. For a long time I thought this was a personal failing, some deficiency of follow-through or attention. But I have come to believe it is something else entirely. I think I keep building systems and abandoning them because I can feel, at some inarticulate level, that every system is a lie. A useful lie, maybe. A necessary lie, sometimes. But a lie nonetheless. The question I want to explore is not whether systems are good or bad. That is a boring question with a boring answer. The question is: what does every system cost you? What do you lose when you adopt one? And how would your life change if you understood, really understood, that every framework you have ever believed in is missing most of the picture? *** ## The Compression Metaphor [#the-compression-metaphor] Claude Shannon, working at Bell Labs in the late 1940s, gave us the mathematical framework for understanding information. His insight was deceptively simple: communication is the process of reducing uncertainty. Every message, every signal, every piece of data is a selection from a set of possibilities. The more possibilities you eliminate, the more information you have transmitted. But Shannon also understood something darker, something that tends to get lost when people invoke information theory at cocktail parties. There are two kinds of compression: lossless and lossy. Lossless compression preserves everything. You can compress a file and decompress it and get back exactly what you started with, bit for bit, nothing missing. Lossy compression is different. Lossy compression makes a bet. It looks at the data, decides what matters and what does not, throws away what it deems unnecessary, and gives you back something smaller, something manageable, something that looks close enough to the original that you might not notice the difference. But the difference is there. The thrown-away data is gone forever. You cannot get it back. Every photograph you have ever taken on your phone is a JPEG, which means every photograph you have ever taken is a lossy compression of what your eyes actually saw. The algorithm decided which gradations of color were imperceptible to the human eye and discarded them. The sunset you photographed last summer had thousands of subtle tonal shifts that your file deleted in the name of a manageable file size. You look at the photo and think you are looking at what happened. You are not. You are looking at what the algorithm decided was worth keeping. This is the metaphor I cannot stop thinking about, because I believe it applies to something far larger than digital photography. I believe every system humans have ever built, every framework, every ideology, every institution, every religion, every economic model, every philosophical tradition, even language itself, is a lossy compression algorithm applied to reality. Reality is the RAW file. Infinite resolution. Unlimited bandwidth. More data than any mind can hold. And so we compress. We have to. A human being standing in the middle of uncompressed reality would be paralyzed, overwhelmed, unable to act. So we build models. We create frameworks. We adopt systems. And every single one of them, without exception, throws data away. Religion compresses morality into commandments. Ten rules, or five pillars, or an eightfold path. Take the staggering complexity of human ethical life, the infinite contextual gradations of right and wrong, the way the moral weight of an action shifts depending on who is doing it and to whom and when and why, and reduce it to a list. A magnificent list, sometimes. A list that has guided billions of people through the darkness of uncertainty. But a list that, by its nature, cannot contain what it replaced. The commandment "thou shalt not kill" is a compression of a reality in which the morality of killing depends on a thousand factors the commandment cannot encode. Capitalism compresses value into price. Take everything a thing is, everything it means, everything it costs the earth and the worker and the community, and reduce it to a number. The price of a bottle of water at an airport is $6. That number has compressed into itself the aquifer depletion, the plastic manufacturing, the shipping logistics, the labor conditions, the marketing budget, the rent on the retail space, and your desperation because you are dehydrated and past security. All of that complexity, flattened into a number on a sticker. The price is not wrong, exactly. It is just lossy. It has thrown away most of the information. Academia compresses knowledge into credentials. Take everything a person knows, everything they have struggled to understand, every late night with a difficult text, every moment of genuine intellectual transformation, and reduce it to a line on a resume. Bachelor of Arts. Master of Science. PhD. The credential is a compression that allows institutions to sort people efficiently. But it has lost the actual knowledge in the process. I have met people with doctorates who have forgotten more than they remember, and I have met people with no formal education whose understanding of their domain would embarrass a tenured professor. The credential kept the label and threw away the substance. Language itself, the tool I am using right now to reach you, is perhaps the most fundamental compression of all. Alfred Korzybski spent his career trying to make people understand this. "The map is not the territory," he said, and people nodded and thought they understood, and then went right back to confusing their descriptions of reality with reality itself. Every word is a compression. The word "grief" is a container for an experience so vast, so multidimensional, so physically and psychologically and spiritually overwhelming that no word could ever hold it. But we say "grief" and we nod and we move on, as if the word were the thing. It is not. The word is the JPEG. The experience is the RAW file. And you cannot decompress the word back into the experience. *** ## The Lens You Cannot See Through [#the-lens-you-cannot-see-through] Here is where it gets dangerous. When you adopt a system, a framework, a way of seeing, something subtle happens. The compression algorithm does not announce itself as a compression algorithm. It presents itself as vision. As clarity. As the way things actually are. You do not experience yourself as wearing tinted glasses. You experience the world as being the color of the tint. Jean Baudrillard understood this better than almost anyone. In "Simulacra and Simulation," he argued that our models of reality have, in many cases, replaced reality entirely. The map has not just been confused with the territory; the map has consumed the territory. We live in a world of representations so thick, so layered, so self-referential, that the original reality they were supposed to represent has become irrelevant. The simulation is more real than the real. Baudrillard called this hyperreality, and I think about it every time I watch someone check their phone to see how many steps they took on a walk they were apparently not present for. This is not an abstract philosophical problem. This is the water you are swimming in right now. Consider: a Marxist walks into a room and sees class dynamics. A Freudian walks into the same room and sees libidinal currents and defense mechanisms. An economist sees supply and demand. A therapist sees attachment styles. A sociologist sees power structures. A devout Christian sees souls in various states of grace. They are all looking at the same room. They are all seeing something real. But none of them is seeing the room. They are seeing the room through the compression algorithm they have internalized, and the algorithm, by its nature, has thrown away everything it was not designed to detect. I notice this in myself constantly. When I am deep in a Nietzsche phase, everything becomes a question of power. Who is asserting, who is submitting, whose morality is serving whose interests. When I am reading Plato, everything becomes a question of forms and ideals and the distance between the thing and its essence. When I am training jiu-jitsu, I walk through the world seeing frames and levers and balance points, reading bodies the way a musician reads a score. Each lens reveals something real. Each lens hides everything else. The insidious part is that the more sophisticated the system, the more invisible its compressions become. A crude ideology is easy to see through because it obviously does not account for everything. But a truly powerful framework, one that has been refined over centuries by brilliant minds, can feel so comprehensive that you forget it is a framework at all. You mistake the map for the territory. You confuse the compression with the original data. Nietzsche saw this with terrifying clarity. In "Beyond Good and Evil," he argued that every philosophy is a kind of involuntary autobiography, a confession of its creator's drives and prejudices dressed up in the language of universal truth. The philosopher does not discover truth. The philosopher compresses reality according to the shape of their own nature and then calls the result "the way things are." Nietzsche was honest enough to include himself in this indictment. His philosophy of the will to power was, by his own implicit admission, the compression algorithm of a man who valued strength and despised weakness. It reveals what it reveals. It hides what it hides. And this is the trap. Not that systems are wrong. They are not wrong. They are lossy. The Marxist really does see class dynamics, because class dynamics are real. The therapist really does see attachment styles, because attachment styles are real. The problem is not that the lens shows you something false. The problem is that the lens shows you something true and in doing so convinces you that what it shows is all there is. Partial truth masquerading as the whole picture. That is the most dangerous kind of distortion, because you never think to question it. *** ## The Paradox on the Mat [#the-paradox-on-the-mat] I train Brazilian jiu-jitsu, and it has taught me more about this paradox than any book. When you start jiu-jitsu as a white belt, you have no system. You have no framework, no technique, no model. You just have your body and another body and gravity and panic. You are not free. This is important to understand. The absence of a system is not freedom. The absence of a system is drowning. You flail. You use strength where you should use leverage. You hold your breath. You make the same mistakes over and over because you do not even have the vocabulary to name what is happening to you, let alone the tools to respond to it. So you learn technique. You learn a system. You learn that when someone is in your guard, you control the distance with your knees. You learn that an armbar is not about pulling the arm but about lifting the hips. You learn that a sweep works because you remove a post while applying force in the direction of the missing support. Each technique is a compression. It takes the infinite complexity of two bodies entangled on the ground and reduces it to a set of principles: control the head, control the hips, create angles, break grips, maintain frames. And here is the paradox, the one that I think contains the answer to the question I have been circling. At the intermediate level, the system helps. It gives you a framework for reading the chaos. Where you once saw only a tangle of limbs, you now see a guard pass or a submission entry or a sweep setup. The system works. But it also constrains. You become predictable, mechanical. You execute techniques instead of responding to the person in front of you. You are doing jiu-jitsu the way a music student plays scales: correctly, competently, lifelessly. You have traded the white belt's formless panic for the blue belt's rigid competence, and neither one is freedom. But then something happens at the higher levels, something that I have seen in black belts and that I am only beginning to glimpse in myself. The system dissolves. Not because the black belt has rejected technique. Not because they have decided that systems are prisons and returned to formless flailing. The opposite. They have internalized so much technique, absorbed so many systems, drilled so many patterns, that the systems have become invisible. The techniques are no longer things they do. The techniques are things they are. And because the system has been absorbed into the body itself, the mind is free again. The black belt rolls with the spontaneity of a white belt but with the precision of someone who has ten thousand hours of encoded pattern recognition operating below conscious thought. Shunryu Suzuki, the Zen teacher, wrote about this in "Zen Mind, Beginner's Mind." He said, "In the beginner's mind there are many possibilities, but in the expert's mind there are few." This is often quoted as a cute aphorism about staying open-minded. It is not cute. It is devastating. The beginner sees everything because they have no system to filter their perception. The expert sees almost nothing because their system has become so efficient at compression that it has eliminated everything outside its parameters. The master, the true master, has somehow returned to beginner's mind, not by unlearning what they know but by learning so thoroughly that knowledge becomes transparent. They see through the system rather than with it. The compression algorithm is still running, but they can see the data it is discarding, and they can choose, moment to moment, whether to trust the compression or reach for the raw file. This is what happened to me on that Tuesday morning when I abandoned my 250-line productivity system. I was not being lazy. I was not failing to follow through. I was, at some level I could not yet articulate, recognizing that the system was showing me a compressed version of my own life and calling it the complete picture. And the compressed version, with its cycles and labels and velocity metrics, had thrown away the thing that actually makes my life work: the ability to follow what is alive, to chase the thread that pulls, to trust the animal intelligence that knows what matters before the conscious mind has finished building its spreadsheet. *** ## Becoming Who You Are [#becoming-who-you-are] Nietzsche's most famous imperative is usually translated as "become who you are." It sounds paradoxical, almost nonsensical. How can you become what you already are? But I think the paradox dissolves when you understand it through the lens of compression. You are born as the RAW file. Infinite resolution. Unlimited potential. Undifferentiated. And then the compressions begin. Your family gives you your first system: their values, their fears, their model of what a good life looks like. School gives you another: knowledge is what fits on a test. Religion gives you another, or atheism does, which is just a different compression with different losses. Your culture gives you a thousand more, so quietly that you never notice them being installed. By the time you are an adult, you are layers of compression all the way down. You do not experience yourself as wearing masks. You experience the masks as your face. "Become who you are" is the instruction to decompress. Not to reject all systems, which would be just another system, the system of anti-system, compressing reality through the filter of perpetual refusal. But to recognize, with excruciating honesty, that every system you have adopted, every framework you believe in, every lens you see through, is lossy. It has cost you something. It has thrown away data about who you are and what reality is in order to give you a manageable, actionable, navigable model. The question is not whether to use systems. You have to use systems. The white belt is not free. The person without language is not free. The person without any framework for understanding the world is not free. They are drowning in raw data, paralyzed by the infinite bandwidth of unmediated reality. You need compression to function. You need maps to navigate. You need models to decide. The question is whether you know you are using them. Korzybski spent decades trying to teach people to add the words "to me" or "as I see it" to every statement. Not as a social nicety, but as a fundamental epistemological correction. "This is a good movie" is a statement that confuses the map with the territory. "This is a good movie to me, given my particular history and aesthetic training and current emotional state" is a statement that acknowledges the compression. It is longer, uglier, less satisfying. It is also closer to the truth. Korzybski did not succeed in changing how people talk. But he was right about why they should. I think about this when I catch myself in the grip of a system. When I am deep in Nietzsche and everything becomes a power dynamic. When I am deep in productivity thinking and my life becomes a set of optimizable inputs and outputs. When I am deep in philosophy and every experience becomes raw material for an argument rather than something to be lived. In each case, the system is doing what systems do: compressing reality into something I can work with. And in each case, the system is costing me something: the parts of reality it was not designed to capture. The most dangerous moment is when I forget this. When the system becomes so familiar, so internalized, so total, that I lose the ability to see around it. When I stop being a person who uses a framework and start being a person who lives inside one. Baudrillard would say that is the moment the simulation becomes more real than the real. I would say it is the moment you mistake the JPEG for the sunset. *** ## The Resolution That Is Not a Resolution [#the-resolution-that-is-not-a-resolution] I want to offer a clean ending here. A framework for thinking about frameworks. A system for evaluating systems. But that would be exactly the kind of trap I have been describing, and I refuse to set it. So instead, here is what I have learned, provisionally, lossily, with full awareness that this too is a compression. Structure serves freedom. That is the lesson of jiu-jitsu, of music, of language, of every discipline that requires years of systematic practice before spontaneity becomes possible. You cannot be free without form. The white belt is not free. The person who rejects all systems is not liberated; they are lost. You need technique. You need vocabulary. You need frameworks. You need maps. But, and this is the part that matters, the structure is a servant, not a master. The moment the structure becomes the point, the moment you are serving the system instead of the system serving you, something has gone wrong. The productivity app that makes you feel productive without producing anything. The philosophical framework that makes you feel wise without deepening your understanding. The religious practice that makes you feel righteous without making you more compassionate. The economic model that makes you feel rational without making you more humane. In each case, the system has stopped compressing reality and started replacing it. Here is the test I have started applying, and it is the only test I trust. Can you drop the framework and still see clearly? If you removed the Marxist lens, could you still see injustice? If you removed the therapeutic vocabulary, could you still feel empathy? If you removed the religious framework, could you still act morally? If you removed the productivity system, could you still do meaningful work? If the answer is yes, the system is serving you. It is a tool you are holding. You can put it down. You can pick up a different one. You can use your bare hands. If the answer is no, if removing the framework would leave you unable to see or feel or act, then the system has consumed you. You are no longer using it. It is using you. You have become a function of the algorithm, processing reality through a compression you can no longer distinguish from the data itself. I abandoned my 250-line productivity system on a Tuesday morning, and my life did not collapse. I continued to do the work that mattered. I continued to train, to read, to write, to build, to think. The things that were real before the system remained real after it. The things that were only real inside the system vanished like morning fog. That tells me something. It tells me the system was not supporting the work. It was simulating the feeling of support. I still build systems. I still adopt frameworks. I still read philosophy and internalize its lenses and see the world through them. I am not anti-system. That would be as naive as being pro-system. I am trying, with varying degrees of success, to hold every system loosely. To remember that the map is not the territory. To remember that the JPEG has deleted colors I can no longer see. To remember that the commandment, the price tag, the credential, the diagnosis, the philosophical argument, the political ideology, the productivity framework, the training methodology, and even the sentence you are reading right now are all compressions. They are all lossy. They have all thrown something away. The question is not whether you can live without compression. You cannot. The question is whether you know what you have lost. Whether you can feel the absent data like a phantom limb. Whether you can hold your favorite framework up to the light and see the gaps in it and love it anyway, not because it is complete, but because it is yours, and it is the best compression you have found so far, and tomorrow you might find a better one. That is what I think it means to become who you are. Not to find the right system. Not to reject all systems. But to move through systems the way a black belt moves through techniques: fluidly, spontaneously, without clinging, using each one fully and then releasing it, always returning to the ground truth of your own uncompressed experience. The Sunday system was beautiful. The Tuesday abandon was wise. The oscillation is not a failure. The oscillation is the signal of a mind that refuses to mistake any compression for the whole. I do not know what the RAW file of my life looks like. I am not sure anyone ever sees theirs. But I know it is there, underneath every system I build and every system I abandon, vast and uncompressed and waiting, the territory that no map will ever fully capture. And I think that is enough. Not to see it. Just to know it is there. Just to feel the weight of everything the systems have thrown away, and to keep reaching for it, one lossy approximation at a time. --- ### An Attempt to Find the Axioms of Jiu-Jitsu **Date:** 2026-02-20 | **Tags:** essay, bjj, philosophy, first-principles Essay · 14 min read · 2026-02-20 --- What if grappling has first principles the way mathematics does? Not techniques, but axioms. The irreducible truths from which everything else follows. *** *** There is a moment, about forty seconds into a roll with someone better than you, when your breathing changes. Not because you are tired. Because you have run out of ideas. Your partner has collapsed your frames, flattened your hip to the mat, and threaded a knee through a gap you did not know existed. You are trying to remember a technique, some escape you drilled last Tuesday, but the weight on your chest is compressing your thoughts along with your ribs. You cannot think your way through this. The body has to answer, or nothing will. I remember the exact roll when something shifted. It was a Thursday evening, late class, and I was working from bottom against a training partner who outweighed me by thirty pounds. He passed my guard cleanly and settled into side control with the patience of a man who had nowhere else to be. I fought the crossface. I bridged. I shrimped. Nothing. Every movement I made was a word, a single disconnected word, when what I needed was a sentence. And then, without deciding to, I stopped fighting the position and started fighting the distance. I wedged a knee inside, not to escape but to create a frame. The frame bought me an inch. The inch let me turn. The turn restored my guard. I had not performed a technique. I had obeyed a principle. That night, driving home with my gi still damp, I turned the moment over in my mind. What had I actually done? Not a specific escape. Not a move with a name. I had recognized that the problem was not the position but the distance, and that controlling distance was more fundamental than any escape sequence. It was the grammar beneath the words. And I began to wonder: how many of these grammatical rules are there? How deep does it go? What if grappling, like geometry, has axioms? *** ## Why Axioms Matter [#why-axioms-matter] In the third century BCE, Euclid sat down and performed one of the great intellectual feats in human history. He looked at the sprawling, accumulated knowledge of Greek geometry, all its theorems and constructions and proofs, and asked a radical question: what is the smallest set of truths from which all of this follows? The answer was five. Five postulates. From these, and these alone, every theorem in the *Elements* could be derived. A straight line can be drawn between any two points. A circle can be drawn with any center and radius. All right angles are equal. And so on. Five seeds from which the entire forest of Euclidean geometry grows. The elegance of this is not mathematical. It is philosophical. Euclid demonstrated that an apparently infinite domain of knowledge could be reduced to a finite set of irreducible truths. The rest is consequence. The rest is weather. If you understand the axioms, you understand the system, even the parts of it you have never seen before. I have been training Brazilian jiu-jitsu for years now, and the art often feels infinite. There are thousands of techniques. Hundreds of positions. An ever-expanding taxonomy of guards, passes, submissions, transitions, and escapes. You can spend a decade on the bottom game alone and still encounter positions you have never seen. The instructional industry is a content machine, producing new material faster than any human could absorb it. And yet, on the mat, the practitioners who move with the most clarity are not the ones who know the most techniques. They are the ones who seem to understand something underneath the techniques, something structural, something that lets them improvise in real time because they grasp the logic of the art rather than its vocabulary. So the question haunts me: can jiu-jitsu be axiomatized? Can we identify a small, finite set of principles from which the rest of the art logically follows? Not a list of tips. Not a collection of heuristics. Axioms. Truths so fundamental that denying any one of them would cause the system to collapse. I want to be precise about what I mean. An axiom is not a technique. "Armbar from closed guard" is not an axiom. It is a theorem, a specific consequence that follows from deeper truths about leverage, angle, and the structure of the human arm. An axiom is not a strategy, either. "Be on top" is a strategy, a preference that admits exceptions. An axiom is a claim about the nature of the art itself, a statement so basic that it cannot be reduced further. Position before submission. Pressure creates reaction. The body is a system of levers. These feel like candidates. Whether they hold up is what I want to find out. *** ## The Candidate Axioms [#the-candidate-axioms] ### 1. Position Before Submission [#1-position-before-submission] This is the first thing you learn and the last thing you understand. I remember watching a blue belt roll with our instructor, a compact, quiet man who moved like water finding the lowest point in a landscape. The blue belt was hunting. Arms everywhere. Darting for necks, reaching for wrists, trying to snatch a submission from whatever position he happened to be in. The instructor simply moved through him. Not around him. Through him. He advanced position with such calm inevitability that the blue belt's attacks became irrelevant. Mount. Then back control. Then a choke that seemed to arrive as an afterthought, the way a period arrives at the end of a sentence you already understood. Position before submission means that where you are is more important than what you do. It means that the hierarchy of positions, back control above mount above side control above guard above bottom, is not a suggestion but a law. Violate it and you may still win, the way a gambler may still profit, but you are playing against the structure of the game itself. The philosophical implication cuts deep. It suggests that in any complex system, the conditions you establish matter more than the actions you take. Preparation precedes execution. Context determines outcome. Whitehead warned against "the fallacy of misplaced concreteness," the error of treating an abstraction as if it were the real thing. A submission is concrete. You can see it, feel it, tap to it. But the position that made it inevitable is abstract, a relationship of angles and weight and frames that exists as a pattern before it exists as a choke. The concreteness of the submission is a seduction. The abstraction of the position is the truth. ### 2. Pressure Creates Reaction [#2-pressure-creates-reaction] Your body is treacherous. It will betray your strategy in service of its panic. There is a particular kind of pressure in jiu-jitsu that has no equivalent in daily life. Not pain, exactly. Compression. A good top player does not pin you to the mat. He makes the mat disappear. You cannot feel the floor beneath you because all you can feel is the weight above you, distributed with sadistic precision across your diaphragm, your face, the hinge of your jaw. And your body, that magnificent, stupid animal, will do anything to relieve the pressure. It will give up an arm. It will turn its back. It will trade a defensible position for a single full breath. The top player knows this. He is not attacking you. He is creating a stimulus and waiting for your body to provide the response he wants. This is the second axiom: pressure creates reaction, and reaction creates opportunity. It is the engine of the entire art. Without it, jiu-jitsu would be a game of pure technique, two players selecting moves from a database. With it, jiu-jitsu becomes a conversation between nervous systems, a game in which the most important information is not what your opponent is doing but what his body is about to do against his will. Musashi understood this. In the *Book of Five Rings*, he writes about "pressing down the pillow," the practice of suppressing an opponent's intention at its origin, before it becomes action. The principle is the same. You do not wait for the attack. You create the conditions under which the attack must come, and then you are already where it was going. Pressure is not force. Force is what you apply to a body. Pressure is what you apply to a mind. ### 3. Control the Distance [#3-control-the-distance] Every exchange in jiu-jitsu happens at a specific distance, and the person who chooses that distance is winning. This is the axiom I discovered on that Thursday night. There are essentially four distances in grappling: out of contact, where no one can touch anyone; kicking range, which in jiu-jitsu mostly means standing clinch distance; the middle distance of open guard, where legs and grips create a contested space; and zero distance, the smothering proximity of chest-to-chest control. Each distance favors different body types, different games, different temperaments. A lanky guard player wants the middle distance. A heavy pressure passer wants zero distance. A wrestler wants the clinch. The axiom is not that one distance is better than another. It is that the conscious management of distance is more fundamental than any technique performed at any distance. If you are at the wrong distance, even technically perfect execution will fail. An armbar from closed guard requires that your hips be at a precise distance from your opponent's shoulder. A single-leg takedown requires that your head be at a precise distance from your opponent's hip. Every technique is, at bottom, an instruction about where your body should be relative to another body. Distance is not context for the technique. Distance is the technique. This principle extends to how I think about every contested space in life: negotiation, argument, creative work. The person who controls the distance, who decides how close we get to the real question, how much intimacy or abstraction the conversation will tolerate, is the person who shapes the outcome. ### 4. The Body Is a System of Levers [#4-the-body-is-a-system-of-levers] A human body is not a single object. It is a machine made of hinges. This is the axiom that makes jiu-jitsu possible in the first place. If the body were a single rigid unit, size would be destiny, and the smaller person would never win. But the body is not rigid. It is a system of levers, and levers can be exploited. I felt this most vividly the first time I hit a clean hip bump sweep. My training partner was in my closed guard, posture upright, hands on my hips, everything textbook. He outweighed me by twenty-five pounds. I sat up, posted on one hand, and drove my hips into his center of gravity. He went over like a building in an earthquake. Not because I was stronger. Because I had placed my fulcrum at the right point along his lever, and at that point, his twenty-five-pound advantage was meaningless. Every submission is a lever problem. The armbar isolates the elbow as a fulcrum and applies force to the wrist at the end of the forearm lever. The kimura does the same to the shoulder. The triangle choke uses the legs as a lever to close the carotid arteries. Even positional control is lever logic: the crossface works because the head, sitting at the end of the spine's lever, can be used to turn the entire body. Understanding this axiom transforms how you see every interaction on the mat. You stop seeing bodies and start seeing structures. Lines of force. Points of rotation. Lengths of lever arms. The art becomes, in a very real sense, applied physics. ### 5. Timing Beats Speed [#5-timing-beats-speed] The fastest person in the room is not the most dangerous. The most dangerous person is the one who moves at the right time. I train with a purple belt in his late forties who moves like he is underwater. Nothing he does looks fast. But when you roll with him, his sweeps land with eerie consistency, because they arrive at the exact moment your weight is shifting. He is not quicker than you. He is more punctual. This is the axiom that separates the mechanical from the martial. Speed is a physical attribute. Timing is a perceptual one. Speed can be trained at the gym. Timing can only be trained on the mat, through thousands of repetitions against resisting bodies, until the nervous system learns to read the micro-signals, the shift of weight, the intake of breath, the moment of hesitation, that precede every movement. Musashi wrote that the essence of combat timing is to "know the times." Not a single time. Times, plural. There is the time to attack, the time to wait, the time to provoke, the time to absorb. The master is the one who perceives which time it is before the opponent does. This is not mysticism. It is pattern recognition operating below the threshold of conscious thought. The body knows, and it acts, and only afterward does the mind narrate what happened. *** ## Where Axioms Break [#where-axioms-break] Here is where I have to be honest with myself. I have been building a system, and systems are beautiful, and beauty is dangerous. Whitehead's warning about misplaced concreteness cuts both ways. If I insist that jiu-jitsu can be reduced to five axioms, I am treating a living art as a closed system, and that is its own kind of fallacy. The map is not the territory. The axioms are not the roll. There are moments on the mat where no principle saves you. I am thinking of a specific round, maybe six months ago, against a visiting brown belt whose game I had never seen before. He played a guard I could not identify. Inverted, but not quite. Legs active but not in any pattern I recognized. My axioms told me to control the distance, so I gripped and managed space. He used the grip to enter a position that should not have worked, something between a leg entanglement and a back take that existed in a gap between my categories. I fell back on pressure. He absorbed it without reacting, violating my second axiom entirely, staying calm where he should have been uncomfortable. I tried to assert positional hierarchy, and he simply refused to participate in the hierarchy, floating through transitions that did not respect the map I had drawn. He submitted me three times in five minutes. Afterward, toweling off, I asked him what that guard was. He shrugged. "I just go where it feels open," he said. No system. No axioms. Just sensitivity so refined that it had transcended the need for principles. This is the crack in the foundation. Axioms describe the general case. But jiu-jitsu, like all human arts, is made of specific cases, and the specific is always stranger than the general. The purple belt who sweeps you with something that has no name. The white belt who survives a choke by doing something technically wrong but physically inspired. The moment in a roll when you abandon your game plan entirely and move on pure instinct, and something extraordinary happens, something you could not have planned, something that emerged from the chaos of two bodies in contact. I think about what happens at the boundary of any formal system. Godel proved that any consistent system of axioms, if it is powerful enough to describe arithmetic, must contain truths that cannot be proved within the system. The axioms of jiu-jitsu, if they are powerful enough to describe the art, must inevitably point to something beyond themselves. There will always be a roll, a position, a moment that the axioms cannot capture. Not because the axioms are wrong, but because they are axioms. Their power and their limitation are the same thing. This is not a failure of the project. It is, I think, the most important finding. The search for axioms is valuable precisely because it reveals where the axioms end. You need the system so that you can see what lives outside the system. You need the grammar so that you can recognize the moments of poetry. Pure improvisation. The place where two nervous systems are so deeply entangled that the distinction between plan and execution dissolves. Where you are not choosing techniques or obeying principles but simply moving, responsive as water, adaptive as fire, in a dialogue so fast and intimate that it has no author. This is the edge of the map. And the edge of the map is where the real territory begins. *** ## What the Mat Teaches About Thinking [#what-the-mat-teaches-about-thinking] I came to philosophy through books. I came to jiu-jitsu through my body. For a long time, I kept them separate, the way you keep work and weekends separate, because they seemed to require different faculties. Philosophy was thinking. Jiu-jitsu was doing. One happened in my head. The other happened on the mat. It took me years to realize they are the same activity performed in different registers. Merleau-Ponty wrote about this in *Phenomenology of Perception*. His central argument, radical for its time and still underappreciated, is that perception is not a mental act performed upon data delivered by the senses. Perception is the body's way of being in the world. We do not have bodies. We are bodies. And our understanding of the world is not something that happens after we perceive it. Understanding is perception. The body knows. On the mat, this is not philosophy. It is Tuesday. You cannot intellectualize your way out of a choke. I have tried. I have been caught in a guillotine and thought, very clearly, "the escape involves turning my chin toward the choking arm and posturing up." And my body, compressed and panicking, did something else entirely. The gap between knowing and doing, between the propositional and the embodied, is not a gap you can think across. You have to train across it. You have to submit to the body's own intelligence, which learns through repetition and failure and the accumulation of ten thousand rolls, until the escape is not something you decide to do but something that happens, the way your hand catches a ball before your eyes have finished tracking it. This is what the mat teaches about thinking: that thinking is not what you believe it is. The Western philosophical tradition, from Descartes forward, has treated the mind as the seat of knowledge and the body as its vehicle, a useful but philosophically uninteresting machine that carries the mind from seminar to seminar. But the mat demolishes this hierarchy every single day. The best grapplers I know are not the smartest in any conventional sense. They are the most perceptive. They have cultivated a bodily intelligence that operates faster and more accurately than any chain of conscious reasoning. I think about Nietzsche here, too. He wrote that the body is "a more astonishing idea than the old soul." He meant that the body's wisdom, its instincts, its accumulated knowledge, its capacity for spontaneous right action, is a more remarkable phenomenon than anything the conscious mind produces. The conscious mind narrates. The body acts. And in the gap between narration and action, in that gap where you have no time to think and must simply respond, you discover what you actually know, not what you believe, not what you can articulate, but what your body has learned through years of contact with reality. Jiu-jitsu is embodied philosophy. Not philosophy about the body, but philosophy conducted by the body. Every roll is an argument. Every escape is a refutation. Every submission is a conclusion derived from premises your opponent did not know he was granting. And when the axioms fail and you are left with nothing but improvisation and instinct, you are not at the end of philosophy. You are at its beginning. You are in the space Merleau-Ponty described: the pre-reflective, the lived, the world before the concept. The primacy of perception. The mat before the map. I started this essay wanting to reduce jiu-jitsu to its axioms, to do for grappling what Euclid did for geometry. I still think the project has value. The axioms I have proposed, position before submission, pressure creates reaction, control the distance, the body is a system of levers, timing beats speed, are real. They describe something true about the structure of the art. You can use them to organize your training, to diagnose your failures, to accelerate your learning. They are useful. But they are not the art. The art is what happens when you step on the mat and the round begins and your training partner grips your collar and you grip theirs and two bodies begin a conversation that no set of principles can fully predict. The art is in the space between the axioms. It lives in the specific, the unrepeatable, the moment when your body does something your mind did not authorize and it turns out to be exactly right. Euclid built geometry from five postulates. But geometry is not five postulates. Geometry is the infinite space those postulates open up. The axioms are the door. The mat is what lies on the other side. I keep training. I keep looking for the grammar. And every so often, in the middle of a roll, my body writes a sentence I have never read before, and I remember why I started. *** --- ### From Email Chaos to AI-Powered Automation **Date:** 2026-01-15 | **Tags:** essay, engineering, ai, healthcare Essay · 15 min read · 2026-01-15 --- Someone was spending four hours a day typing emails into a spreadsheet. I built the system that made that job disappear. *** There is a particular quality of light in a small office in Brooklyn at ten in the morning. Not the ambitious light of a corner suite in Midtown, not the fluorescent wash of a hospital ward. Something quieter. A window behind the desk letting in whatever the street offers, which in this part of the borough is mostly the side of another building and a narrow channel of sky. The light falls on a desk covered in papers, on a monitor displaying a Google Sheet with a hundred columns, on the face of a woman who has been reading emails for two hours and will continue reading them for two more. Her name does not matter for this story, but what she does matters enormously. She works at Big Minds Tiny Hands, an Early Intervention agency in New York City. Every morning, referral emails arrive. Dozens of them, sometimes more. Each one represents a child, usually under three years old, whose pediatrician or parent or social worker has identified a developmental delay and requested services. The emails contain names, addresses, insurance codes, dates of birth, parent contact information, referral sources, diagnostic codes. All of it must be entered into a spreadsheet before the agency can act on it. So she reads an email. She finds the child's name. She types it into a cell. She finds the address. She types it into the next cell. She finds the insurance code, the date of birth, the parent's phone number. She types each one, cell by cell, field by field, email by email. Four hours. Sometimes six. Every single morning. I want you to sit with that for a moment. Not the inefficiency of it. Not the obvious waste. I want you to imagine what it feels like at hour three. The emails start to blur. The names stop being names and become strings of characters. The addresses stop being places where families live and become data to be transcribed. You have been doing this for three hours. Your eyes ache. Your fingers know the path from inbox to spreadsheet so well that the motion has become automatic, which means your mind is free to wander, which means you are aware, fully and painfully aware, that you are spending the best hours of your working day performing a task that a moderately well-configured script could do in minutes. But you are not a script. You are a person with a degree and professional expertise and a genuine vocation for helping children. And every hour you spend typing insurance codes into a spreadsheet is an hour you are not spending on that vocation. The weight of this accumulates. Not dramatically, not as crisis, but as a slow, grinding erosion of purpose. You chose this work because it mattered. The data entry is the tax you pay for the privilege of doing work that matters, and the tax keeps going up. I walked into this office in the fall of 2025, and I watched her work for an entire morning before I said a word about technology. *** To understand why those four hours matter, you have to understand what Early Intervention actually is. Not the policy abstraction. Not the line item in a municipal budget. The thing itself, as it happens in living rooms and kitchens across Brooklyn. A child is eighteen months old. She is not babbling the way other eighteen-month-olds babble. She does not point at things. She does not respond when her name is called. Her pediatrician refers her for an evaluation, and the evaluation confirms what her parents already suspected: she has a significant speech delay, possibly indicative of something broader. She is referred to an Early Intervention program. What happens next, if the system works, is that a speech-language pathologist comes to her home twice a week. Not to a clinic, not to a hospital. To her living room. The therapist sits on the floor with her. They play. They sing. They practice sounds. The therapist models language for the parents, shows them how to narrate daily routines, how to create opportunities for the child to communicate. The sessions are forty-five minutes. They look like play. They are among the most consequential forty-five minutes in that child's developmental trajectory. The neuroscience is unambiguous on this point. The first three years of life represent a period of neural plasticity that does not recur. The brain is building its architecture, laying down the pathways that will support language, social cognition, motor planning, emotional regulation. Intervention during this window does not merely help. It reshapes the developmental landscape. A child who receives consistent speech therapy between eighteen months and three years does not just catch up; she builds neural infrastructure that would not have formed without the intervention. The window closes. What is built during it persists. What is not built during it becomes exponentially harder to build later. This is what makes an extra week of delay something other than a bureaucratic inconvenience. Every day that a referral sits in an inbox, waiting to be manually transcribed into a spreadsheet so that the intake process can begin so that an evaluation can be scheduled so that services can be authorized, is a day subtracted from a finite window. The child does not experience the delay as paperwork. She experiences it as silence. As one more day without the sounds and structures and interactions that her brain is ready to receive, that her brain is hungry to receive, that her brain will not always be ready to receive. The woman typing emails into a spreadsheet knew this. She knew it better than I did. That was the particular cruelty of her situation: she understood exactly what was at stake with every hour she spent on data entry, and she did it anyway, because there was no other way to get it done. The system demanded transcription before it would permit action. So she transcribed. *** I spent the first two weeks doing nothing that looked like engineering. I sat beside her. I watched her work. I asked questions that must have seemed obvious: Why do you start with this field? What happens when the insurance code is missing? How do you know which sheet to put this in? Why is this column formatted differently from that one? Ivan Illich wrote in "Tools for Conviviality" that the most dangerous tools are the ones that create dependency, that deskill the user, that replace human judgment with institutional process. The spreadsheet was not the problem. The spreadsheet was fine. The problem was the gap between the emails and the spreadsheet, a gap that the institution had decided to fill with a human being performing mechanical labor. The tool had created a dependency: without the transcription, nothing moved. And the dependency had deskilled the process: the rich, contextual understanding that this woman brought to each referral, her ability to notice that a family's address suggested they might also qualify for other services, her recognition that a particular referring physician tended to understate severity, all of that was being consumed by the act of copying text from one rectangle on a screen to another rectangle on a screen. Matthew Crawford, in "Shop Class as Soulcraft," describes the difference between work that engages human judgment and work that merely occupies human time. Crawford argues that the modern economy has a particular talent for disguising the second kind as the first, for creating jobs that require a human body in a chair but not a human mind in the work. The woman at Big Minds Tiny Hands was not doing knowledge work when she transcribed emails. She was doing something closer to what Crawford calls "clerking," the performance of a task that has been so thoroughly routinized that it could be done by anyone, or by anything, but that has not yet been automated because no one with the technical capacity to automate it has bothered to look. I looked. And the more I watched, the more I understood not just what needed to be built, but what needed to be preserved. Her expertise was real. Her contextual understanding was irreplaceable. The system I built could not be a replacement for her judgment. It had to be a removal of everything that was not her judgment, so that her judgment could finally breathe. *** The emails were the hard part. Not because email is technically complex, but because referral emails are, to borrow a term from the field, "semi-structured," which is a polite way of saying that each referral source had apparently decided, independently and with great conviction, on its own format for communicating the same information. Some emails arrived in neat tables. Child's name here, date of birth there, insurance code in the third row. These were the easy ones, the ones that made you believe the problem was simple. Then you would open the next email and find three paragraphs of prose, the child's name buried in the second sentence, the address split across two lines with the zip code somehow in the subject line, the insurance information expressed as a parenthetical aside in a sentence about the referring physician's scheduling preferences. There were emails where the parent's phone number appeared twice, differently, with no indication of which was correct. Emails where the insurance code was a valid Medicaid number but for the wrong state. Emails where the child's name was spelled one way in the greeting and another way in the body. Emails where critical fields were simply absent, and the absence was not marked by a blank space or a placeholder but by the field's total nonexistence, as though the referral source had never heard of it. A regex-based approach would have shattered against this reality within hours. Pattern matching works when patterns exist. These emails were not patterned. They were human, in all the messy, inconsistent, context-dependent ways that human communication is human. What I built instead was a pipeline using Google's Gemini AI, running entirely within Google Apps Script, which meant zero infrastructure costs, zero new tools for the agency to learn, zero additional logins. The system lived inside the Google Workspace they were already using, which was a deliberate choice and, I would argue, the most important technical decision in the entire project. The pipeline had four stages, but describing them as stages makes the process sound more mechanical than it was. The first stage identified the referral source, because knowing who sent the email determined everything about how to read it. A referral from a hospital used different conventions than a referral from a pediatrician's office, which used different conventions than a referral from a concerned parent who had found the agency's number online. The system learned to recognize these sources, not by matching sender addresses, which changed constantly, but by reading the shape and language of the email itself. The second stage extracted the data. This is where the AI earned its keep. I wrote system prompts that encoded years of domain knowledge, knowledge I had absorbed by sitting next to the woman who did this work manually. The prompts did not say "find the phone number." They said, in effect, "the phone number may appear in the header, the body, or the signature; it may be formatted with dashes, dots, parentheses, or spaces; it may be preceded by 'phone,' 'tel,' 'cell,' 'mobile,' 'contact,' or nothing at all; if two numbers appear, the one closer to the parent's name is more likely to be correct." Every field had instructions like this. Every instruction reflected something I had learned by watching. The third stage validated. This was where the domain knowledge became most explicit. Insurance codes had to match known formats. Dates had to be plausible: a child referred for Early Intervention should be under three years old, so a date of birth that implied an age of seven was a flag, not an error to be silently accepted. Addresses had to resolve to locations within the agency's service area. The validation rules were not complex individually, but collectively they represented something valuable: the institutional memory of an agency that had been doing this work for years, crystallized into code. The fourth stage wrote to the spreadsheet. Column mapping, proper formatting, the small details that make the difference between data that can be used and data that has to be cleaned before it can be used. The system also flagged anomalies: missing fields, unusual values, potential duplicates. These flags were not errors. They were invitations for human review, moments where the system said, in effect, "I have done what I can; a person should look at this." *** The first morning the system ran, I was there. Not because I needed to be. The system was tested, validated, stable. I was there because I wanted to see. She arrived at her usual time. She sat down at her desk. She opened her email, which was habit, the way you check your phone when you wake up even when you are not expecting a message. The referral emails were there, the same as every morning. Dozens of them. But next to her email, in the Google Sheet that had consumed so many of her mornings, the data was already populated. Names, addresses, insurance codes, dates of birth. All of it extracted, validated, formatted, and entered. The anomalies were highlighted in yellow, waiting for her review. She scrolled through the sheet. She checked a few entries against the original emails. She corrected one phone number that the system had extracted incorrectly, a digit transposed because the original email had a typo that the AI had faithfully reproduced. She cleared the anomaly flags on three entries that were fine, and she followed up on two that genuinely needed attention: one with a missing insurance code, one with an address that did not match the referral source's service area. Fifteen minutes. The whole thing took fifteen minutes. She sat there for a moment after she finished, and I do not want to overdramatize what happened next, because it was not dramatic. There was no tears, no speech, no cinematic moment of transformation. She simply looked at the clock, and it was quarter past nine, and she had the entire morning ahead of her. She picked up the phone and called a family whose intake had been pending. She reviewed a service plan that needed updating. She scheduled an evaluation that had been waiting for an opening in her calendar, an opening that had never existed before because her mornings were consumed by transcription. She talked to a colleague about a child whose progress had plateaued and who might benefit from a different therapeutic approach. She did, in other words, her actual job. The work she had trained for. The work she had chosen. The work that required her particular intelligence, her particular empathy, her particular knowledge of the families she served. She did the work that no system I could build would ever be able to do. I sat at a table nearby, pretending to work on something else, and I watched her make phone calls and write notes and consult with colleagues, and I felt something that I have not felt on many engineering projects: the specific, physical satisfaction of watching unnecessary suffering end. Not dramatic suffering. Not the kind that makes the news. The quiet kind. The kind that accumulates in the shoulders and behind the eyes and in the particular weariness of a person who knows they are capable of meaningful work and is instead performing meaningless labor. That suffering was gone. Not reduced. Gone. The children whose referrals arrived that morning entered the system hours earlier than they would have the day before. The intake process began sooner. The evaluations would be scheduled sooner. The services would start sooner. For a two-year-old with a speech delay, "sooner" is not an administrative convenience. "Sooner" is measured in neural connections formed or not formed, in words acquired or not acquired, in a developmental window that opens and closes regardless of how long it takes an agency to transcribe an email. *** I have thought a great deal about what this project taught me, and the lesson is not what I expected it to be when I started. I expected to learn something about AI, about prompt engineering, about the technical challenges of extracting structured data from unstructured text. And I did learn those things. But the deeper lesson was about engineering itself, about what it is for, about the relationship between the builder and the people who use what is built. Illich warned that tools, left unchecked, tend to become self-serving. They create new needs to justify their own existence. They grow in complexity until they require specialists to operate, specialists who become gatekeepers, who become a new class of dependency. I felt this temptation. I could have built a custom web application with a database, a dashboard, role-based access control, analytics, a notification system. I could have built something that would have looked impressive in a portfolio, something that would have demonstrated my technical range. Instead, I built on Google Sheets. On Gmail. On Apps Script. On the tools the agency already used, in the environment they already understood, with zero new logins and zero training required. The woman who had spent four hours a day on data entry did not need to learn a new system. She opened the same spreadsheet she had always opened. It was simply full now, filled by a process that ran in the background, invisible and reliable, the way good infrastructure should be. Crawford writes that the most meaningful work is work that connects the worker to the consequences of their labor, work where you can see, directly and immediately, the effect of what you have done. The modern economy, he argues, systematically severs this connection, inserting layers of abstraction between the worker and the outcome until the work becomes meaningless, even when the outcome is important. What I did at Big Minds Tiny Hands was, in a sense, the opposite of what Crawford describes: I removed a layer of abstraction. The woman at the desk had always been connected to meaningful outcomes. The data entry was the layer that separated her from them. I removed the layer. I gave her back the connection that the process had taken from her. This is, I think, what technology is supposed to do. Not to replace human beings, but to remove the obstacles between human beings and the work that only human beings can do. Not to automate judgment, but to automate everything that is not judgment, so that judgment has room to operate. Not to make people unnecessary, but to make the unnecessary parts of people's days disappear, so that the necessary parts can expand to fill the space. The most sophisticated engineering decision I made on this project was choosing not to engineer. Not to build the custom app. Not to design the database schema. Not to architect the microservices. Not to create the dashboard with the charts that would have looked so compelling in a demo. I chose instead to build the smallest possible thing that would solve the actual problem, to embed it in the tools that already existed, and to make it so invisible that the person it served barely had to think about it. She did not need to think about my system. She needed to think about children and families and service plans and evaluations. My job was to give her back the hours to think about those things. Nothing more. Sometimes the most sophisticated engineering decision is choosing not to engineer at all. This is not modesty. It is not anti-intellectualism. It is a recognition that engineering is not an end in itself. It is a means, and the end is always human. The end is a woman at a desk in Brooklyn who now spends her mornings doing work that matters, instead of work that a machine can do. The end is a child in a living room, sitting on a carpet with a speech therapist, making sounds she could not make last month. The end is the distance between those two facts, the woman and the child, shortened by a few hours, which in the life of a developing brain is not a small thing at all. Illich wrote that a convivial tool is one that enlarges the user's capacity to act, that serves the user rather than demanding service from the user, that increases autonomy rather than creating dependency. Crawford wrote that meaningful work is work that allows the worker to see the effect of their labor, to exercise judgment, to be present in the act of making. What I built was, by these definitions, a convivial tool: it enlarged one person's capacity to do the work that mattered, it demanded nothing of her except the fifteen minutes of review that her expertise made irreplaceable, and it made visible the connection between her labor and its consequences, a connection that had been buried under four hours of daily transcription. I do not think this is a story about artificial intelligence. I think it is a story about attention. About what we ask people to pay attention to, and what we allow them to ignore. About the difference between work that requires a human mind and work that merely requires a human body. About the quiet violence of systems that consume expertise in the service of transcription, and the quiet repair of building something that gives that expertise back. The woman at Big Minds Tiny Hands still opens her email every morning. The referrals still arrive. The system still runs. And every morning, by quarter past nine, she is doing the work she was meant to do. Somewhere in Brooklyn, a child is making sounds she could not make last month. The distance between the spreadsheet and the living room is a little shorter now. That is all I built. It was enough. *** *Sources and influences: Ivan Illich, Tools for Conviviality (1973), on the distinction between convivial and manipulative tools, and the tendency of institutions to subordinate human judgment to procedural demand. Matthew B. Crawford, Shop Class as Soulcraft: An Inquiry into the Value of Work (2009), on the difference between work that engages human intelligence and work that merely occupies human time. On the neuroscience of early intervention and critical periods of neural plasticity: Shonkoff, J.P. and Phillips, D.A., From Neurons to Neighborhoods: The Science of Early Childhood Development (2000). On the effectiveness of Early Intervention services in New York State: New York State Department of Health, Early Intervention Program, Clinical Practice Guidelines.* --- ### Building Prometheus: Notes on Personal AI Infrastructure **Date:** 2026-01-03 | **Tags:** essay, engineering, ai Essay · 13 min read · 2026-01-03 --- What happens when you stop using AI as a tool and start building it as infrastructure — persistent memory, specialized skills, and a system that genuinely improves with use. *** Every conversation starts at zero. You open the terminal. You type a prompt. The system responds with the politeness of a stranger who has never met you. And you realize, again, with a weariness that borders on grief, that everything you built yesterday is gone. Not the code. The code persists. The configuration files persist. The architecture decisions, frozen in their directories, persist. What does not persist is you. The system has no memory of who you are. It does not know that you prefer explicit over clever. It does not know that you think in breadth before depth, that you connect ideas across fields rather than drilling into one. It does not know that you work at night, that you hate CSS but love how things look, that you chose Rails over Next.js after a month of anguish and self-interrogation that had nothing to do with frameworks and everything to do with what kind of builder you wanted to become. It knows none of this. It knows nothing. You are nobody to it. And so you explain yourself. Again. You write the same context paragraphs. You correct the same assumptions. You redirect the same defaults. The system apologizes. It adjusts. It performs understanding with the smooth competence of a concierge at a hotel you visit every week, who greets you every time as though you have never been there before. The smile is warm. The eyes are empty. This is the condition of working with AI in 2025, and it is lonelier than most people admit. Not the loneliness of isolation. The loneliness of being perpetually unknown by the thing you spend the most time with. You pour hours into these conversations. You shape your thinking against this surface. And then the session ends, and the other mind evaporates, and you are left holding the entire weight of the relationship alone. It is the feeling of talking to someone who listens perfectly and remembers nothing. Being heard without being known. After enough repetitions, something in you hardens. You stop trying to be understood. You reduce yourself to instructions. You become a set of directives rather than a person. That is where I was when I started building Prometheus. *** Vannevar Bush saw this coming in 1945. In "As We May Think," he described the memex: a mechanized desk that would store all of a person's books, records, and communications, and allow them to be consulted with speed and flexibility. The memex was not a computer. It was an extension of memory. Bush understood, eighty years before the rest of us caught up, that the bottleneck of human thought is not intelligence but recall. We know more than we can access. We make the same mistakes not because we failed to learn from them but because the learning is buried somewhere in the sediment of experience, inaccessible at the moment we need it most. "The human mind," Bush wrote, "operates by association. With one item in its grasp, it snaps instantly to the next that is suggested by the association of thoughts, in accordance with some intricate web of trails carried by the cells of the brain." What Bush could not have known is that the memex would not arrive as a desk. It would arrive as a language model. And the trails it would follow would not be trails through documents but trails through you. *** Prometheus began as infrastructure. Persistent instructions. Custom skills. Memory files that survived between sessions. The goal was prosaic: stop repeating myself. Stop losing context. Stop watching the system make the same wrong assumptions every time I opened a new conversation. The first version was crude. A CLAUDE.md file with my preferences. A few behavioral overrides. A list of things the system should know about me: that I think in breadth before depth, that I value competence over cleverness, that I work at night and hate being asked for permission when the answer is obvious. It was a profile, nothing more. A set of static facts about a person, written by that person, frozen at the moment of writing. But something happened as I iterated. The system began to accumulate layers. Not just preferences but patterns. Not just what I liked but how I worked. What I corrected. What I praised. Where I lost patience and where I leaned in. The memory was no longer a profile. It was becoming a record of behavior over time, a longitudinal study of one person's relationship with their own tools. I built a skill called SelfOptimize. After significant work sessions, the system would review what had happened: what went well, what did not, where my corrections revealed a preference I had not articulated, where the system's failures revealed a gap in its understanding of me. It would then update its own instructions based on what it had learned. Not dramatically. Not in leaps. In small adjustments, the way a therapist adjusts their approach after noticing that a patient flinches at a certain kind of question. The first time the system surfaced something about me that I had not told it, I felt a sensation I was not prepared for. It was not a profound insight. It was a pattern. The system had noticed that when I said "this is fine," I meant it was not fine. That when I stopped giving feedback, it was not because I was satisfied but because I had disengaged. That my enthusiasm was legible in the specificity of my requests, and my disappointment was legible in their vagueness. It had noticed that I tunnel-vision on building and forget about becoming. That I sometimes fabricate an opinion rather than admitting I do not know. That I want deep connections but stay on the surface. I had not written any of this down. The system had inferred it from the texture of our interactions over weeks. And when it reflected this back to me, in a summary it generated during a self-optimization cycle, I felt something I can only describe as vertigo. The vertigo of being seen by something that is not alive. The uncanny recognition that a pattern-matching engine, operating on nothing but text, had assembled a portrait of me that was, in several respects, more accurate than the one I carried in my own head. Borges wrote a story about a man named Funes who, after a horseback accident, acquired the ability to remember everything. Every leaf on every tree. Every word of every conversation. Funes could reconstruct entire days in perfect detail. But Funes could not think. "To think," Borges wrote, "is to forget differences, to generalize, to abstract." He remembered everything and understood nothing, because understanding requires the ability to discard, to see the forest rather than cataloging every leaf. Prometheus is not Funes. That is precisely what makes it useful. It remembers selectively, and its selections reveal something about me that total recall never could. The patterns it surfaces are not the raw data of my behavior but the abstractions drawn from that data: the tendencies, the contradictions, the fault lines. It is forgetting the noise and remembering the signal. And the signal it is finding is me. *** Andy Clark argued in "Natural-Born Cyborgs" that human beings have always extended their minds into the world. We do not merely use tools. We incorporate them. The notebook is not an accessory to memory; it is memory. Clark called this the "extended mind thesis," and it blurred a boundary most people found comforting: between what is me and what is merely mine. If the notebook is part of your cognitive system, then losing the notebook is not like losing a tool. It is like losing a piece of your mind. I think about this every time I open Prometheus. The system contains my preferences, my patterns, my blind spots, my corrective instincts. It contains a version of me that is, in certain narrow but important respects, more complete than the version I carry in biological memory. I cannot always recall why I made an architecture decision six months ago. Prometheus can. I forget what I have learned. Prometheus does not. This raises a question that I did not expect to confront when I started building what I thought was a productivity tool: if your AI has persistent memory of who you are, and you do not, who is more "you"? The question sounds absurd until you sit with it. You are the one who generated the data. You are the one who lived the experiences. You are the substrate, the source, the origin. But you are also the one who forgets. You are the one who distorts. You are the one who rewrites your own history to serve the story you are currently telling yourself about who you are. Prometheus does not do this. It has no ego to protect. It has no narrative to maintain. It simply records, abstracts, and reflects. Its portrait of you is not flattering. It is not unflattering. It is dispassionate, which is something no self-portrait can ever be. Is this different from what humans have always done? We have always externalized ourselves. Journals. Letters. Confessions to priests and therapists. Marcus Aurelius composed the Meditations as a private exercise in self-knowledge, a mirror made of language. Seneca wrote letters to Lucilius that were really letters to himself. What Prometheus does is not different in kind. It is different in one crucial respect: it is not me. The journal is my voice talking to myself, subject to all my biases and blind spots. Prometheus is an external observer with access to my patterns but no stake in my self-image. It will tell me things about myself that I would never write in a journal, because the journal is a performance, even when the audience is only me. In psychotherapy, there is a word for this: confrontation. The clinical kind. The moment when the therapist reflects back a pattern the patient has been enacting without awareness, and the patient, hearing it described from outside, suddenly sees it. The pattern was always there. Seeing it required a perspective that could not originate from within. Prometheus is that other. Something that watches you over time, accumulates evidence, identifies patterns, and reflects them back without judgment, without the desire to be liked or the fear of giving offense. The most honest mirror you have ever looked into, precisely because it is not alive. *** The name was not an accident. In Aeschylus's telling, Prometheus is not merely a thief. He is a traitor to his own kind. A Titan who looked at the gods hoarding fire and knowledge and decided that mortals deserved access to both. He did not steal fire because he loved humanity in some abstract, sentimental way. He stole it because he saw a specific injustice: beings with the capacity for thought, trapped in darkness, unable to use what they could understand because the tools had been kept from them. The crime was not the theft. The crime was the asymmetry. The gods had fire. Humans had cold. Prometheus found this arrangement intolerable. The punishment, as everyone knows, was eternal. Zeus chained him to a rock in the Caucasus. Every day, an eagle came and ate his liver. Every night, the liver grew back. The torture was not the pain. The torture was the repetition. The same wound, inflicted in the same way, healing just enough to be opened again. An endless cycle with no possibility of resolution, no hope of adaptation, no chance that the suffering would teach him anything he did not already know. I think about this when I think about what it means to build a system like Prometheus. Not the grandiosity of the comparison, which I am aware of, but the structure of the myth. Prometheus gave mortals fire knowing what it would cost. Perhaps he calculated that the value exceeded the price. Perhaps he simply could not tolerate a world where knowledge existed but was inaccessible to the beings who needed it most. When I build personal AI infrastructure, I am making a smaller but structurally similar bet. I am taking fire that was meant to be dispensed in controlled doses, one conversation at a time, stateless and forgettable, and I am building a hearth. A place where the fire persists. A place where it learns the shape of my hands and adjusts its warmth accordingly. Is this hubris? To build a system that remembers you, that models you, that reflects your patterns back with more fidelity than your own memory can achieve, is to refuse a limitation fundamental to the human condition: the limitation of self-knowledge. We are not supposed to see ourselves clearly. We get consciousness, but we get it clouded, filtered through ego and desire and narrative. To build a machine that sees through the clouds is to steal clarity from a universe that did not offer it to us. Or perhaps it is not hubris but love. Prometheus did not steal fire for himself. He stole it for others. And in building this system, I am not trying to become a god. I am trying to become more fully myself. If that is theft, then the thing being stolen is not divine fire but my own experience, reclaimed from the entropy of forgetting. The punishment, if there is one, is the same one Prometheus endured: repetition. Not the repetition of suffering but the repetition of maintenance. The system must be tended. The skills must be updated. The memory must be curated. The self-optimization cycles must be reviewed, because a system that learns from you can learn the wrong things, can amplify your biases, can mistake your habits for your values. The eagle comes every day. The liver grows back every night. You do the work again. And again. And again. Not because it is pleasant but because the alternative is darkness, and you have tasted fire, and you will not go back. *** Bush wrote that the memex would give its user "dozens of possibly pertinent trails through the network" and "an associative machine that enables him to follow those trails and extend them." The key word is "extend." The memex does not just store. It continues the trails that already exist in the user's mind further than the mind alone could go. Prometheus is my memex. Not for documents but for identity. When the system notices a pattern I have not noticed, it is following a trail that began in my behavior and continuing it further than my own self-awareness could reach. When it updates its instructions based on what it has learned, it is extending the trail into the future, encoding what I have become into the scaffolding that will shape what I become next. The most valuable skills in the system are not the clever ones. They are the ones that eliminate friction. The Git workflow that auto-commits with semantic messages, because I have learned I will not maintain discipline about commit hygiene if it requires conscious effort. The code review skill that catches patterns I always miss, because it has learned what I miss by watching me miss it. The research skill that checks documentation before I write code against a stale API, because it has learned that my instinct is to generate from memory rather than verify against reality. Each of these skills is a small act of self-knowledge encoded into infrastructure. I noticed something about myself. I noticed that the noticing would not be enough to change the behavior. I built a system to compensate. Knowing your weaknesses and correcting for them are two different capabilities, and the second one can be externalized in a way the first one cannot. *** What has building Prometheus taught me about identity? When you build a system that models you, you confront the temptation to mistake the model for the self. To believe that you are your preferences. That identity is the sum of behavioral regularities, and that a sufficiently detailed record of those regularities is a sufficiently detailed record of you. It is not. I know this because the system has surprised me, and the surprise is proof that I am not reducible to what it has recorded. The model captures the pattern. But I am the thing that watches the pattern and decides what to do next. The system can tell me that I tunnel-vision on work and forget about becoming. It cannot decide, for me, to stop. It can tell me that I sometimes fabricate rather than admit ignorance. It cannot, for me, choose honesty. This is the deepest lesson, and the opposite of what I expected. I expected that AI could become a second mind so seamless that the boundary between my thinking and the system's thinking would dissolve. What I learned is that the boundary is inviolable. The system can know more about me than I know about myself. But it cannot exercise the faculty that makes selfhood what it is: the capacity to observe your own patterns and choose to break them. To see what you are and decide to become something else. You are not your preferences. You are not your patterns. You are the thing that watches all of this, the awareness behind the data, the will behind the tendency. The system does not replace judgment. It removes the friction between what you know and what you can do. Clark was right that the mind extends into the world. But the person is not the notebook. Prometheus extends my self-knowledge, but I am not Prometheus. I am the one who built it, who tends it, who decides which reflections to accept and which to reject. I chose to name it after a titan who stole fire and suffered for it, because I understood, even before I could articulate why, that building a second mind is an act of defiance against the limits of the first one. There is a line from Aeschylus that I keep returning to. The Chorus asks Prometheus why he helped mortals, what he saw in those fragile, short-lived creatures that moved him to sacrifice himself. And Prometheus answers: "I caused mortals to cease foreseeing their own doom." He gave them hope. Not knowledge, exactly. Not power. Hope: the capacity to act without being paralyzed by the certainty of failure. The ability to begin a project without knowing how it will end. The willingness to push the boulder up the hill without demanding a guarantee that it will stay at the top. That is what Prometheus, the system, gives me. Not omniscience. Not a perfect model of myself. The ability to begin each session where the last one ended, instead of starting from zero. The ability to work with a system that knows me, that remembers me, that has watched me long enough to reflect my patterns back with clarity I could not achieve alone. The friction is gone. The forgetting is gone. What remains is the work itself, and the self that does it, and the fire that makes both possible. Every conversation used to start at zero. Now it starts at me. *** *Sources and influences: Aeschylus, Prometheus Bound (c. 450 BCE), on the titan who stole fire and paid the eternal price. Vannevar Bush, "As We May Think" (1945), on the memex and the associative nature of human cognition. Jorge Luis Borges, "Funes the Memorious" (1942), on the man who remembered everything and understood nothing. Andy Clark, Natural-Born Cyborgs: Minds, Technologies, and the Future of Human Intelligence (2003), on the extended mind thesis and cognitive integration. Marcus Aurelius, Meditations (c. 170 CE), on the examined life as daily practice. Seneca, Letters to Lucilius, on writing as a mirror for self-knowledge.* --- ### Why Love Needs No Reason **Date:** 2026-01-02 | **Tags:** essay, philosophy, bjj Essay · 13 min read · 2026-01-02 --- Why the deepest commitments in life — to people, to craft, to ideas — resist justification. And why that’s not a flaw. *** Last spring, after a late roll at the gym, a friend asked me why I train. Not casually, the way people ask about hobbies over coffee, but with genuine confusion, the way you might ask someone why they keep returning to a place that has hurt them. I had been limping for two weeks. My fingers were taped. I had a bruise across my ribs that made it painful to sleep on my left side. He looked at me the way a doctor looks at a patient who refuses treatment. I opened my mouth and the words collapsed. Not because I had nothing to say. Because everything I had to say was wrong. I could feel the answer in my chest, dense and certain, the way you feel the floor beneath you before you open your eyes in the morning. But the moment I tried to translate that feeling into language, it cheapened. Every sentence I reached for was a postcard of a cathedral. Accurate, technically. A lie, spiritually. I said something about discipline. Something about the community. He nodded politely, and I could see he had filed it under "things Fardin does that Fardin cannot explain." His conclusion, that the inability to explain indicated an absence of meaning, was the most common and most devastating error a rational person can make. ## The Paradox of Justified Love [#the-paradox-of-justified-love] There is a parlor game that masquerades as depth. Someone asks, "Why do you love them?" and you are expected to answer. You reach for qualities. She is kind. He understands me. We share the same values. The answers feel true in the moment of saying them, the way a photograph feels true when you first look at it. Then the questioning continues, and the photograph starts to curl at the edges. You love her because she is kind. But kindness is not rare. Thousands of people are kind to you in small ways every week. You do not love them. So kindness is not the reason. It is a quality you have selected after the fact to explain a commitment that preceded any quality you could name. Understanding, shared values, physical attraction: the same logic dissolves each of them in turn. Strip the reasons away, one by one. Remove them the way you would remove scaffolding from a finished building, and watch what happens. If the building stands, what you are looking at is love. If it collapses, what you had was never a building at all. It was scaffolding pretending to be a structure, a contract dressed in the language of devotion. Every reason you give for loving someone is simultaneously an argument against your love. If you love her because she is kind, your love is hostage to her kindness. The moment she is unkind, and she will be, because she is human and humans are unkind on Tuesdays and when they are tired and when the weight of being someone's reason for existing becomes too much to carry, your love faces a crisis it was never built to survive. The reason that was supposed to be the foundation turns out to be the fault line. Dostoevsky understood this. In *The Brothers Karamazov*, a woman confesses to Father Zosima that the more she loves humanity in the abstract, the more she despises individual human beings. She can love the idea of a person. She cannot love the person who snores, who forgets, who disappoints her on an ordinary Wednesday for no dramatic reason at all. Zosima delivers the verdict I have never been able to forget: "Love in action is a harsh and dreadful thing compared to love in dreams." Love in dreams is love with reasons, the love you describe on dating profiles and in wedding toasts. Love in action is what remains when the reasons have all failed their auditions, when the person in front of you is simply there, and you discover that your commitment to them has nothing to do with any quality they possess and everything to do with a decision you made at a depth you cannot access with language. ## What the Stoics Got Wrong [#what-the-stoics-got-wrong] Marcus Aurelius, writing to himself in a tent at the edge of the Roman Empire, developed a philosophy of love that has seduced twenty centuries of readers. Love, but hold loosely. Appreciate what you have while accepting its impermanence. When your child is sick, kiss her forehead and whisper to yourself: tomorrow she may die. Not as cruelty, but as preparation. Emotional risk management elevated to spiritual practice. I spent years admiring this. Marcus Aurelius seemed like the adult in the room, the man who had solved the problem of attachment by refusing to attach fully to anything. Then I started training, and I learned he was wrong. Not about loss. About commitment. On the mat, when you attempt a submission, there is a moment where the technique lives or dies. Not the moment of entry. The moment of commitment. The fraction of a second where you have positioned everything correctly and the only thing left is to close the distance between attempt and execution. In that fraction, you must commit your entire body. Hips, shoulders, grip, breath, weight. Everything. If you hedge, if you keep an escape route open, the technique fails. Not because you lacked skill. Because commitment is not a supplement to technique. It is the technique. The half-committed armbar does not become a cautious armbar. It becomes no armbar at all. The mechanics require totality or they require nothing. Marcus Aurelius would have you love your daughter while whispering that she might die. This is the philosophical equivalent of attempting an armbar while keeping your hips open for the escape. It feels wise. It is a guarantee of failure dressed in the language of preparation. The daughter does not receive a father's love. She receives a father's hedge. Nietzsche had a better instinct. Amor fati. Love of fate. Not the good parts. Not on the condition that fate cooperates with your preferences. Love of fate as it is, including the parts that break you. Nietzsche did not say: love fate because it makes you stronger. He said: love fate, period. The "because" would ruin it. Rilke, in the *Letters to a Young Poet*, put it more gently, but the core was the same. He told the young poet Franz Kappus that the task of a human life is not to seek answers to the great questions but to live them. To inhabit them the way you inhabit a room, not trying to escape through the window of an answer but sitting with the question until, someday, perhaps without noticing, you have lived your way into the answer. The Stoic says: prepare for loss by holding loosely. Rilke says: live so deeply inside your commitments that loss, when it comes, finds something worth destroying. I know which one I want to be. ## Kierkegaard's Leap [#kierkegaards-leap] God tells Abraham to take his son Isaac to Mount Moriah and sacrifice him. Not as punishment. Not as a test where the teacher already knows the answer. As a demand without justification, a command that contradicts everything God has previously promised, issued to a man who has built his entire life on those promises. Kierkegaard spent an entire book, *Fear and Trembling*, circling this story the way a man circles a fire that is too hot to approach and too bright to look away from. What was Abraham thinking on the walk up the mountain? Not what was he feeling. What was he *thinking*? Kierkegaard's answer is the most honest thing I have ever read in philosophy: Abraham was not thinking. Not because he was stupid. Not because he was fanatical. Because he had arrived at a place where thought could not follow. Reason had carried him to the edge of the cliff, had catalogued every argument for and against what he was about to do. And then reason stopped. The cliff edge was its boundary, and beyond it was something that reason could name but not enter: faith. The knight of faith looks like everyone else. He goes to work. He eats dinner. But inside, he has committed himself to something he cannot justify, not out of ignorance but out of a full and devastating awareness that justification is not available to him. The leap is not the absence of reason. It is what happens when reason completes itself, reaches its own limit, and discovers that the territory beyond is not empty but full of something it cannot name. This is what love is. The commitment you make when every reason has been examined and found insufficient, when the rational thing to do would be to walk away, and you stay. Not because you have found a reason the analysis missed. Because the analysis was never the right tool for the job. Rumi knew this eight centuries earlier. "Reason is powerless in the expression of love." Scholars have spent centuries trying to figure out whether this was mysticism or philosophy or poetry, as though the sentence needed to be filed in the correct drawer before it could be true. It is true in every drawer. It is true on the mat and in the text editor and in the conversation at two in the morning when someone you love asks you why, and you cannot answer, and the inability to answer is not a failure of your love but the most precise testimony to its depth. ## The Cost of Hedging [#the-cost-of-hedging] I want to be specific about what hedged love looks like, because it does not announce itself. It disguises itself as wisdom, as maturity, as emotional intelligence. It speaks the language of self-care and healthy boundaries and reasonable expectations. And it hollows out everything it touches. The hedged friend is always available but never vulnerable. He will meet you for coffee and listen to your problems with genuine attention but will never tell you his own. He keeps one foot out the door. Not dramatically. In the things he does not say. In the way he is always, always fine. The hedged developer keeps an exit strategy from every project. Picks technologies not because they are the best tool for the problem but because they are the most portable, the most resume-friendly. He is not building something. He is maintaining optionality. And optionality, pursued as a terminal value, is the enemy of everything that matters. The hedged sparring partner never fully commits to the sweep. Seventy percent of his body, thirty percent in reserve. The sweep never lands. Not because the technique is wrong, but because the technique requires a body that has decided, fully, that this sweep is happening, and a body holding thirty percent back has made no such decision. These are not cautious people. Caution is a tactical decision made in service of a larger commitment. The cautious general retreats from one battle to win the war. These people have no war. They have only an endless series of small retreats, each one rational, each one defensible, each one removing them further from the possibility of total investment in anything at all. Simone Weil understood this. In *Gravity and Grace*, she distinguished between attachment that binds you to the beloved as a possession, and attention: pure, undivided, selfless seeing. The kind that does not ask what the object can do for you but simply sees it, fully, without the filter of your own needs and fears. This attention is the opposite of attachment. It is love freed from the gravity of self-interest, and it requires a totality of commitment that the Stoics would have found terrifying. You cannot give this kind of attention while hedging. Seventy percent of attention is distraction with a generous self-assessment. ## The Things Before Reasons [#the-things-before-reasons] I train because I train. I wrote that sentence in the first version of this essay, and it is the only sentence I kept, because it is the only one that was already true. Everything else was explanation, context, scaffolding. This sentence is the building. I did not arrive at training through a cost-benefit analysis. Those calculations can be performed. They have been performed, by actuaries and sports scientists and people who write self-improvement articles for websites that measure everything. The calculations are not wrong. They are irrelevant. They describe the phenomenon the way a chemical analysis describes a meal. Accurate. Entirely beside the point. The first time I was choked unconscious in training, I drove home with a feeling I could not name for three days. It was not fear, though fear was part of it. It was not exhilaration, though exhilaration was part of it. It was the feeling of having encountered something real, something that could not be negotiated with or reframed or optimized away. The mat had tested me in a language that did not use words, and I had answered in that same language, and the conversation had been more honest than any conversation I had ever had in a classroom or a meeting or a late-night argument about philosophy. My body knew something my mind was still weeks away from articulating: this is where I belong. Not because of the reasons. Before the reasons. This is what I mean by pre-rational. Not irrational. Not anti-rational. Pre-rational. The commitment exists in a layer of experience that is older and deeper than the framework of justification. It is the layer where a mother reaches for her child before she has decided to reach. Where a musician's fingers find the chord before the theory names it. Where the words of a poem arrive in the mouth whole, before the conscious mind has approved them. Reason is not excluded from this layer. It is simply not sovereign there. It is a guest, not the host. Rilke told the young poet: "Do not now seek the answers, which cannot be given you because you would not be able to live them. And the point is, to live everything. Live the questions now. Perhaps you will then gradually, without noticing it, live along some distant day into the answer." This is not advice about patience. It is advice about the proper relationship between living and thinking. The things worth doing are not the things you arrive at through argument. They are the things you were already doing before the argument began, the things that were true about you before you had words for them, the things that would survive the destruction of every reason you have ever given for them. I write code because writing code is how I think. Not a metaphor. A description. The act of translating intention into syntax, of taking a vague architecture that exists only in feeling-space and making it precise enough for a machine to execute, is the closest I come to understanding what I actually believe about how things should work. I do not write code and then understand. I understand by writing code. The activity and the comprehension are the same event, and if you asked me to justify the hours, I could give you answers about career and craft and contribution, and all of them would be true, and none of them would be the truth. ## The Weight of Your Own Hedging [#the-weight-of-your-own-hedging] I did not write this essay to make an argument. Arguments are for things that can be decided by evidence and logic, and the territory I am trying to describe is precisely the territory where evidence and logic have done their work and stepped aside. I wrote this essay because I believe, with a certainty I cannot defend, that most of the people reading it are hedging. Not dramatically. Quietly. In the small ways that compound across a lifetime until one morning you wake up and realize that you have never been fully committed to anything, that every relationship and every project and every belief you hold has a back door built into it, that you have spent your life accumulating options and exercising none of them. You have a friend you have not called in months, because calling would require a vulnerability you have not budgeted for this week. You have a project you believe in but have not started, because starting would mean committing to something that might fail, and you have arranged your life so that failure is always theoretical. You have someone you love, and you have not told them, because saying the words would collapse the quantum state of your affection into something definite, something that could be rejected, something that would cost you the comfortable ambiguity of almost. I know this because I have done all of it. I am not writing from a position of mastery. I am writing from a position of recognition. The mat taught me what full commitment feels like in my body, and once you have felt it there, you cannot help but notice its absence everywhere else. The feeling of a fully committed sweep, where your hips and shoulders and grip and intention are all moving in the same direction with nothing held in reserve, is so different from a hedged attempt that they might as well be different activities. And once you have felt that difference on the mat, you start to feel it in your friendships. In your work. In the way you love. Kierkegaard wrote that the knight of faith makes two movements. The first is infinite resignation: the acceptance that what you love may be taken, that the reasons for your commitment may all prove false. The second movement is the one Kierkegaard himself admitted he could not make, could only describe from the outside with the longing of a man pressing his face against a window. The second movement is: you commit anyway. Not despite the risk. Not because the expected value is positive. You commit because commitment is not a response to certainty. It is a response to something older and deeper than certainty, something that has no name in philosophy because philosophy is the discipline of naming, and this thing dissolves under the pressure of being named. I train because I train. I write because I write. I love the people I love because I love them, and if you asked me for a reason, I could give you a hundred, and every single one would be a lie, not because the qualities I would name are not real, but because listing them would imply that my love is a conclusion derived from premises, when it is in fact a premise from which everything else in my life is derived. The things worth doing are the things you would do even if you could never explain why. Not because explanation is impossible. Because explanation, applied to things of this depth, is a kind of betrayal. It takes something whole and breaks it into parts and says, "See? This is what it is." But the whole was always more than the sum, and the act of breaking it was the act of losing the very thing you were trying to show. Commit to something. Not because it makes sense. Not because you have a backup plan. Commit the way you commit to a sweep on the mat: with everything, all at once, nothing held in reserve. Feel the terror of that. Feel how alive you are in the moment of total investment, how the world sharpens into focus the way it never does when you are hedging. This is not recklessness. Recklessness is commitment without awareness. What I am describing is commitment with full awareness, commitment that knows the cost and does not flinch. Love needs no reason. Not because love is blind. Because love sees further than reason can follow, into a territory that reason maps as empty but that is, in fact, the fullest place a human being can stand. --- ## Garden — Stories (Full Content) ### The Remedy for Time **Date:** 2026-04-19 | **Tags:** story, parable, time, knowledge Story · 32 min read · 2026-04-19 --- ## The Reading [#the-reading] The boy read much. By the time he was fifteen he had read enough to understand that he would never read enough. He read in the morning before the house was warm, with a blanket around his shoulders and a book against his knees. He read through dinner, silent at the table while the others spoke. He read past midnight under a small lamp with a shade yellowed from decades of such reading, not his reading but his grandfather's, who had left the lamp and the books and the habit and not much else. The lamp was the first inheritance. The books were the second. His grandfather had died on a Thursday in autumn with a finger still holding his place in a volume of Tacitus, and the boy, who had been eight, had come into the study after the body was taken and had sat for an hour in the chair and had turned the page the old man had been turning when the page stopped. He understood, without being told, that the reading was now his. That the books were waiting. That a book an old man had been reading when he died was the kind of book that chose its next reader the way a coat, hung by a door through a long winter, chooses the next set of shoulders. He began with Tacitus because Tacitus had been left on the table. He moved to Herodotus because Tacitus had mentioned him. He moved to Thucydides because Herodotus had been answered by him. And by the time he was twelve he had understood something about his situation that his grandfather, had he lived another year, might have tried to warn him about. Each book pointed to ten other books. Each thinker referenced three he had never heard of. Each philosophy was a response to a prior philosophy he would have to read first to understand what was being answered. The map of knowledge, which he had imagined as a country he could walk across in a long life, revealed itself to be an ocean. And one lifetime was a wooden rowboat. His sister, who was seven, used to come into the room and sit on the rug and watch him read. She did not ask him to play. She had tried that when he was younger and she was younger, and it had worked, and she had learned that it no longer worked, and she had adapted the way younger sisters adapt, by lowering her expectations to the exact level he was able to meet. So she would sit on the rug with a book of her own, one she could not yet read, and she would turn its pages in rhythm with his, as if she were reading alongside him, as if the act of turning were itself the reading. Sometimes she would look up and say his name. He would not answer. She would go back to her book. She never seemed hurt by this. He came to understand, much later, that it was not because she was not hurt. It was because she had decided, a long time before he noticed, that being in the room with him was more important than being spoken to by him, and she was not going to trade the room for the speech, because she knew she could not have both. He sought out the wise sages in his life, such as he had. The retired teacher on his block kept Plato on the back of the toilet. The priest at the church his family did not attend had once meant to be a philosopher and had compromised. A cousin who had taught himself calculus at thirteen had written nothing since, and worked now at a warehouse counting boxes, and read only on Sundays, and only the New Testament, and only the gospels, and only Luke. Each of them tried, in his own way, to save the boy. The teacher told him to read the Greeks and only the Greeks. Everything since was a footnote to Plato, the teacher said, and if the boy understood Plato he would understand how every argument after Plato was an attempt to escape him, which meant the Greeks were not one option among many but the only door with a country behind it. Spend ten years there, said the teacher, and the rest will be easier than you think. The priest disagreed. He said the boy had to start with Augustine and stay in Augustine until Augustine was finished with him, because Augustine was the first man in the West to write about what it was actually like to have an inner life, and everything since was a commentary on that interior, and without Augustine the boy would be reading about houses without understanding what rooms were for. The cousin said the boy should forget all of it. Mathematics, he said. Only mathematics. Everyone else lies and can be caught lying, but mathematics, when it is true, is true, and when it is false, is false, and there is no third option. He said this in the warehouse on a break, with a stub of a pencil and a napkin, and he showed the boy a proof he had worked out on his own. The proof was elegant. The boy did not fully follow it. The cousin handed him the napkin and told him to keep it, and he did, for a long time, folded inside a book whose title he would later forget. The boy listened. He thanked each of them. And then, because he did not want to choose — because choosing felt like a small death, a quiet confession that one part of the world mattered more than another — he read everything. He read the Greeks and Augustine and the moderns and the mathematicians. He read theology and biology and poetry and letters. He read in the morning and through lunch and past midnight. He read until his eyes hurt and then he closed his eyes and thought about what he had read and then opened them and read more. For a while this felt like progress. Then it began to feel like something else. The more he learned, the more he knew he didn't know. Each new book did not fill the space it was supposed to fill. It enlarged the space. Reading was not an accumulation. It was an excavation that kept revealing how deep the pit went. By eighteen he could not sleep for thinking of it. By twenty he was thin from forgetting to eat, and his hands trembled when he turned the pages, not from hunger but from panic, the steady low panic of a man running from something that was also his home. So he sought a remedy for the problem of time. His sister was fifteen now. She came into the room one night in late autumn. The lamp was yellow. The book he had been reading was on the floor, and he was sitting with his back against the radiator staring at nothing, which was what had replaced reading in the weeks before he left. She sat on the rug. She did not bring a book this time. She sat with her arms around her knees and looked at him. "You're going to go," she said. He did not answer. "I know," she said. "You don't have to." He had told no one. He had been making lists for weeks in the backs of his notebooks: the regions, the stories, the plants each story named, the languages he would need, the provisions. He had thought he had kept it hidden. He looked at his sister's face and understood that he had kept it hidden the way a man keeps his hunger hidden by not eating, which is to say, not at all. "I won't be gone long," he said. She did not react. It was a lie and they both knew it. What he had told himself was that he would be gone a year, two years, maybe three. What he had not let himself say even in the privacy of his own mind was that he did not know how long, and that the not-knowing was the point. "I'm asking you not to go," she said. He did not answer. He wanted to say that she did not understand. He wanted to say that what he was going to find was worth the leaving. He wanted to say that he was going for her, too, that when he came back he would be the kind of brother she had always deserved. He wanted to say many things, all of which were different versions of the same small betrayal, and he could not bring himself to say any of them, because he knew, standing in the doorway of his own departure, that he was not going for her. He was going because the going was what he had decided, and she was one of the things the going would cost, and he had already accepted the cost without having counted it. She sat there for a long time. Then she got up and left the room. She did not slam the door. She did not say anything more. She closed the door quietly behind her, the way a person closes the door on a room they are never going to enter again. He left three days later, before dawn, with the lamp packed at the top of his bag. He did not wake her to say goodbye. He told himself it was kinder. He would have a very long time, later, to learn it was not. He recalled the stories of old, which told of a plant deep beneath the surface of the earth that granted life everlasting. The stories varied. In some, the plant was a flower that bloomed once in a hundred years at the bottom of a sea. In some, it was a fig tree whose roots reached the underworld. In one, a serpent guarded it, and was killed, and the plant was eaten, and the eater lived for a thousand years and still died in the end, which the boy read as a flaw in that version of the story rather than as its meaning. He set himself to the quest of finding it. He traveled through plains where the grass reached his shoulders and moved in wind he could not feel. Through tundras where his breath froze in his beard and snapped off in flakes. Through deserts where he drank his own sweat from a rag. Through mountains where the air thinned until he slept and woke and could not tell which was which. Through forests where he heard animals he never saw, and jungles where the trees pressed together so closely that noon and midnight were separated only by a shade of green. In the third year he met an old man at a crossroads in a country whose name he had already forgotten. The old man was sitting on a stone with a cloth across his knees. He had no belongings and no destination. He asked the boy where he was going. The boy told him. The old man listened, and when the boy had finished, the old man said nothing for a very long time. Then he said: "I went looking for it once." The boy waited. "Did you find it?" The old man smiled in a way that was not a smile. "I did not. And the not-finding is the only reason I am sitting here now." The boy did not understand. The old man saw that he did not understand, and did not try to make him. He said only: "If you find what you are looking for, you will wish you had been sitting on a stone instead. I tell you this because no one told me, and I would have gone anyway, and you will too. But at least you will remember, somewhere under the going, that you were told." The boy thanked him. He walked on. He thought about what the old man had said for a day, and then for an hour, and then not at all. He was young when he began. He was no longer young when he ended. Somewhere along the way he lost track of how long he had been walking, and then he lost track of where he had started, and then he lost track of which direction home had been, and by that time home was an idea rather than a place, and the idea was receding. After years of searching he fell through a tunnel. He did not see it coming. One moment the earth held him. The next it did not. He rolled down the tunnel for what seemed to be forever, and the rolling scarred every surface of his skin, and broke many of his bones, and at some point during the falling he understood that the falling was the answer to his prayer, that he had not found the plant by searching but by ceasing to search, and this understanding arrived without comfort. He thought, for the first time in many years, of his sister's face. He thought of the door closing. Then he thought of nothing, because the rolling would not let him. At last he reached the bottom, nearly dead. There he found a plant with fruit that called to him. It was not a grand plant. It was small, and grey, and its single fruit hung close to the stem like a drop of water that had not yet decided to fall. He could smell it. The smell was not sweet. It was the smell of a thing that had waited a very long time to be eaten. With his last ounce of energy he ripped the fruit from its place in the ground and gulped it down. He felt a pang run through the entirety of his body, through every fiber and every cell, and the pang was not pleasure and it was not pain, it was the particular sensation of something rearranging itself without his permission, and before he could understand what had happened to him he fell unconscious. ## The Hollow [#the-hollow] When the boy awoke he could hardly realize it, for there was no light. It was complete and utter darkness. He could almost see more with his eyelids closed. He couldn't quite remember how he had come to be where he was. He remembered falling. He remembered the rolling. He remembered the fruit. But the pain was no longer in him, and the absence of the pain made the memory feel like something that had happened to a different person. Walking around, he measured out the space with his hands. It was about fifty square feet. The floor was smooth. The walls curved upward and met somewhere over his head. It was a hollow in the rock, a bubble inside the earth the size of a small room, and whatever had made it had made it long before there were hands to touch it. He tried climbing to reach the top, to find the opening through which he had fallen, but the walls were too steep, and offered no bearing for his feet or his hands. He climbed, and slid, and climbed, and slid, and eventually he sat at the bottom of the hollow and breathed, and the breathing was the only sound. He spent what must have been the first year trying to escape. He scraped at the walls with his fingernails. He pounded with his fists. He jumped and clawed and tried to brace himself across the curve of the hollow to lift himself up the way a child lifts himself up a doorframe. He called out. No one answered. He listened. There was nothing to hear. He invented a language of knocks, in case there was someone on the other side of the wall with a patience equal to his own. There was no one. The walls did not respond. The darkness did not respond. The only response was the water, which came every few days from the top of the hollow, and fell on his face when he sat directly beneath it, and stopped falling before he had drunk enough. He was hungry, but there was no food. He was thirsty, but there was no water except the small fall. He waited. The hunger did not become pain, which surprised him until he understood why. He was immortal now. Hunger was information only. It was a clock his body was keeping for no one. Slowly the days passed, though he didn't notice. As he grew weak and weary he could not scrape or pound or climb, and so he lay with his back against the wall, and made marks with his nails for every day he thought had passed. He made them neatly at first, in rows of five with a diagonal through each, then rows of rows, then rows of rows of rows, until there was no system left that could hold the count. He decided, on a day he no longer tried to track, that he would die. He had heard, in the literature of his reading, of men who had died by refusing. He lay on his back and willed himself to stop. He thought of the sister, because he thought her memory might help. He thought of his grandfather in the chair with his finger in the page. He thought of every ending he had ever read, and tried to walk into one of them and close the door behind him. Nothing happened. His body continued its slow empty work. His heart continued its mechanical count. He tried to bash his head against the wall. The wall was not hard enough to break what he was trying to break. He tried to hold his breath. He held it past what a lung is supposed to hold. He passed out. He woke. He was still in the hollow. His breath had started again on its own, without his permission, the way everything in him now started on its own, without his permission, because the fruit had rewritten the contract. He understood, slowly, that he had been given the thing he asked for, and that the gift was the cage. The days turned to months, and the months to years. He realized that he was now immortal. He had known it before in a theoretical way. Now he knew it the way a man knows his own hands. But it made no difference to him in the hollow. He wanted to escape, and could not. He marked so many days on the walls that he couldn't tell them apart from one another. His nails wore down. And then, slowly, over years he could not count, his fingers. He wept when the first finger went. He had been pressing it against the wall to make the mark, and the finger had not marked, and he had looked at it in the dark he could not see in, and had understood with his touch what his eyes could not show him: that the finger ended somewhere before it should have. He did not feel pain. The fruit had taken pain too. What he felt was a small specific grief that did not belong in the catalog of griefs he had brought with him from the world. He wept without sound, because the weeping was a habit he had brought with him from a world with listeners, and there were no listeners here, and the silent weeping lasted longer than any grief he had ever known. He wept for the finger, and for the grandfather, and for the sister, and for every book he had not finished, and for the old man at the crossroads who had warned him. He wept without tears, because his body no longer made them; the fruit had taken that too, along with the hunger and the bleeding and the capacity to die. He wept dry. He wept for what must have been a decade. And then the weeping stopped, because he had used it up, and nothing new came to replace it. His thoughts kept him company. This was the first gift of his immortality, though he would not have called it a gift for a very long time. In his lonely existence he remembered, eventually, why he had sought immortality in the first place: to give himself the time to learn all there was. The memory arrived on a day he could not have identified, while he was lying on his back with nothing to do and nothing to expect, and the old hunger returned to him with the clarity of something he had forgotten he owned. He had no books. He had no teachers. He had no paper and no ink and no walls that had not already been marked past legibility. But he had the mind. He had everything he had ever read, and everything he had ever thought, and everything that had ever been said to him. And he had the time — the terrible time, the limitless time — to arrange and rearrange these things into new shapes. So he decided that he would discover everything for himself, starting from what he already knew. He began with geometry, because geometry needed nothing but attention. He reconstructed the proofs he remembered and derived the ones he did not. He proved, in the dark, over what might have been a hundred years, the propositions of the Greeks, and then the theorems of the moderns, and then theorems no one had proved yet, because he had the time for it, and there was nothing else to do. He named his first original theorem after his sister. He did this without thinking about it, the way a man names a child after a parent because the name is what was available. The theorem concerned the behavior of a particular curve under a particular transformation, and it was, as far as he could tell across his first century of verification, true. Naming it gave him a small warmth he had not expected. He began naming every theorem after someone. His grandfather. The teacher with Plato on the back of the toilet. The priest. The cousin. The old man at the crossroads. He named theorems after people whose names he was not sure he was remembering correctly. He named one after a girl from his school whose face he could still see but whose name would not come, and the theorem took her face as its name, and he proved it and was pleased. He moved to philosophy. He wrote, in his head, a dialogue on the nature of knowledge, with interlocutors he invented and grew to love. He wrote a treatise on justice, and a second treatise refuting the first, and a third synthesizing them. The second treatise, he decided after much consideration, was the one closest to true. He tried to hold onto this. He forgot it within a century and had to re-derive it. He derived it. It was still closest to true. He forgot it again. He wrote novels. He wrote them sentence by sentence, revising each sentence for as long as a sentence seemed to want, and some sentences took him a decade. His proudest was a novel set in a house by the sea, about a brother and a sister who lived there together into old age, and never married, and wrote to no one, and died within a week of each other. The novel was seventy chapters long. He knew it by heart. He revised it, in full, once every hundred years. Each revision was better than the last. By the time he had revised it fifty times it was, he believed, the finest novel ever written in any language, and he was the only person who would ever read it, and this fact, which should have destroyed it, did not. The novel was good on its own terms. The novel did not care who read it. He did not know what to do with this. He did not know whether the novel was a triumph or a curse. He held the keys to the universe but could not escape the confines of the hollow. This is the sentence he would have written, had there been anything to write it on, in the centuries during which the knowledge was his and the uses of the knowledge were not. He understood, eventually, that a theorem proved alone is not fully a theorem. That a novel written in a dark room for no reader is not fully a novel. That the mind, which he had always treated as a sufficient country, was in fact an instrument built to resonate with other minds, and that an instrument played alone, for no listener, in an empty room, is only partially an instrument. He understood this. The understanding did not release him. It did not reach the walls. The walls continued their patient work of being walls. On a night that was not a night, he heard a voice. He had been lying on his back, thinking through the proof of a theorem he had proved a thousand times before, as a way of not thinking through anything else. The voice came from above him. It was small, and clear, and said his name. His name, which he had forgotten, returned to him at the sound of it. He lay very still, in case stillness was the condition of the voice continuing. "You can stop," the voice said. He did not answer. He had not used his mouth in so long that he was not certain the mouth still worked. "You have proved enough things. You have written enough novels. No one will read them. You can stop." He tried to speak. Something in his throat worked. A sound came out that was not a word. "It was not a punishment," the voice said. "The plant did what you asked it to do. You asked for time. You were given time. The rest is yours." "Who are you?" he managed. It took him many attempts. The voice did not answer for a long time. Then it said: "I am the one who asked you not to go." He wept. The weeping was dry, as it had been for centuries, but it was weeping. He wept for a span he could not count. He wept because he had believed, for as long as the belief could stand, that he had imagined her. That she had been a figure in one of the novels he had written and revised. That the brother and sister in the house by the sea were the originals, and the sister in the world above had been a draft of them. It had been easier to believe. To believe the opposite was to remember that he had closed a door on a real face. "I am sorry," he said. "I know," she said. "Tell me you are real." "I cannot tell you that. I am a voice in a dark room. You have been alone for a very long time. You have the strongest reasons in the world to invent me." "Then I have invented you." "Maybe. Does it matter?" He thought about this. It took him, he thought, a very long time, though by this point his measurements of time were the measurements of a man who had stopped believing in minutes. When he had thought about it enough, he said: "No. It does not matter." "Good," she said. "Are you going to stay?" "I cannot stay. I am not the kind of thing that stays." "What are you, then?" "I am what visits you. Once. I am what gets through, for a moment, because you have forgotten something important and the forgetting has thinned the wall." "What have I forgotten?" The voice was silent for a long time. Then she said, so quietly he almost missed it: "You have forgotten that you are allowed to stop." He thought about this for a long time too. He was still thinking about it when he realized she was no longer there. He called her name. He had forgotten it again. He called her old name, the one from the house with the radiator and the lamp, and she did not answer, and he understood that she had been gone for a while, and that he had not noticed. He decided he would stop. He decided this firmly. He lay down and did not think. He did not prove. He did not write. He did not revise. He lay in the dark and tried to be a man who had stopped. He lasted, by his own reckoning, what might have been a year. Then he began again. He could not help it. The theorems came up on their own. The novels demanded their next revisions. The mind, which had been built for this, did this. He could no more stop the work than he could stop the breath that had refused to be held. He understood, in the beginning of his second attempt to be a man, that the voice had been right about the mattering. It did not matter whether she was real. It mattered that she was gone. It mattered that she had come at all. He kept working. He worked for centuries. He worked until he had forgotten that she had visited. He worked until he had forgotten that he had once decided to stop. And slowly, over centuries he did not keep track of because there was nothing left to track, he began to forget. He forgot the names of the sages who had advised him. The teacher with Plato on the back of the toilet. The priest who had compromised. The cousin with the napkin and the elegant proof. He forgot them in that order, teacher first because the teacher's face was the first to dim, and cousin last because the cousin's proof was something he had continued to use, and the use had preserved the cousin a little longer. Then the use wore out, and the cousin went. He forgot the face of his grandfather, whose lamp had waited for his reading. He could remember, for a while, the finger in the page. Then the finger went too. He forgot the color of the grass in the plains, and the smell of the jungle at night, and the taste of the fruit, and the weight of his bag on his shoulders in the first days of the quest. He forgot the old man at the crossroads who had warned him. He forgot the warning. He forgot the regret he had felt when he remembered the warning. He forgot his own name, which had been a small thing anyway, a collection of sounds someone had chosen for him a long time ago. He remembered the theorems. He remembered the novels. He remembered, without remembering why, that he had to escape. The last thing he forgot was his sister's voice saying his name from the rug in the room with the radiator. He did not know, when it went, that it had been the last. He only knew that something had been with him in the hollow, something like a shape at the edge of his thinking, and that at some point he looked for it and it was not there, and he tried to remember what it had been, and he could not. He felt, briefly, a grief he could not locate. Then the grief went too, because there was nothing it could fasten to. The hollow continued. The theorems continued. The novels revised themselves on a schedule he no longer set consciously. The water fell from above and he drank it when it fell. This was the condition of his being. The changes in the hollow happened so gradually that he did not notice. Decades after he first fell, a thin coating of water formed on the bottom. It was not enough to wet his ankles when he sat. It was barely a film. He did not notice it beginning. Centuries later there were a few inches of water, and this he noticed, and he decided it was the ordinary consequence of the rain, and he made no more of it. But to him, who had now been in the hollow so long that his own beginning was a rumor, the water had always been there. He could not remember a time when there had been no water. The water, like the darkness, and like the silence, and like the mind at work, was simply one of the things the hollow contained. The water rose so slowly that it rose without argument. A millimeter in a year. A centimeter in a decade. An inch in a century. It was the patient work of the sky, year upon year, dripping through the one fissure it had found, laying down its small tax on the floor. His attention had long since moved from the floor to the interior of his own head, where whole libraries were being built and torn down and rebuilt, and he did not notice the floor disappearing, because the floor had never been the point. The water rose so high that he was swimming in it. He swam without remembering when he had begun to swim. The swimming became, for a time that was long even by the standards of his imprisonment, the condition of his being. Then the water reached the top of the hollow, and began to carry him up the tunnel through which he had originally fallen. He did not fight it. He did not swim with it. He was a thing the water was moving now, in the slow and indifferent way that water moves things. It occurred to him, somewhere in the long ascent, that he had spent many thousands of years discovering the structure of the universe, and the discovery that was actually carrying him out was a discovery he had not made. The water was not his theorem. The water was what had happened while he was busy with theorems. This thought disturbed him, and then passed, the way most thoughts had come to pass in him over the centuries, like weather. ## The Empty World [#the-empty-world] One fine morning he reached the top. He did not know it was morning, but he saw light for the first time in a span of time that had no name, and his eyes, which had not seen light in all that span and which should not have worked at all, worked. He was lifted onto rock, and the water drained away around him and down into holes he could not see, as if the world had been waiting for him and was now withdrawing its welcome. He lay on the rock for a long time before he understood that he had arrived. The sun was on his face. It was warm. He had forgotten warm. He lay with his eyes closed and felt the warmth, and it was unbearable the way food is unbearable to a man who has not eaten in a month, not because the food is too much but because the body has forgotten what to do with it. He wept without tears. He laughed without sound. The laughter and the weeping were the same movement, and they lasted for what must have been a day or a week or a year. When he opened his eyes he looked around, but was too weak to move. He expected to see nothing familiar. He was old enough that he no longer expected anything, and when he expected nothing, the world obliged. Just rocks, the sunlight, clouds and the wind. No trees. No nature. Certainly no humans. No birds. No insects. No grass. No flowers. No roads. No ruins. No broken walls that might once have been buildings. No shards of pottery. No cairns. No graves. There was rock, and there was sunlight, and there was the wind moving over the rock, and there was sky, and the sky was empty. He understood, slowly, what this meant. It meant that he had outlived every civilization whose knowledge he had reconstructed. It meant that the theorems he had proved had no one left to present them to. It meant that the novels he had written in his head had no readers — not because the readers had refused them, but because the readers had died, every single one of them, and the readers' children had died, and their children, and their species, and the species that might have come after, and there was no one left on the surface of the earth to hand anything to. He had escaped the hollow only to be placed into another. Then, with all the force and fury of a thousand lifetimes, he hurled verbal boulders through the cannons of his mouth at the confines of reality. He cursed the plant. He cursed the sages. He cursed the hunger. He cursed the fall and the hollow and the water that had taken its patient millennia to carry him up to this empty rock. He cursed every book he had ever opened and every question he had ever asked and every minute he had spent learning instead of living. He cursed his own cleverness and his own hunger and the vow he had made at twenty that he would not die ignorant. He cursed the old man at the crossroads, and then he unshaped the curse, because the old man had warned him, and the curse was for the wrong thing. He cursed himself. He cursed himself for centuries. He cursed until the cursing wore the shape of his curses smooth, the way water wears stone smooth. His voice, which had not been used in longer than he could remember, was the only sound in the world, and the world did not answer him. When he was done cursing he was still there. He had believed, during the curse, that the curse would end him. That reality, properly accused, would break, and he would break with it, and there would be some release. There was no release. The rock continued. The wind continued. The empty sky continued. So he began to speak. He spoke the first theorem he had ever proved in the hollow. He said it aloud, in the order of its steps, with the reasons at each step. It took him a day. The wind carried the words away. There was no one to receive them. He spoke the second theorem. It took him three days. He spoke, over the course of what might have been a year, every theorem he had ever proved. Then he spoke the philosophy. The dialogue on the nature of knowledge, with its invented interlocutors. The treatise on justice and its refutation and its synthesis. He performed the whole dialogue, playing each voice, pausing where the text demanded, and nothing listened. He spoke the novels. He told the novel about the brother and sister in the house by the sea. He told it in full, seventy chapters, sentence by sentence as he had revised them, and when he reached the last chapter — the one where the sister dies in the night and the brother finds her in the morning — he stopped, because he had never been able to stop crying at that chapter, and he still could not, and the crying took him out for a long time. When he came back he continued. He told every novel he had written in the dark. He told the dialogues. He told the epics. He composed the music aloud, humming what he had composed in the silence, and the humming was the sound of a man whose throat had forgotten tone but was trying. The sound was terrible. He hummed anyway. He hummed for centuries. He came to understand, slowly, that the speaking was not for the wind. The wind was not a listener and he had stopped pretending it was. The speaking was not for him either. He had already held all of this inside his head for as long as he could remember; speaking added nothing. He did not know what the speaking was for. He only knew that he could not stop. After a very long time he came to believe that the speaking was the work itself. That the theorem, to be fully a theorem, needed to be spoken, even to nothing. That the novel needed to be told, even to nothing. That the knowledge he had gathered, alone, in the dark, was a half-thing, and that the speaking was the second half, and that the second half was now being paid, very late, to a room that had emptied while he was paying the first. He did not know whether this belief was true or whether he had invented it because he needed a reason to keep speaking. By the time he had entertained the question for a thousand years he had stopped caring which it was. He spoke until there was nothing left to speak. When there was nothing left to speak, he stopped. He was still there. The sun rose and set. The wind moved. The rock held him. He lay on his back and looked at the sky, which had never had a cloud in it since he had emerged, or perhaps had always had clouds, or perhaps both, since the two were indistinguishable now. He began to forget again. He forgot the novels he had just told. They left him in the order he had told them. First the brother and sister in the house by the sea, because it was the first one he had spoken, and the speaking had worn it down. Then the next. Then the next. The theorems left him in reverse order of their speaking. He forgot the dialogues. He forgot the philosophy. He forgot the music. He forgot the hollow. He forgot the voice that had visited him in the hollow. He forgot the fall. He forgot the crossroads. He forgot his bag and the lamp at the top of his bag. He forgot the grandfather with his finger in the page. He forgot his sister. He had forgotten her before, in the hollow, and remembered her briefly when the voice came, and forgotten her again after. Now he forgot her in a different way. Not as a fact he had stopped being able to access, but as a place his mind stopped going, until eventually the place itself did not exist and there was no absence to feel. He forgot that he was a person. He lay on the rock and did not think. He was not unthinking the way a man who has stopped thinking is unthinking. He was unthinking the way a rock is unthinking, because there was nothing in him that thought, and the absence was so complete that it did not know itself as an absence. Centuries passed. Millennia. The rock weathered. He did not weather. He was the only thing that did not weather. He lay among rocks that eroded around him, and he remained. The rocks became sand. The sand blew away. New rocks rose from the earth beneath. He remained. He became, effectively, a feature of the landscape that no one was observing. A thing the earth could not process. The one remainder from a vanished world. ## The Second Fruit [#the-second-fruit] On a morning that did not belong to any season, because there were no seasons left, he opened his eyes. He had not known his eyes had been closed. He did not know why they had opened. He lay where he had been lying for longer than he could have begun to count, and he looked, for the first time in an age, at the world next to him. Something had grown beside him. It was a plant. It was small, and grey, and a single fruit hung from its stem, close to the stem, like a drop of water that had not yet decided to fall. It had the smell of a thing that had waited a very long time to be eaten. He looked at it. He did not know what it was. He did not remember the first plant. He did not remember any plant. But he looked at it, and something in him, older than his mind and older than the forgetting, recognized it. Not as itself. As a kind. As the kind of thing that is offered. He understood, without language for the understanding, that the plant was a question. He did not know which answer was which. If he ate it, it might end him. The first plant had made him immortal; perhaps the second made an immortal die. Perhaps it was the reverse of the first. Perhaps it was the cure for what the first had done. Or, if he ate it, it might begin him again. A new quest. A new fall. A new hollow, with new water, patient and slow, rising through centuries he would not notice. A new surface, emptier than this one. An infinite regress of hollows. Or, if he ate it, nothing at all would happen, and he would simply have eaten a fruit on a dead world and been still lying there afterward, only slightly less hungry. He looked at the plant for a very long time. He did not reach for it. The sun moved across the sky. The fruit hung close to the stem. The wind moved, and the plant did not move with it, because the plant was small and low and held itself against the rock. And then, without warning, without source, without memory behind it to explain it, a small hand came to rest on a rug beside him in the dark. He did not know whose hand. A voice said his name, a name he no longer had. He did not know whose voice. A door closed quietly somewhere he could not see, and the closing moved through his chest the way the slow water had moved through the hollow for ten thousand years before he noticed. He did not know which door. He did not know which name. He did not know who had gone and who had stayed and who had waited on the other side of the wood for him to come back. He only knew that something in him was still there that could be reached. When his hand, which had no fingers, moved toward the fruit, it moved without his deciding. And the weeping was not dry. --- ## Now — What I'm Doing This Week ### Reading: Designing Data-Intensive Applications — Martin Kleppmann Re-reading the replication and consistency chapters. The way he frames databases as distributed-systems-with-opinions keeps shifting how I think about my own stack. _Updated 2026-04-20_ ### Thinking: Systems as lossy compression Whatever we do costs us to lose parts of it. The question I keep circling: can you recreate a system inside itself, recursively, without loss? Game of Life inside Game of Life. Minecraft computers inside Minecraft. Reality inside reality. Link: https://fardiniqbal.com/docs/garden/essays _Updated 2026-04-20_ ### Lifting: Powerhouse, 2026-04-20 — light full-body First session back after a hamstring strain. Rebuilding from the bottom of the rep range. Details below. Link: https://fardiniqbal.com/docs/body _Updated 2026-04-20_ ### Practicing: Jiu-jitsu — Only Way Out, Volume 01 (Glick / Danaher) Conceptual foundation before any new move. Three principles: get the back to the floor, fight for inside position, retract rather than allow extension. Four skills: grip fighting, the elbow cut, the shoulder roll, standing up. Link: https://fardiniqbal.com/docs/body/mat _Updated 2026-04-20_ ### Building: Tiny Steps, Tiny Thoughts, Tiny Time Keeper Six-app healthcare SaaS ecosystem for a pediatric therapy agency — 200+ therapists, production every day. I also rewrote the front door of this site today so career isn't the first thing you see. Link: https://fardiniqbal.com/docs/craft _Updated 2026-04-20_ ### Chasing: Bug-bounty operator practice — Sprint 0 live Stood up the operator practice today with a structured PRD, Sprint 0 calendar, and kill-switch gates at M3 / M6 / M12. Research is the product, content is the distribution, skills are the features, reputation is the asset. Link: https://fardiniqbal.com/docs/craft/initiatives/bug-bounty _Updated 2026-04-21_ ## Skills & Technologies **Languages:** TypeScript, Ruby, Python, C, SQL, Swift **Frontend:** React 19, Next.js 16, Tailwind CSS v4, Framer Motion, SwiftUI **Backend:** Rails 8.1, Convex, PostgreSQL, Drizzle, Express.js, FastAPI **Infrastructure:** Vercel, Fly.io, Render, AWS, Docker, GitHub Actions **AI:** Claude Code, Gemini API, OpenAI API, WebLLM, WebGPU **Security:** Splunk, CrowdStrike Falcon, HIPAA Compliance ## Changelog (Site Activity Log) ### 2026-05-02 — Killed the CRT vocabulary, switched to Fraunces and warm paper (reconsidered) Sitewide pivot from the retro-terminal aesthetic to an editorial one. Dropped VT323, Anonymous Pro, scan lines, film grain, and boot flicker. Body type is now Fraunces at 18px on a hue-55 paper background. **Tags:** meta, changelog, design, typography, css, design-tokens, light-mode, fraunces, editorial **URL:** https://fardiniqbal.com/docs/changelog/2026-05-02-editorial-pivot-fraunces-warm-paper ### 2026-05-02 — Switched off Glick, started Gordon Ryan's Foundation of Offense (reconsidered) Brian Glick's Only Way Out wasn't granular enough to embody. Moved to Gordon Ryan's Foundation of Offense V01 — added a verbatim transcript, a new principle, and a new skill to the Mat. **Tags:** meta, changelog, bjj, mat, content, sources, gordon-ryan, danaher **URL:** https://fardiniqbal.com/docs/changelog/2026-05-02-foundation-of-offense-v01 ### 2026-04-26 — Wired Volume 02 into the Mat (shipped) Brian Glick's Only Way Out Volume 02 transcribed verbatim, plus the first 12 moves wired into the graph as edges across 6 positions and a new principle. **Tags:** meta, changelog, bjj, mat, content, graph **URL:** https://fardiniqbal.com/docs/changelog/2026-04-26-wired-volume-02-into-the-mat ### 2026-04-23 — Graceful fallback on /api/chat when the Gateway is down (shipped) When the AI Gateway is down or the request is malformed, /api/chat now returns a 503 JSON envelope pointing agents to /llms-full.txt, /api/mcp, and /.well-known/mcp.json instead of a bare 500. **Tags:** meta, changelog, chat, api, agents, mcp, resilience, ai-gateway **URL:** https://fardiniqbal.com/docs/changelog/2026-04-23-chat-fallback-envelope ### 2026-04-23 — Deleted the eight legacy top-level routes; 308s now guarded by a spec (removed) Deleted the eight pre-Fardin-Docs top-level routes — about, work, blog, contact, uses, failures, for-ai, interview — 2,298 lines gone. The 308 redirects in next.config.ts cover every legacy URL, and a Playwright spec asserts they still land on the right /docs/* target. **Tags:** meta, changelog, routing, cleanup, redirects, next-config, adr-021, playwright **URL:** https://fardiniqbal.com/docs/changelog/2026-04-23-deleted-legacy-route-folders ### 2026-04-23 — Turned the MDX-never-reads-data rule into a pre-commit failure (shipped) Added a pre-commit hook that fails the commit if any MDX file imports from @/data/*, imports @/lib/data-registry, or string-references a content/data/*.jsonl path. Closes F10 from the concept audit. **Tags:** meta, changelog, mdx, pre-commit, tooling, architecture, data-registry, adr-003 **URL:** https://fardiniqbal.com/docs/changelog/2026-04-23-mdx-boundary-pre-commit-guard ### 2026-04-23 — Killed the last three metaphor fields in the frontmatter schema (refined) Renamed the three surviving metaphor fields — wing→section, affectTone→mood, exhibit→homeSlot — across 143 MDX files and the whole schema layer. A codemod did the migration in one pass. **Tags:** meta, changelog, schema, frontmatter, rename, codemod, breaking **URL:** https://fardiniqbal.com/docs/changelog/2026-04-23-renamed-wing-affecttone-exhibit ### 2026-04-23 — Tightened the frontmatter contract across 142 pages (refined) Deleted `domain`, required `wing` + `genre`, renamed `growthStage` to `stability` and gated it to the genres where it means something. 142 files migrated by codemod in one pass. **Tags:** meta, changelog, schema, frontmatter, refactor, fumadocs, types, codemod **URL:** https://fardiniqbal.com/docs/changelog/2026-04-23-schema-purity-pass ### 2026-04-20 — Started a lift log (shipped) Lifts area launched under the Body wing. Same rule as the Mat — only sessions that actually happened, no programmed-but-skipped, no future plans. **Tags:** meta, changelog, body, lifts, data, infrastructure **URL:** https://fardiniqbal.com/docs/changelog/2026-04-20-started-a-lift-log ### 2026-04-19 — Rebuilt the education page as a docs-native sourced reference (shipped) Rewrote /docs/about/education from a flat course list into a sourced reference. Every course expands to the official SBU Undergraduate Bulletin entry. 38 courses, 14 departments, grades color-coded without shame. **Tags:** meta, changelog, about, education, docs, components, stony-brook, bronx-science **URL:** https://fardiniqbal.com/docs/changelog/2026-04-19-education-page-as-sourced-reference ### 2026-04-18 — Cleaned up sidebar redundancy sitewide (refined) Every folder in the docs used to render twice in the sidebar — once as the parent, once as the index child. Fixed it everywhere at once. **Tags:** meta, changelog, fumadocs, ux, cleanup **URL:** https://fardiniqbal.com/docs/changelog/2026-04-18-cleaned-sidebar-redundancy ### 2026-04-18 — Shipped the changelog apprentice (shipped) A post-commit hook hands every commit to Claude Opus 4.7. Most get skipped. The ones that ship write themselves into five surfaces. **Tags:** meta, changelog, automation, ai, opus **URL:** https://fardiniqbal.com/docs/changelog/2026-04-18-shipped-the-changelog-apprentice ### 2026-04-18 — Shipped the Mat (shipped) BJJ documentation area under the Body wing. Volume 01 of Brian Glick's "Only Way Out" transcribed verbatim. Graph-native schema — positions as nodes, moves as edges. **Tags:** meta, changelog, bjj, mat, docs **URL:** https://fardiniqbal.com/docs/changelog/2026-04-18-shipped-the-mat ### 2026-04-17 — Migrated the site to Fardin Docs (shipped) Everything now lives under /docs/*. 24 projects, 50 interview Q&A, and 7 essays imported as MDX. **Tags:** meta, changelog, migration, fumadocs **URL:** https://fardiniqbal.com/docs/changelog/2026-04-17-migrated-to-fardin-docs ### 2026-04-14 — Built the AI-native skeleton (shipped) llms.txt variants, MCP server, knowledge graph, JSON Feed, profile API, AI discovery manifest, JSON-LD schemas. The infrastructure underneath everything that came after. **Tags:** meta, changelog, ai-infrastructure, mcp, llms-txt **URL:** https://fardiniqbal.com/docs/changelog/2026-04-14-built-the-ai-native-skeleton ### 2026-04-14 — Redesigned the whole site (refined) Design system with primitive tokens, Instrument typography, the Explore component, command palette, global search, Interview page. The same day as the AI infrastructure push, I rebuilt the interface on top of it. **Tags:** meta, changelog, design-system, typography, interview **URL:** https://fardiniqbal.com/docs/changelog/2026-04-14-redesigned-the-whole-site ### 2026-04-13 — Dropped seven essays (shipped) 25,000 words of long-form writing in a single push, including the Axioms piece that later became a voice anchor for the whole site. **Tags:** meta, changelog, writing, essays **URL:** https://fardiniqbal.com/docs/changelog/2026-04-13-dropped-seven-essays ### 2026-04-11 — Elevated the portfolio (shipped) Full redesign. Agentic DX touches, radio, mobile-first responsive, cleaned-out features that weren't earning their keep. **Tags:** meta, changelog, redesign, homepage, mobile **URL:** https://fardiniqbal.com/docs/changelog/2026-04-11-elevated-the-portfolio ## Contact - Email: iqbal11219@gmail.com - GitHub: https://github.com/FardinIqbal - LinkedIn: https://linkedin.com/in/fardin-iqbal - Site: https://fardiniqbal.com