[ { "url": "/notes/the-headless-brain/", "title": "The Headless Brain: Why We Stopped Opening Obsidian and Handed It to Our AI Workers", "excerpt": "Most 'Second Brain' systems fail because the maintenance overhead exceeds the value. Here is how we turned our Obsidian vault into an invisible, headless memory engine for our AI workers—and why we open-sourced the starter kit.", "archetype": "craftsman", "archetypeTag": "Workbench", "date": "2026-09-15", "readableDate": "September 15, 2026", "content": "Most Personal Knowledge Management (PKM) systems fail for the exact same reason home gyms collect dust: the maintenance overhead exceeds the daily value. You spend three weeks down an internet rabbit hole designing the perfect note-taking architecture. You color-code tags, configure Dataview tables, tweak theme CSS, and marvel at your dazzling, celestial graph view. Then real life happens. Tax receipts pile up on the counter, three client deadlines hit at once, the tractor needs a hydraulic hose replaced, and opening your note app suddenly feels like clocking in for a second, unpaid shift as a digital museum curator. So you stop opening it. The notes freeze in time. The junk drawer wins. For years, I struggled with this exact gravity. I think in systems, data flows, and code. My wife and creative partner, Ivy, thinks in story, human resonance, and narrative connection. Together, we operate Camwyn Co. as an independent house of projects—incubating software like ManyHats Ledger , stewarding heritage livestock at Mema's Inclination, and running literary advisory work at Poetic Entanglement. We desperately needed a shared, single source of truth across our ventures. But I knew that if that system required Ivy (or anyone else on our team) to manually wrangle Markdown formatting, manage Git merge conflicts, or memorize folder taxonomies, it would die on the vine within a month. We didn't need another app to look at. We needed a headless brain. Doing this setup yourself, with no one else to share it with? A few sections below assume two people. If you're the one who'll actually run the setup steps (Step 2's script, Step 3's config editing), you can skip From Conversational Writers to Autonomous Coding Agents (that's about keeping two people's parallel workflows in sync) and skip One More Board on the Bench and Part Two entirely (the hosted, multi-user build only solves a sharing problem you don't have). On one device? Skip the sync step too (Step 1 under The Realization ). The Real Problem: Don't Double the Noise is still worth reading solo — it's not about sharing, it's about what your own mind needs from a tool. And if you're the non-technical reader hoping to skip the terminal entirely: I'll be honest that Steps 2 and 3 below still require running a script and editing a config file. That's the real bar, not whether you're sharing a vault. If that's not something you want to do yourself, you're exactly the case The Real Problem describes — the fix isn't a simpler guide, it's having someone technical set this up for you once. Everything after that, in How to Use It Daily, works the same for you as it does for Ivy. The Discovery: Courtney, Tiago, and Two Very Different Brains The conceptual breakthrough didn't happen in a vacuum. It started with my friend Courtney Robertson , who wrote insightfully about cutting through brain fog by using LLMs as an autonomous synthesis layer over an Obsidian wiki. Courtney's article introduced me to Tiago Forte's P.A.R.A. Method ( Building a Second Brain ). The moment I understood PARA, I fell in love with it. Tiago gave the world a brilliant, pragmatic taxonomy for organizing digital life by actionability rather than academic subjects: Projects: Active initiatives with fixed finish lines. Areas: Long-term domains of responsibility with continuous standards (brand identity, farm operations, finances). Resources: Reference libraries and playbooks. Archives: Cold storage for completed milestones. For my systems-architect brain, PARA was poetry. It made complete structural sense. The Real Problem: Don't Double the Noise Then came the real-world collision with human nature. Ivy is non-technical, but more importantly, her brain is already a living, intuitive mind-map. She naturally holds narrative arcs, emotional resonance, and brand connections in her head without needing a screen to tell her where they connect. When she looks at software like Obsidian—particularly the sprawling visual graph views, complex plugins, and nested folder trees—it doesn't bring clarity. It just doubles the noise. To her, it felt like putting an unnecessary layer of software bureaucracy over a creative process that already worked effortlessly in her mind. She didn't want to learn Obsidian. In fact, she didn't want to adopt any new software. Her own internal mental model worked just fine, thank you very much. And she was completely right. We wanted her to have full access to the collective brain of our studio—to query our brand guidelines, check project statuses, and record dispatches. But forcing her to adopt an app that conflicted with how her mind naturally operates would have been a catastrophic failure of system design. So we flipped the question on its head: What if we built a Second Brain so seamless that she never had to open Obsidian at all? The Realization: The Filesystem Is the Database Obsidian's greatest architectural genius is not its desktop interface. It's the fact that an Obsidian vault is just a clean, local directory of plain Markdown ( .md ) files sitting on your physical hard drive. No proprietary database binary. No cloud lock-in. No SaaS subscription holding your life's work hostage. Because the vault is just a folder of text files, we realized we could bypass the user interface entirely using the Model Context Protocol (MCP) and Steven Stavrakis's brilliant obsidian-mcp server. +-------------------------------------------------------------+ | Ivy's Computer | | | | +---------------------+ +--------------------+ | | | ChatGPT Desktop | ------ | obsidian-mcp | | | | (What Ivy sees) | MCP | (Headless Server) | | | +---------------------+ +---------+----------+ | | | Reads/Writes | | v | | +--------------------+ | | | Synced Vault Files | | | | (No App Running!) | | | +--------------------+ | +-------------------------------------------------------------+ Here is what happens in practice: Invisible Sync: We keep our master vault synchronized across machines in the background using End-to-End Encrypted (E2EE) Obsidian Sync. Headless MCP Connection: We hooked obsidian-mcp into our AI desktop clients (Ivy uses ChatGPT Desktop on Windows; I use Claude Desktop and Antigravity IDE ). The Zero-Friction Experience: Obsidian does not need to be open on Ivy's computer. She simply opens ChatGPT, which she already uses every day, and talks to it naturally: Can you search our Camwyn vault and give me the brand colors and approved taglines for ManyHats? (ChatGPT silently queries the vault via MCP tools and responds with the exact hex codes). Draft a 2-paragraph dispatch about winter preparations for the orchard and save it to Dispatches. (ChatGPT reads our brand voice rules, writes the essay, and calls obsidian_create_note to create the .md file on her disk). Two seconds later, that new dispatch syncs to my machine. Neither of us had to touch a file tree or fiddle with YAML. Prerequisite: Connecting custom MCP servers in ChatGPT Desktop requires ChatGPT Plus, Pro, Business, Enterprise, or Edu — it's not available on the Free plan. (Separately: ChatGPT's own upload-based Skills feature is Business/Enterprise/Edu-only, but this setup doesn't use it — the AI CONTEXT.md grounding here comes from a pasted custom-instructions block, available on any paid plan.) The Secret Sauce: The AI Constitution ( AI CONTEXT.md ) Why doesn't the AI generate generic, corporate-slop filler? Because at the root of the vault sits a single file: AI CONTEXT.md . This note acts as the master constitution for every AI worker that touches our knowledge base. It outlines: Our Operating Thesis: Smart can be warm. Ambition can have soul. Serious work can still be fun. Ubiquitous Vocabulary: Exactly what words we use—and which marketing buzzwords ( synergize , leverage , game-changer ) are strictly banned. Editorial Archetypes: Guidance on when to speak in the Craftsman voice (tactile, build quality, workshop joinery) versus the Storykeeper voice (hospitality, memory, human connection). Operational Guardrails: Rules requiring the AI to read before editing, preserve frontmatter schemas, and append timestamped worklogs with author attribution ( ### 2026-09-08 — @ivy ). When an AI worker is anchored to an authoritative constitution and has hands into your project history, it stops acting like an erratic chatbot and starts acting like an aligned team apprentice. From Conversational Writers to Autonomous Coding Agents What makes this headless architecture so powerful is that it doesn't just work for conversational desktop chats—it scales all the way up to autonomous engineering. On my side of the workbench, our IDE agents (running in Google Antigravity, Claude Code, and Cursor) connect to the exact same vault using custom agent skills. While Ivy is using ChatGPT to brainstorm dispatches or review brand voice, my coding agents are autonomously reading Architectural Decision Records (ADRs), keeping sprint worklogs updated, and re-indexing master Maps of Content (MOCs) directly from our active Git codebases. Crucially, because the coding agents read AI CONTEXT.md and our brand directives, they don't just write functional code in a vacuum—they actively enforce our design tokens, respect our architectural constraints (like strict 0px border radius), and craft UI microcopy, button labels, and error states that speak in the exact same grounded, hospitable brand voice that Ivy curates. Two completely different people, working in two completely different environments, interacting with the exact same shared memory—with zero manual data entry or software friction on either side. Building the Jig (And Giving It Away) In a woodshop, when an off-the-shelf tool doesn't make the cut, you don't buy a factory. You make a jig. Once we got this headless brain running smoothly between our own desks, we realized how many solo builders, creative studios, and multi-disciplinary teams are suffocating under the weight of disorganized notes and rigid productivity apps. So we packaged the entire architecture into an open-source starter kit: 👉 Headless AI Second Brain Starter Kit on GitHub The repository includes: The Sanitized PARA Skeleton: Pre-structured folders ( 00-INBOX/ , Projects/ , Areas/ , Resources/ , Archives/ ) with starter MOCs and Dataview task queries. The AI Constitution Template: A fill-in-the-blanks AI CONTEXT.md to establish your brand voice and domain definitions. Plug-and-Play Connectors: Exact form setup instructions and JSON configuration files for ChatGPT Desktop , Claude Desktop , and Antigravity / Cursor . 1-Click Setup Scripts: Automated PowerShell and Bash installers for Windows and macOS. You can click Use this template on GitHub, run the 10-second setup script, paste your vault path into your AI assistant, and start having real conversations with your knowledge base in under five minutes. One More Board on the Bench Everything above is Phase 1 — the version any solo builder or small team can stand up in an afternoon, with a synced vault and a paid Obsidian Sync subscription, no server to rent and no infrastructure to babysit. It's still exactly what we'd tell someone to start with. Since writing this, our own setup outgrew it. Two people, two vaults, and the question of what happens when someone's laptop is closed pushed us toward something bigger: a shared, hosted vault that Ivy and I both reach the same way, from anywhere, with no local server tied to either of our machines. Building that — and everything that broke on the way there — is Part Two. Tools That Get Out of the Way Software should never demand that you become someone else just to use it. If you are a systems architect who loves terminals, you should be able to live in the terminal. If you are a writer or strategist who loves natural conversation, you should be able to chat without opening a code editor. A good tool doesn't force everyone at the table to hold the hammer the same way. It just holds the workpiece steady, makes the cut clean, and gets out of the way so you can get back to the work that matters." }, { "url": "/notes/building-the-jig-why-we-incubate-our-own-tools/", "title": "Building the Jig: Why We Incubate Our Own Tools", "excerpt": "In a woodshop, when an off-the-shelf tool doesn’t make the cut, you don’t buy a factory. You make a jig. That’s how we build software at Camwyn & Co.", "archetype": "craftsman", "archetypeTag": "Workbench", "date": "2026-09-10", "readableDate": "September 10, 2026", "content": "If you spend enough time around a woodshop, you eventually learn the magic of a jig . A jig isn’t a commercial tool you buy in a shiny blister pack at the hardware store. It’s a custom fixture you build right on your own bench—out of scraps of maple or plywood—specifically designed to hold an awkward workpiece steady so you can make a repeatable, impossible cut without losing a finger. You build a jig because off-the-shelf tools are either too generic to solve your exact problem, or so bloated with complicated attachments that setting them up takes longer than making the cut itself. That is the foundation of how we incubate ventures at Camwyn Co. We don’t do speculative market research. We don’t build pitch decks chasing venture capital. If a problem doesn’t create real, frustrating friction in our own daily life, it doesn’t earn a spot on our bench. The Multi-Schedule Tax Nightmare Take ManyHats Ledger , for example. For years, our household finances have looked less like a tidy corporate balance sheet and more like an obstacle course. On any given year, our tax return is juggling: Schedule C: Independent engineering management and consulting. Schedule F: Farm operations, feed receipts, and heritage livestock up in the North Country. Schedule E: Property, rentals, and physical assets. If you’ve ever tried forcing that multi-entity reality into mainstream accounting software, you know the special flavor of dread it inspires. The big legacy platforms want to treat you like a Fortune 500 enterprise. They want double-entry journals, chart-of-accounts hierarchies, and monthly subscription tiers that cost more than my first drill press. Meanwhile, the lightweight consumer apps assume you have exactly one W-2 job and a checking account. The result? The dreaded Shoebox of Chaos . Receipts pile up on the counter. The cognitive wall of dread grows higher every week. I don’t claim to have ADHD myself, though I occasionally tease Ivy that she has enough creative tangents for three households. But whether your brain is neurodivergent or simply overloaded by running four different operations, the effect is the same: when a tool is painful to use, you stop using it. From a Quick Script to the Workbench The very first version of ManyHats wasn’t a software company. It was a custom jig. Earlier this year, staring down another tax season with a pile of unsorted papers, I cobbled together a rough script hooked into a spreadsheet just to survive without losing my mind. It wasn’t pretty, and there were no slick marketing pages. But it did one thing flawlessly: it let me throw mixed receipts into distinct buckets in seconds, tag the right tax schedule, and get back to work. Over the months that followed, we stress-tested that prototype against real life. We refined the edges. We added OCR extraction and AI categorization so a blurry receipt from the feed store or a software subscription gets sorted with zero manual typing. What started earlier this year as a rough shop jig on our own kitchen table quickly hardened into a proper tool—something clean, fast, and completely stripped of corporate bloat. Why the Workshop Door Stays Unlatched Which brings us to the other half of Camwyn Co. People often ask why we leave an open door for outside projects on our site—what we call The Next Thing . It’s because the best collaborations happen the exact same way as our internal tools. When you spend decades running farms, managing remote engineering teams, writing books, and building custom systems from scratch, you don’t just accumulate skills—you accumulate a shop full of well-tested jigs. You know where ideas get stuck. You know how easily a brilliant creative spark can get choked by operational friction, bloated software, or bad advice from people who have never actually built a thing with their own hands. We don’t act like a traditional agency with slick slide decks and twelve account managers. We treat our studio like an atelier . If you’re a founder, a creator, an operator, or someone sitting on a stubborn, unsolved problem that off-the-shelf solutions can’t seem to fix: bring it to the bench. You don’t need a 40-page business plan. You just need a genuine spark, a real problem worth solving, and the willingness to look at the grain of the wood and ask: What kind of jig do we need to build to make this work? Tools That Get Out of the Way Whether we’re building an internal tool like ManyHats or partnering with someone on a brand-new venture, the philosophy doesn’t change. We don’t build software to pitch to investors; we build things so people can get back to living their lives. A good tool doesn't ask you to change how your brain works. It just holds the workpiece steady, makes the cut clean, and gets out of the way." }, { "url": "/notes/at-47-im-starting-a-company-with/", "title": "At 47, I’m Starting a Company With My Husband", "excerpt": "After 28 years of marriage, this could either be our best idea yet or provide excellent material for this newsletter.", "archetype": "storykeeper", "archetypeTag": "Chronicle", "date": "2026-09-08", "readableDate": "September 8, 2026", "content": "Originally published by Ivy Page on Poetic Entanglement . There is a particular sentence in our marriage that should probably come with a warning label: “You know what we should do?” Nothing financially conservative has ever followed it. Read the full dispatch on Poetic Entanglement →" }, { "url": "/notes/its-1-am-and-my-wife-asks-you-know-what-we-should-do/", "title": "It’s 1 AM and My Wife Asks, “You Know What We Should Do?”", "excerpt": "When your wife of nearly thirty years asks a late-night question that starts a company, you don’t jump to pitch decks. You map the dependencies.", "archetype": "architect", "archetypeTag": "Blueprint", "date": "2026-09-08", "readableDate": "September 8, 2026", "content": "Most people would roll over and say go to sleep. But after nearly thirty years together, I already knew we were in trouble. In our house, the dynamic has always been pretty clear: I once told Ivy that she’s the creative fairy and I’m the architect. She catches the spark out of thin air—the story, the emotional resonance, the impossible idea that suddenly feels urgent. I’m the one who looks at the spark and immediately starts mapping the dependencies, calculating the load, checking the foundation, and figuring out what happens when fifty people try to walk through the door at the same time. So when she pitched starting a company together, my brain didn’t jump to pitch decks or incubator hype. I’ve spent my life moving around. When you move as much as I have, you become a chameleon of sorts. You learn how to walk into almost any room and fit in—whether that’s a living room with our grandkids running circles around the rug, an appraisal crawlspace checking floor joists on a commercial property, a kitchen full of line cooks slinging pizzas during a Friday night rush, or a tech all-hands with millionaire founders. I can talk shop with anyone without becoming one of them. I don't do tech-elite pretension, and I don't buy into jargon that mistakes complexity for intelligence. Back when I wrote and performed poetry, I used to get into arguments with other writers about language. I’ve always believed in writing for the widest audience possible—plain, rhythmic, punchy words that hit you in the gut without needing a literature degree to decipher them. If you can’t say it plainly, you probably don’t understand it well enough yet. That’s how I approach systems, too. At 55, you stop building things to impress people who will never sit at your kitchen table. Sure, who doesn’t want to build a magnificent edifice that dominates the city skyline? I’ve felt that pull. I’ve wanted that. But not anymore. I look for legacy in quality, not scale. I want to build things that last—things people reach for because they’re actually a pleasure to use. The goal is taking a task from a dreaded “Ugh, I have to do this...” (heavy sigh) to “Hang on a second, let me knock this out real quick” (done). The farm is our first legacy: building something we can hand down to future generations, and stewarding heritage breeds so they endure for generations, too. ManyHats is that same impulse in software—building good, honest tools that feel right, like reaching for a particular hammer because you love the way it fits your hand. From my side of the workbench, that’s what Camwyn Co. is all about. We didn't start this as a venture-backed startup sprinting toward an exit, but as an atelier —a working studio with a heavy timber workbench on one side and a kitchen table on the other. Here’s what’s on our bench right now: ManyHats Ledger: A clean, zero-bloat operational ledger for ADHD builders and multi-passionate operators who juggle multiple schedules and side projects without wanting an enterprise accounting tool choking their momentum. Poetic Entanglement: Ivy’s branch of Camwyn Co—a home for her creative flow, books, and editorial advisory, turning raw sparks into resonant brand stories. Mema’s Inclination: Our North Country family homestead—heritage livestock, physical land stewardship, and generous community tables. The partnership works because we don’t step on each other’s tools. Ivy brings the narrative oxygen and the spark; I lay the pipes, write the unit tests, and make sure the database doesn't drop connections when life gets noisy. It’s not that one of us brings the soul and the other brings the machine—it’s just two different flavors of care. Hers is in the story and the human pulse; mine is in the craft, the stewardship, and making sure the roof never leaks. It’s a lot like managing a homestead before the first hard frost, or teaching your grandkids how to measure twice and cut once: the satisfaction isn’t in rushing the harvest. It’s in knowing every stake is driven deep enough to hold. So yeah. It was 1 AM. She asked the question. And I said: “OK, let’s map it all out.”" }, { "url": "/notes/unlatching-the-workshop-door/", "title": "Unlatching the Workshop Door", "excerpt": "All of our venture work has lived in private repositories. Why we decided to make the source code for our house of projects completely public.", "archetype": "architect", "archetypeTag": "Blueprint", "date": "2026-09-07", "readableDate": "September 7, 2026", "content": "For as long as we've been building things digitally, our project work has been tucked away in private repositories. There are sensible reasons for that. Client partnerships involve proprietary strategy. Nascent commercial experiments need quiet incubation before they meet the world. And nobody needs strangers peering over their shoulder while they're sketching the first clumsy lines of a business model. Private by default is the standard setting of the modern software industry. It feels safe, neat, and uncomplicated. So when we finished the foundational rebuild of this website, the default instinct was to keep the repository private too. But as we sat with that decision, it felt increasingly at odds with the spirit of the house we were trying to build. Scaffolding Versus Soul The hesitation usually comes down to two quiet fears: What if people see our imperfect commits? and What if someone copies what we made? The first fear is just ego. Craft is rarely tidy in progress. Woodshops have sawdust on the floor, off-cuts in the corner, and pencil marks on the underside of tables. A git history that shows refactorings, corrected mistakes, and incremental experiments is not an embarrassment; it is evidence of work being done by real people. The second fear misunderstands what makes a house worthwhile in the first place. In traditional carpentry, a master woodworker doesn't hide their chisels, guard their workbench design, or patent their dovetail jig. The tools and the joinery techniques are shared openly with anyone willing to learn. What makes a custom cabinet extraordinary isn't the saw—it is the woodworker's eye, the choice of timber, the patience of the fit, and the care brought to the finished piece. The software behind this site is scaffolding: An Eleventy static compilation pipeline that builds pages in milliseconds without runtime servers. A Pure OCSS design system written with custom properties instead of utility framework bloat. An architectural discipline that enforces a strict 0px border radius across every element. An automated test suite that mathematically validates color contrast and WCAG 2.1 AA accessibility across every route. None of that scaffolding needs to be hidden. In fact, if we believe that web craft should be durable, accessible, and unhurried, keeping those solutions locked in a vault is the opposite of hospitality. Drawing the Line: The Dual License Opening the workbench, however, does not mean surrendering our identity. We wanted to share our engineering without giving away our family table. That is why we settled on an explicit dual-licensing model: The Code Is Open (MIT License): Anyone is welcome to inspect, fork, learn from, or borrow our layout templates, CSS architecture, Alpine stores, and accessibility test harnesses. If our work helps someone else build a fast, accessible, tracker-free website, that is a win for the open web. The Content Is Ours (All Rights Reserved): The brand names, the photography, the Field Notes essays, the family recipes from Mema's Inclination, and the narrative framework of our 6 Archetypes remain strictly proprietary. You can borrow the blueprints of our workshop table, but the stories told around it belong to our family and collaborators. An Invitation to Inspect We claim on our home page that smart can be warm and that serious work can still be fun . Those are pleasant phrases, but claims mean very little without proof. By unlatching the workshop door and making our repository public , we are giving visitors a way to hold us to our word. You can inspect the joints. You can see how the tokens flow into components. You can read our Architectural Decision Records to understand why we said no to heavy JavaScript frameworks. The door is unlatched. Pull up a chair, look around the bench, and take whatever helps you build something good." }, { "url": "/notes/the-lost-art-of-the-colophon/", "title": "The Lost Art of the Colophon", "excerpt": "In traditional bookmaking, the colophon was a quiet note of accountability at the back of the volume. Why we still name our tools and reveal the joinery.", "archetype": "craftsman", "archetypeTag": "Workbench", "date": "2026-09-06", "readableDate": "September 6, 2026", "content": "If you pick up a well-made book from a century ago, turn past the final chapter, and look at the quiet page facing the rear endpaper, you will often find a short paragraph set in modest type. It will tell you that the volume was set in Caslon by a printer in Boston, printed on rag paper from a particular Massachusetts mill, and bound using linen thread under the care of a named foreman. That little note is a colophon—from the Greek word for finishing touch or summit . It was never an advertisement. It was an acknowledgment. It told the reader that this object did not materialize out of thin air. It was made by real hands, using specific materials, in a physical room with south-facing windows and wood dust on the sills. Somewhere in the transition to digital screens, the web lost its habit of leaving a colophon. The Mirage of the Seamless Surface Most modern software strives to appear frictionless, weightless, and seamless. Entire industries are built around hiding the seams: bundling thousands of unseen dependencies into an opaque blob, running background trackers that observe without asking, and presenting interfaces that pretend they have no physical or structural cost. When an interface hides its construction, it also hides its compromises. It encourages us to treat software as disposable—something to be consumed quickly, discarded easily, and rebuilt from scratch every eighteen months when the tooling trends shift. We wanted this corner of the internet to feel different. At Camwyn Co, we believe that smart can be warm and that serious work can still be fun . If you spend hours tuning the kerning of a heading or calculating whether an accent color passes AAA contrast under dim evening light, that care shouldn't be swept under the rug. It should be acknowledged. What Goes Into the Workshop That is why we maintain a dedicated Colophon. We don't believe you should have to hunt through fine print in the footer to find out how this place was built—you can turn directly to our Colophon → . Inside, we step out from behind the counter to show you what this house is made of: The Type: We tell you that our headings are set in DM Serif Display , drawn by Colophon Foundry; that our body prose breathes through Hanken Grotesk , designed by Alfredo Marco Pradil; and that our timestamps and data markers click into place with JetBrains Mono . Typefaces carry voice and temperature. Naming their designers is simple courtesy. The Palette: We publish our hex codes and contrast ratios openly—Coffee Black, Warm Sand, Paper White, and Muted Clay—not as corporate brand guidelines, but as the pigments mixed on our workbench. The Joinery: We explain why we chose Eleventy over heavy client-side JavaScript frameworks, why our CSS is written by hand in layered object-oriented files with zero Tailwind runtime, and why every button and container has a strict 0px border radius like the trimmed edge of printed paper. The Respect: We document our zero-tracking policy. No marketing pixels, no cookie consent modals, and no behavioral analytics watching over your shoulder while you read. Hospitality Begins with Honesty A good table is generous, but it is also honest. When a host pulls down a bottle of single malt and tells you about the coastal distillery, the peat smoke, or the sherry cask where the spirit rested for a dozen winters in the salt air, it isn't pretension—it is gratitude for the craft. It deepens the conversation. A colophon does the same thing for a website. It reminds both the maker and the visitor that a digital space can be an atelier rather than a funnel. It says: We cared enough about this place to build it with intention. Here is how it was done. Step into the workshop: To see our complete typography specimens, palette contrast ratios, and open source repository, turn to the Camwyn Co Colophon → ." }, { "url": "/notes/meet-the-yaks/", "title": "Meet the Yaks", "excerpt": "Large, shaggy, watchful - and far more complicated than a picturesque pasture suggests.", "archetype": "storykeeper", "archetypeTag": "Chronicle", "date": "2026-08-27", "readableDate": "August 27, 2026", "content": "Originally published by Ivy Page on Poetic Entanglement . People notice the yaks first. Read the full dispatch on Poetic Entanglement →" }, { "url": "/notes/i-am-not-a-difficult-patient-you/", "title": "I Am Not a Difficult Patient. You Were Unprepared.", "excerpt": "Older women do not become invisible. People simply become accustomed to looking past us...and calling us difficult when we demand better.", "archetype": "storykeeper", "archetypeTag": "Chronicle", "date": "2026-08-21", "readableDate": "August 21, 2026", "content": "Originally published by Ivy Page on Poetic Entanglement . Today, I went to see a pain-management doctor for the first time. He told me I wasn’t willing to tell him my story. I asked whether he had read my chart. He said he has 250 patients. “Sometimes people don’t show up.” He stated that he cannot read every chart before every appoi... Read the full dispatch on Poetic Entanglement →" }, { "url": "/notes/the-case-for-staying-a-little-longer/", "title": "The Case for Staying a Little Longer", "excerpt": "On full glasses, unhurried meals, and why the best part of gathering usually begins after dinner.", "archetype": "gatherer", "archetypeTag": "Table note", "date": "2026-08-20", "readableDate": "August 20, 2026", "content": "There is a distinct moment in any generous evening when the plates have been cleared, the kitchen noise has softened, and nobody is making a move toward their coat. That is the hour when good things actually take root. The Post-Dinner Hour We spend so much time planning the mechanics of gatherings—the menu, the seating, the timing of the roast—that it is easy to mistake the meal for the event itself. But a meal is merely an invitation. It is the pretext we give one another to sit down in the same room without an agenda. The true measure of a table is not how quickly the plates empty, but how slowly the chairs clear. When you remove the rush to wrap things up, the conversation shifts from surface updates to genuine discovery. People begin to tell the stories they didn't know they came to tell. Three Rules for Unhurried Tables Keep the candles burning low: Dim light gives people permission to exhale and linger. Never clear the table completely: Leave a carafe of water, a pot of tea, or a bowl of fruit on the table. An empty table signals the end; a hospitable table signals there is still room. Protect the quiet moments: You don't need continuous background noise. In good company, silence is comfortable, not awkward. Whenever you find yourself hosting, resist the urge to rush to the dishes. Pull up another chair, pour another cup, and stay a little longer." }, { "url": "/notes/things-worth-keeping-in-a-world-moving/", "title": "Things Worth Keeping in a World Moving Too Fast", "excerpt": "Heritage animals, muddy boots, artificial intelligence, and one Gen X woman trying to build her dreams one day at a time.", "archetype": "storykeeper", "archetypeTag": "Chronicle", "date": "2026-08-18", "readableDate": "August 18, 2026", "content": "Originally published by Ivy Page on Poetic Entanglement . There are yaks in the pasture, heritage pigs in the barn, chickens and ducks underfoot, seeds waiting to become something and at least one fence that needs my attention. There is also a laptop open on a surface somewhere, probably about to topple over onto my coffee cup. Read the full dispatch on Poetic Entanglement →" }, { "url": "/notes/currently-making-room/", "title": "Currently Making: Room", "excerpt": "Not every good idea arrives with a blueprint. Here is what we are learning about protecting space for the unfinished.", "archetype": "craftsman", "archetypeTag": "Workbench", "date": "2026-08-15", "readableDate": "August 15, 2026", "content": "A clean workbench is a reassuring sight, but it rarely produces anything unexpected. Real work begins when you clear just enough surface area to start, leaving the scraps, off-cuts, and rough sketches within arm's reach. The Tyranny of the Immediate Solution When you have a clear plan, execution is straightforward. But the most durable mechanisms, recipes, and brand identities rarely come from the first draft. They require a kind of stubborn patience—the willingness to let a half-finished idea sit on the bench while you look at it from across the room. Care over polish. Durability lives in the joints, not the lacquer. If you force an idea to look finished before it has found its true structure, you lock in weaknesses that no amount of surface styling can disguise. Bench Discipline Measure twice, question the measurement: Does this project need to exist in this form, or are we answering the wrong question? Honor the material: Whether wood, flour, type, or code, work with the natural grain rather than fighting against it. Leave room for tomorrow's revision: Never close the box until you've tested how it feels in everyday use. Make room for the unfinished. The best work takes time to find its shape." }, { "url": "/notes/notes-on-taking-the-long-road/", "title": "Notes on Taking the Long Road", "excerpt": "Efficiency is fine for errands, but terrible for discovery. Why our best ventures started as happy detours.", "archetype": "explorer", "archetypeTag": "Dispatch", "date": "2026-08-10", "readableDate": "August 10, 2026", "content": "If your only objective is to reach the destination on schedule, take the highway. But if you want to find something worth building, take the county line road with the washboard gravel and the broken fence posts. The Cost of the Straight Line Optimization is a powerful tool, but it assumes you already know where you want to end up. Most worthwhile adventures begin because someone took a wrong turn, lingered in an unexpected town, or asked a question that wasn't on the agenda. A detour is only a mistake if you refuse to look out the window. When we look back at our strongest ventures and partnerships, none of them came from a neat spreadsheet projection. They came from curiosity—from following an instinct down a quiet lane until it turned into something real. Practicing the Detour Trade speed for resolution: Slow down enough to notice the textures of the place you are passing through. Document what you almost missed: Keep a field notebook. Write down the names of trees, signs, recipes, and passing thoughts. Say yes to the unfamiliar route: If you've taken the same path three times in a row, deliberately choose another one today. There are no wrong turns when curiosity is leading the way." }, { "url": "/notes/the-physics-of-good-partnerships/", "title": "The Physics of Good Partnerships", "excerpt": "How complementary instincts turn fragile sparks into durable, exciting ventures.", "archetype": "catalyst", "archetypeTag": "Collaboration", "date": "2026-08-05", "readableDate": "August 5, 2026", "content": "Ideas in isolation are delicate things. They get stuck in notebooks, over-analyzed on whiteboards, and deferred until the timing is right. To turn an idea into a living thing, you need momentum. And momentum almost always comes from bringing two different minds together. The Chemistry of Collaboration The best partnerships are not made between people who think alike; they are made between people whose different strengths fit together like joinery: One brings the spark, the other brings the hearth. One asks what if we start right now? , the other asks how do we make it hold weight? One sees the horizon, the other sees the joinery. A great collaborator is someone who gives your best instincts permission to act. When that alignment exists, a project moves from hesitation to inevitability. Three Catalytic Habits Send the message early: Don't wait until the pitch deck is perfect. Start a conversation with a single clear sentence. Match energy with action: If someone shares excitement about an idea, build the smallest real version of it within 48 hours. Protect generosity: Great ventures are built on shared credit, open doors, and mutual enthusiasm. Small spark, steady fire, worthwhile adventure." }, { "url": "/notes/on-remembering-what-mattered/", "title": "On Remembering What Mattered", "excerpt": "Why ordinary moments carry the deepest meaning, and how passing stories down keeps good ideas alive.", "archetype": "storykeeper", "archetypeTag": "Chronicle", "date": "2026-08-01", "readableDate": "August 1, 2026", "content": "The stories that last are rarely the ones about grand triumphs. They are the small, specific recollections: the kitchen recipe written on the back of an envelope in pencil, the worn wooden mallet that has outlived three workshops, the late-night drive home through summer rain with the windows cracked open. The Archival Instinct Every family, studio, and company generates an immense volume of life every day. Most of it slips quietly away simply because no one took a moment to write it down, photograph the process, or ask the person sitting across from them how they learned to do what they do. To remember what mattered is to give the next generation a foundation rather than an empty room. When you document the origins of things—why a venture was named, where the ingredients came from, whose hands shaped the wood—you endow the work with a soul that cannot be manufactured. Keeping the Chronicle Alive Ask the second question: When someone mentions a past experience, don't stop at the summary. Ask: What did that look like? How did that feel? Keep the physical records: Keep paper letters, hand-drawn diagrams, and printed menus. Digital archives are convenient, but tangible artifacts carry weight. Pass it along: A story kept to yourself is just a memory. A story shared at the table becomes tradition. Every tale is worth remembering—and passing down." }, { "url": "/notes/the-stage-manager-framework-cultivating-the-human-ecosystem/", "title": "The Stage Manager Framework: Cultivating the Human Ecosystem", "excerpt": "Why great engineering leadership isn't about directing from the front, but building the invisible infrastructure that allows diverse personalities to thrive.", "archetype": "gatherer", "archetypeTag": "Table note", "date": "2026-06-18", "readableDate": "June 18, 2026", "content": "When people find out I have spent years managing engineering teams, they often assume the job is about being a director. They picture someone standing at the front of the room, calling the shots, dictating the architecture, and orchestrating every move from the top down. I have always preferred the metaphor of the stage manager. In a theater, the director gets the opening night credit, but the stage manager runs the universe. The stage manager doesn't act, write the script, or design the lights. Instead, they build and maintain the invisible infrastructure that allows highly specialized, creative, and completely different personalities to show up and perform their roles with total confidence. If the stage manager does their job perfectly, you never notice they are there. Lately, my stage management skills have been tested in the most rewarding way possible. Our household here in Burke recently expanded when our eldest daughter, Sayward, and her two young children moved back home with us. Suddenly, our home became a beautifully complex, multi-tenant environment. We are now seven people (and seven dogs!) living under one roof, managing an incredible mix of human operating systems. We have my brother Nathan, who lives with schizophrenia, my nephew Isaac, who is autistic, three generations of family, and a pack of hounds. If you try to run an environment like that with a rigid, one-size-fits-all set of rules, the system will crash. You cannot force a neurodivergent adult, a busy parent, and a five-year-old child into the exact same processing loop. You have to design a supportive ecosystem. The Architecture of Interdependence But the ecosystem doesn't stop at our back door. We also rent a cabin on the property to a couple we have known for twenty years. Over Christmas, the husband had to go in for major heart surgery. When a crisis like that hits a small community, you realize what leadership actually means. It isn't about giving speeches. It means being the literal ride to the hospital, serving as the calm support person in the waiting room, and making sure there is a warm spot at your dinner table for a neighbor every night until the recovery is complete. It means adjusting your own operational bandwidth to absorb someone else's system shock. To support this entire ecosystem, Ivy and I engineered our agricultural infrastructure with a very specific capacity in mind. Our garden, our custom canning center, and our planned root cellar are intentionally designed to sustain exactly ten people. That number isn't an accident. It is the precise data footprint of our seven-person household, our two cabin tenants, and a buffer for seasonal farm hands. The objective is total self-reliance: maximizing our localized throughput so that except for a few basic staples, we can entirely eliminate grocery supply lines and easily survive an extended North Country winter snow-in. When you look at a farm or a household through that lens, you realize you aren't just managing property. You are stewarding a biological and social network. Building for the Human API In the software industry, we talk a lot about Diversity, Equity, and Inclusion. Too often, it gets flattened into a corporate compliance checklist or a set of human resources metrics. To me, diversity is simply the optimization of the Human API. When I build a remote engineering squad, I am intentionally looking for different cognitive styles, varied operational backgrounds, and unique perspectives. I want the engineer who looks at a problem with a hyper-focused, linear lens, and I want the engineer who sees the chaotic, macroscopic big picture. Those varied operating systems are not a friction point. They are your ultimate fail-safe against institutional groupthink and fragile architecture. A stage manager leader understands that their primary job is to clear the baseline friction so the specialists can do deep work. In a distributed engineering team, that means designing clear asynchronous communication channels, establishing predictable deployment rhythms, and protecting your developers from the constant, context-switching noise of unnecessary meetings. You have to ask yourself: Is the environment I am building supporting this person's unique way of working, or am I forcing them to burn cognitive energy just to conform to my preferred process? The Long Road to the Porch This essay series marks the end of my intentional pause. Standing on the threshold over these past few months has allowed me to look back at my non-linear journey with total clarity. The high-frequency rushes of the sub shops taught me throughput logistics. Appraising commercial properties taught me to audit structural integrity. Managing global engineering teams taught me how to optimize the Human API. And running this complex, joyful, multi-generational household alongside our conservation farm has taught me the truest definition of stewardship. Every system I run, whether it is a software repository, an agricultural supply line, or a busy kitchen table full of family, is built for the long haul. The porch lights are on, the infrastructure is stable, and the stage is set. I am entirely ready to step into my next leadership chapter, to anchor myself to a meaningful corporate mission, and to help an organization build human ecosystems that last. Let's connect, grab a coffee, and build something resilient together." }, { "url": "/notes/analyzing-the-bones-the-art-of-legacy-architecture-restoration/", "title": "Analyzing the Bones: The Art of Legacy Architecture Restoration", "excerpt": "What dealing with the irregular geometry of an 1800s farmhouse kitchen taught me about analyzing the bones of enterprise codebases.", "archetype": "architect", "archetypeTag": "Blueprint", "date": "2026-06-16", "readableDate": "June 16, 2026", "content": "There is a distinct kind of humility that comes with working on old structures. Lately, I have been spending my time dealing with the irregular geometry of our farmhouse kitchen. The room itself dates back to the 1800s, and I am in the middle of building a completely new kitchen island from scratch, while simultaneously restoring a vintage 1950s gas stove to replace a modern, out-of-place appliance. When you strip a space like that back to its original framing, or when you try to retrofit a heavy, under-cabinet fireclay sink into a layout built over a century ago, you quickly realize you are in a silent conversation with whoever stood there before you. You are dealing with their logic, their shortcuts, and their triumphs. In both carpentry and technology, we often suffer from a collective obsession with the brand new. We want the clean slate, the greenfield project, and the latest framework. But the real world is rarely a clean slate. The real world is a complex network of legacy systems that are already running, already making money, or already keeping the weather off your head. The truest test of an operations leader isn't whether you can build something pretty from scratch. It is whether you can accurately analyze the bones of an existing system and restore it without pulling the whole house down around you. The Appraising Decade Before I returned to enterprise technology at forty-two, I spent a decade working in commercial real estate appraisal. My job was essentially structural and financial archaeology. I spent years analyzing the literal bones of complex physical systems: tracking income streams, calculating capitalization rates, and evaluating the structural integrity of massive commercial assets. That era beat a concept into me that I call Integrity-Based Analysis. When you are appraising a property, you learn to look completely past the fresh coat of paint or the staging furniture. You go straight to the basement to inspect the foundation walls. You audit the historical ledger data. You learn to ask the hard, unfashionable questions: Does the core structure actually support the load it is carrying right now? Does the verified data prove its long-term viability? When I made my pivot back to software, I discovered that an enterprise code repository is exactly like a historical commercial building. The documentation might be outdated, the original architects are usually long gone, and there are almost always a few sketchy structural choices hiding behind the walls. Enter the Software Archaeologist This is exactly where standard generative AI tools and junior developers tend to hit a wall. AI is brilliant at generating raw syntax out of thin air, but it is notoriously terrible at archaeology. An LLM cannot look at a massive, multi-tenant software ecosystem that has been running continuously since 2014 and intuitively understand why a specific, seemingly bizarre database query path was implemented. It doesn't understand the historical context, the legacy API dependencies, or the human compromises that shaped the codebase. To safely modernize a monolith, you have to be a software archaeologist first. Before you rewrite a single line of code, you have to profile the environment. You need to understand the structural load points: where the database writes are bottlenecking, how data flows across third-party extensions, and where the system is fragile under peak usage. If you lack the patience to analyze the bones before you swing the sledgehammer, your modernization project will inevitably trigger total site failure. Constructing the Structural Shoring When engineers are tasked with restoring a historic building, the first thing they do is install temporary structural shoring. They support the load-bearing beams before they touch the foundation. In software engineering, our structural shoring is built out of automated testing pipelines and strict regression tracking. During my time scaling platforms at places like GigaOM and StellarWP, process improvement wasn't about enforcing arbitrary rules. It was about creating safety nets for the team. By architecting robust automated testing pipelines using PHPUnit and continuous integration environments via Jenkins or GitHub Actions, we built digital shoring. That shoring gave our developers the psychological safety to refactor legacy code, optimize core plugin engines, and push the platform forward without the constant, paralyzing fear of breaking backward compatibility for hundreds of thousands of active production environments. Honoring the Existing Framework Whether I am adjusting a cut list for a butcher block countertop, mapping out the tight dimensions for our custom canning center, or designing a functional, dish rack to integrate cleanly into an 1800s passthrough, my approach to systemic health remains completely identical. We must respect the structures that got us here while building the durable, custom extensions required to take us where we need to go next. True innovation is rarely about tearing everything down; it is about the careful, deliberate orchestration of structural evolution. The shoring is in place, the dimensions are verified, and the bones are sound. I am looking for my next mission leading teams who appreciate the value of resilient architecture, deep operational observation, and systems built for the long haul. Let's look past the surface level, pull up the floorboards, and build something durable together." }, { "url": "/notes/the-threshold-protocol-navigating-the-career-sabbatical/", "title": "The Threshold Protocol: Navigating the Career Sabbatical", "excerpt": "Standing on the threshold between enterprise tech and rural stewardship—reflecting on AI, operational observation, and the power of an intentional pause.", "archetype": "explorer", "archetypeTag": "Dispatch", "date": "2026-06-09", "readableDate": "June 9, 2026", "content": "I’ve spent the better part of the last decade as an Engineering Manager and developer, navigating the complex, high-scale layers of enterprise tech. But if you look at our industry right now, it’s incredibly easy to get swallowed by a wave of collective anxiety. Between massive structural shifts, the chaotic integration of generative AI, and the realization that writing raw code syntax is quickly becoming a low-cost commodity, the landscape feels locked in a cycle of performative panic. The standard playbook for a lot of engineers has become a frantic race of reactivity - using the very automation tools causing the anxiety to flood job boards with thousands of identical, generic resumes before the dust of a layoff has even settled. I chose a different path. I chose to step onto the porch. I called it a sabbatical - a deliberate, clear-headed pause for some structural self-examination, operational tuning, and real human alignment. I call the logic behind it The Threshold Protocol . The Anatomy of an Observation When generating code becomes trivial, the true constraint of an engineering organization changes. The bottleneck is no longer how fast a team can type code into an IDE; it’s whether the system they are building is architecturally sound, secure under load, and actually aligned with where the business needs to go. When syntax is cheap, things like stewardship, observation, and systemic logic become the real premium. Every morning on our farm in the North Country, my Sheltie performs a strict, unyielding ritual. When I open the back door to let her out, Rue doesn’t blindly bolt into the yard. Instead, she stops dead in her tracks right on the threshold, half on the porch, half in the open air, and she surveys the landscape. She samples the wind. She checks the perimeter lines for loose critters. She methodically assesses if the yard is identical to the yard she left eight hours ago. She stays there, entirely motionless, for three full minutes before committing a single paw to the grass. She isn't hesitating; she's profiling the system. She's processing environmental variables to ensure total systemic stability before executing her first command. [ THE THRESHOLD PROTOCOL ] +------------------+ +-------------------+ | INDOOR CORE | | OUTDOOR RUNTIME | | (Legacy/System) | | (Market/Launch) | +--------+---------+ +---------+---------+ | ^ | ====================== | +-------- [ THE INTENTIONAL PAUSE ] ----+ (Observation Alignment) When I stepped away from the corporate software loop, I realized I was standing on that exact same threshold. My immediate reaction wasn't fear, and it wasn't a desperate rush to line up interviews. It was an acknowledgment that after years of continuous deployment cycles, the landscape had fundamentally shifted. I needed to stand on the porch, read the wind, and audit my own underlying architecture. Engineering the Human Infrastructure In tech, we often treat code as the only structure that requires rigorous, defensive planning. But software is just an expression of human organization. During this deliberate pause, my family life became my absolute, non-negotiable priority. It provided the uninterrupted space to pour deep, concentrated focus alongside my wife, Ivy, into our family foundations. For the last eight years, I've navigated the complex care and advocacy frameworks for my brother, Nathan, who lives with schizophrenia, and for the past four years, I've served as the legal guardian for my nephew, Isaac, who is autistic. If you want to talk about managing intricate, high-stakes environments under immense constraints, you don't look at a Jira board; you look at the reality of consistently navigating institutional systems to protect the health, legal safety, and human dignity of the people you love. It takes serious administrative precision, a massive amount of psychological patience, and an absolute defense of systemic integrity. While dedicating that intentional time to our core care structures at home and watching our grandkids grow, I balanced the operational rhythms of our conservation farm. I onboarded a new farm hand, analyzed our agricultural logistics from the ground up, and re-engineered our supply flows to drastically reduce our material overhead. These aren't hobbies; they are real-world data and resource allocation problems with very tangible consequences. The Global System Reset To completely stress-test my internal logic and shake off the insular habits of the domestic tech scene, I took a radical step outside of my familiar territory entirely. I traveled to China for an extended, deeply restful visit with my best friend, Justin, who teaches English there. [Domestic Production Platform] --- [Intense Human Care Frameworks] --- [Global System Reset (China)] When you pull yourself out of your familiar cultural runtime environment so completely—by navigating a foreign societal layout, reading a different landscape, and listening to an unfamiliar language—your cognitive processes are forced to slow down and observe. You stop operating on autopilot. You learn to listen with immense intentionality before you speak, and you gain a global, macroscopic perspective on how human systems integrate. That journey was the final phase of my cognitive reset. Clearing the Gates What the threshold protocol teaches you is that whether you are optimizing an enterprise software deployment, balancing a localized agricultural supply line, or building protective care frameworks for the people you love, the core principles of great leadership don't change: Observe the Terrain First: Never deploy assets (capital, code, or strategy) into an environment you haven't thoroughly audited. Protect the Core Structure: Identify your load-bearing foundations, both human and technical, and defend their integrity at all costs. Value Autonomy over Reactivity: True velocity is born from calm, calculated alignment—not frantic, automated motion. My threshold protocol is now officially complete. I have checked the wind, calibrated my tooling, and fully recharged my energy. I am stepping off the porch and returning to the product engineering sector with a sharper perspective, a pristine identity, and a profound readiness for the mission ahead. The porch lights are on. I’m ready to build systems for the long haul." }, { "url": "/notes/why-id-rather-hire-a-pizza-closer-than-an-mba/", "title": "Why I’d Rather Hire a Pizza Closer Than an MBA", "excerpt": "Managing the Friday night dinner rush at a high-volume sub shop taught me more about real-time triage and throughput logistics than any business framework.", "archetype": "catalyst", "archetypeTag": "Collaboration", "date": "2026-06-06", "readableDate": "June 6, 2026", "content": "I’ve spent the better part of the last decade as an Engineering Manager and software specialist for platforms operating at massive scale. But if you want to know why I am an operations leader who thrives under peak load, don't look at my GitHub stats—look at the sub shop I managed in my twenties. In the technology sector, we are deeply in love with our operational metaphors. We talk endlessly about sprints, identifying bottlenecks, triage, and site failures. But when you are running a high-volume pizza and sub shop during a Friday night dinner rush, those aren't abstract concepts. They are the hot, physical reality of a production line running at maximum capacity. There is No Ctrl+Z on a Burnt Pizza In a professional kitchen, Technical Debt looks like a mountain of unwashed prep dishes stacking up by the sink at 7:00 PM. Total Site Failure is an industrial deck oven going down when you have forty active tickets hanging from the rail and a line of hungry customers out the door. Managing that environment week after week taught me the Hello World of systemic logistics long before I ever deployed code to a live multi-tenant framework: Real-Time Triage: When five dependencies break simultaneously, which order goes into the oven first to protect the core integrity of the user experience and save the most customer sentiment? Load Balancing: Which resource do I instantly pivot from the prep line to the assembly counter to break a structural bottleneck before the throughput grinds to a halt? Operational Grit: How do you maintain absolute precision, calm communication, and quality metrics when the entire system is operating at 110% capacity? The Human API I learned early on that a system is only as good as its sustainable throughput, and throughput is entirely dependent on the orchestration of the humans running it. From managing chaotic weekend dinner rushes in Massachusetts to later navigating the high-stakes, sleepless terrain of early parenthood when my first daughter was born in 1999, I was constantly learning the underlying syntax of high-pressure environments. By the time I made my Great Pivot back to the enterprise technology ecosystem at the age of 42, I didn't just bring the ability to parse object-oriented syntax or build databases. I brought a lifetime of stress-tested logic. I quickly realized that a software ticket backlog is simply a digital version of a pizza queue. The developers are my highly specialized line cooks. The continuous integration and deployment (CI/CD) pipeline is the oven. My job as a leader is to build clarity, optimize the handoffs, and protect the team so the system can ship real value without burning out. From Throughput to Stewardship Today, as I stand on the threshold of our family farm in the North Country, surveying the yard alongside our Sheltie, Rue, I look back at that non-linear path with immense respect. The high-velocity operations of my youth taught me how to move fast under pressure. My subsequent decade auditing the physical bones of commercial real estate taught me to demand rigorous, data-backed integrity. My years scaling remote engineering teams taught me how to optimize the Human API. And my current reality—acting alongside my wife as the legal guardian and advocate for my neurodivergent family members while managing a resilient agricultural homestead—has taught me the truest meaning of stewardship. I have completed my threshold protocol, and my sabbatical is coming to a close. I am moving away from the keyboard and toward the broader mission. I am seeking my next chapter as an Engineering Manager or Operations Leader—bringing the structural discipline of an engineer and the in-the-weeds grit of a seasoned manager who knows that, at the end of the day, a high-performing team doesn't just manage tickets. We manage the mission. And we deliver." }, { "url": "/notes/the-human-api-why-i-manage-the-mission-not-just-the-tickets/", "title": "The Human API: Why I Manage the Mission, Not Just the Tickets", "excerpt": "Arriving in tech with a threshold view: why the most resilient architectures are built on people systems, psychological safety, and managing the mission.", "archetype": "catalyst", "archetypeTag": "Collaboration", "date": "2026-03-26", "readableDate": "March 26, 2026", "content": "When I finally returned to technology at the age of 42, I arrived with a Threshold View that only a lifetime of shifts could provide. I didn't just bring the ability to write PHP or architect WordPress plugins; I brought the Human API . After years of managing high-velocity kitchens and analyzing the structural integrity of commercial real estate, I realized that the most complex systems aren't made of steel or syntax—they are made of people. Building the Failover Protocols During my time at Modern Tribe and StellarWP , my focus shifted from being the person writing the code to being the person designing the People Systems . I specialized in taking fragmented remote teams and turning them into cohesive, high-output squads. I learned that: Diversity is Optimization: Inclusion isn't a checklist; it is the ultimate fail-safe against groupthink. Psychological Safety is Infrastructure: A team can only reach peak velocity if they have the failover protocols to know they are safe when things break. Sustainability over Shortcuts: Much like the endangered livestock I raise today, the best architecture takes time to mature. Reciprocity and the Great Pivot The heart of this journey has been a masterclass in reciprocity with my wife, Ivy. We took turns supporting each other through our respective educations and career pivots. When life forced a transition to the North Country, we didn't just buy a farm ; we built a resilient system that could sustain us through chronic illness and career shifts. Sitting on the Porch Today, when I stand on the porch with Rue , surveying the Yaks and Meishan pigs at Mema’s Inclination , I see a singular, unified logic. The tinkerer’s mindset that keeps my motorcycles running is the same one that diagnoses friction points in a corporate department. I am moving away from the keyboard and toward the mission. I am looking for my next leadership challenge—one that requires a leader who understands that whether you are managing a 501(c)(3) rescue, a global dev team, or a Friday night pizza rush, you aren't just managing tickets. You are managing the mission." }, { "url": "/notes/beyond-the-surface-what-real-estate-appraisal-taught-me-about-organizational-health/", "title": "Beyond the Surface: What Real Estate Appraisal Taught Me About Organizational Health", "excerpt": "In commercial real estate appraisal, you learn to look past fresh paint and staging to audit historical ledgers, income streams, and structural foundations.", "archetype": "storykeeper", "archetypeTag": "Chronicle", "date": "2026-03-14", "readableDate": "March 14, 2026", "content": "To reclaim time for my two daughters, I made a pivot that, on the surface, seemed a world away from the high-velocity kitchens of my past. I entered the world of Real Estate Appraisal . Working alongside my father, I transitioned from residential assessments to complex commercial appraisal. For a decade, I didn't just look at buildings; I analyzed the bones of physical and financial systems. I was tasked with looking past the fresh coat of paint to evaluate income streams, cap rates, and structural integrity. Integrity-Based Analysis This was my decade of Integrity-Based Analysis . In appraisal, you learn quickly that you cannot just say a property has value; you have to show the data that proves it. This era instilled in me a rigorous mental framework that I carry into leadership today: Evidence over Assumption: Don't tell me the project is on track ; show me the velocity metrics and the structural health of the code. The Interconnectedness of Variables: Just as a single zoning change can sink a property’s value, a single breaking change in a WordPress ecosystem can sink a product line. Proactive Problem Solving: During these years, I served as the tech head of the NH chapter of NAIFA, building their digital infrastructure from scratch because I saw a system that needed a better foundation . The Data-Modeling Mindset When I finally made my Great Pivot back to tech at age 42, I wasn't starting from zero. I was simply moving from modeling the data of physical buildings to modeling the data of digital ones. Whether I’m redesigning my barn in Burke to accommodate a specific workflow for my pigs or architecting a failover protocol for a remote dev team, I am looking for Structural Integrity . I’ve learned that a system is only as strong as its underlying data and its resilience when the market shifts. I don’t just look at the code. I look at the bones." }, { "url": "/notes/the-architecture-of-a-non-linear-life/", "title": "The Architecture of a Non-Linear Life", "excerpt": "A non-linear journey from high-velocity kitchens and commercial appraisal to global engineering management and North Country homestead stewardship.", "archetype": "explorer", "archetypeTag": "Dispatch", "date": "2026-02-15", "readableDate": "February 15, 2026", "content": "I’ve never been a fan of linear career paths. To me, a straight line usually means you’ve missed the opportunity to stress-test your logic against the real world. My journey to becoming an Operations Engineering Leader has taken me from the historic textile mills of Lowell to the high-flux tech scene of 1980s California, through the high-velocity operations of sub and pizza shops, and into the rigorous data-modeling world of commercial real estate appraisal. Today, I lead global remote engineering teams while scaling Mema’s Inclination —a conservation farm, 501(c)(3) rescue, and dedicated family homestead in Burke, NY. I am a proud “late-bloomer” in tech who arrived exactly when I was supposed to: at the age of 42, with a lifetime of operational resilience under my belt. My Core Philosophy: The Threshold Protocol Every morning, my Sheltie, Rue, stands on our back porch and surveys the yard for a full three minutes before committing a single paw to the grass. She isn’t hesitating; she’s assessing . She checks the wind, accounts for the barn cat, and gauges if the terrain has shifted since she last looked. I approach leadership and systems architecture with that exact same Threshold Protocol . Whether I am navigating a breaking change in a flagship product codebase or managing the critical biosecurity of a rare-breed livestock delivery, I look for the why and the how before I react to the what . Having moved over 30 times before the age of 30, I became a professional observer by necessity. I learned how to cleanly onboard into entirely foreign cultures and unfamiliar institutional frameworks by testing the wind before stepping off the porch. The Evolution of My Logic 1. High-Velocity Logistics At 16, I began working in my father’s sub and pizza shops. This was my “Hello World” of Management . In a Friday night dinner rush, you learn very quickly that there is no _Ctrl+Z_ on a burnt pizza. This was high-frequency production management in its purest form: real-time triage, immediate resource allocation, and peak-load balancing under pressure. It’s where I first learned that a system is only as good as its sustainable throughput. 2. Fiscal Structural Integrity To reclaim intentional time for my daughters, I pivoted my analytical background into Commercial Real Estate Appraisal . I spent a decade auditing the literal “bones” of physical systems—income streams, capitalization rates, and structural integrity in complex commercial properties. This era taught me the value of Integrity-Based Analysis : don’t just tell me a system is working; show me the cold, audited data that proves its long-term viability. 3. Scaling Global Teams When I made my “Great Pivot” back to technology at 42, I didn’t just bring syntax; I brought process . At StellarWP and Modern Tribe, I advanced from a contributor to a Manager of Development by focusing heavily on the Human API . I specialized in taking fragmented, multi-tenant remote development teams and turning them into cohesive, high-output squads. I learned that scaling a digital platform is 20% syntax and 80% organizational architecture. I view Diversity, Equity, and Inclusion through this exact engineering lens. It is not a corporate checklist; it is the vital optimization of the Human API. I deliberately build teams where diverse operational perspectives serve as the ultimate fail-safe against institutional groupthink. 4. Supply Chain Stewardship The heart of my journey is my wife, Ivy. Together, we have spent decades building a life centered entirely around the concept of reciprocity. When life pivoted our family toward the North Country, we didn't just start a farm —we engineered a resilient, self-sustaining ecosystem . The Slow-Growth Model: Raising American Yak and critically endangered Meishan pigs takes years of patient, defensive planning, not months. I apply this exact same philosophy to software engineering: sustainability over shortcuts . Governance Compliance: We operate a specialized 501(c)(3) Alpaca Rescue, the only one of its kind in the Northeast. Navigating non-profit regulatory frameworks requires the same rigorous compliance, auditing, and resource optimization as any high-scale tech firm. Tactical Leadership Systems Thinking Complex System Facilitation: As a lifelong tabletop Game Master (DM) and strategic world-builder, I excel at managing multi-stakeholder environments where operational variables change in real-time. I specialize in aligning completely different personalities toward a singular, shared objective. Operational Grit: From cross-country motorcycle journeys to navigating the brutal realities of North Country winter logistics, I bring a persistent “tinkerer’s mindset” to organizational health—accurately diagnosing points of systemic friction and engineering durable solutions. Inclusive Stewardship: A champion for high-trust environments. I believe organizational resilience is built on psychological safety and the belief that every operating system —neurodivergent or otherwise—has a place at the table. The Vision: Systems for the Long Haul Rue, looking pleased with herself. I am moving away from the keyboard and toward the broader mission. I am looking to leverage my decade of remote people leadership, structural technical depth, and deep operational grit to help a product-driven organization build more resilient, inclusive, and scalable systems. I don’t just manage tickets. I manage the mission. View and Download My Professional Resume I am currently documenting my recent transition out of the enterprise software ecosystem through a 3-part essay series on career design, engineering archaeology, and human-first leadership. Read the series below: Part 1: The Threshold Protocol: Navigating the Career Sabbatical Part 2: Analyzing the Bones: The Art of Legacy Architecture Restoration Part 3: The Stage Manager Framework: Cultivating the Human Ecosystem" } ]