01
Technical and digital systems
I build firmware, mobile and web tools, automation, documentation, and practical systems that people can understand and continue using.
Engineering, inner work, and what I am learning
Schuyler
I build software, embedded systems, and practical systems for organizing and using information. I also spend a lot of my life exploring embodiment, spiritual practice, relationship, and what it means to become more fully myself.
My days move between these things. Sometimes I am tracing a firmware bug or creating a publishing workflow. Sometimes I am listening with another person to what their body is communicating, sitting with uncertainty, or writing about what I am learning.
I am enamored with this journey through life. I love making things that help people feel more capable and less tangled, and I love sharing what I experience when it might help another person become more of who they want to be.
What I care about
What I spend my life doing
Some of this becomes a project, session, collaboration, or piece of writing. Some remains personal practice, curiosity, relationship, or ordinary life.
02
Knowledge and organizational systems
I help people organize information so they can find what matters, understand their work, and move it forward without living inside unnecessary complexity.
03
Embodiment and inner work
I practice body listening, meditation, and spiritual inquiry. I also accompany people who want unhurried attention while they listen to their own experience.
04
Ritual, beauty, and transition
I am drawn to marking beginnings, endings, grief, celebration, and other changes with tea, beauty, conversation, and attention.
Availability
Let’s start with the real conditions
I can do much of my technical and knowledge-system work remotely. Hardware, bodywork, and ritual depend on where I am, what space and equipment are available, and whether travel or shipping makes sense.
Tell me what you have in mind. We can talk through timing, practical constraints, and budget or exchange if the work feels worth exploring.
Things I have built
A few technical things I have built
Usable alpha Public-readable
Termux Dashboard
A phone-friendly way to open the right project and return to an existing terminal workspace with one command.
The repository is public to read, but it does not currently include a license granting reuse rights.
Experimental Open source
Repo Automation Template
A set of terminal-first workflows that make careful GitHub and Codex work easier to repeat from a phone or computer.
Licensed under Apache-2.0. The public helper surface is still stabilizing.
Paused Open source
ESP32 NFC Security System
Offline-first firmware and a local mobile interface for controlling and understanding an NFC-based workshop security system.
Licensed under Apache-2.0. Later milestones are paused before bench testing resumes.
Ways we might work together
Technical, personal, and embodied work
Available by conversation
Listening Hands
A consent-based bodywork practice centered on careful touch, unhurried attention, and listening to what your body is communicating.
Available by conversation
Spiritual Guidance and Embodied Integration
Companionship for turning inward, listening to your body and intuition, and meeting a changing life without handing your authority to someone else.
Available by conversation
Technical Systems and Problem Solving
Engineering, troubleshooting, and practical decision support for a device, workflow, or software system that needs to become clearer and actually work.
Available by conversation
Personal Knowledge and Digital Systems
Practical ways to organize the notes, files, projects, and context your life or work depends on so you can find what matters and use it.
How I work
I begin by understanding what is actually needed
- Listen to the person, the system, and the conditions around the problem.
- Clarify what already exists, what matters most, what is constrained, and what a useful result would look like.
- Make the smallest useful thing that moves the work forward without creating unnecessary complexity.
- Test what can honestly be observed, checked, or verified in the real environment.
- Document the important decisions, instructions, limits, and next steps so the work remains understandable.
- Leave it understandable so the people living with the work can keep using, changing, and caring for it without depending on me.
My current life and work
What I am tending right now
I am continuing to build technical tools, shape a calmer way to write and publish, and bring more of my real life and earlier writing into this public space.
Visit the now pageBringing more of my work into Heartloom
I am gradually moving selected writing, projects, and parts of my earlier public life out of old Notion spaces and into this website. I am doing that carefully so private material stays private and the public pages remain understandable.
A calmer way to write and publish
I am building a private, offline-first writing practice in Obsidian and a careful path for reviewed material to move into this static website. I want publishing to feel more like writing and less like operating a software release every time.
Development from Android
I continue exploring how much careful technical work I can do from an Android device. Termux Dashboard and my repository workflows help me move between real projects without giving up explicit checks, local ownership, or an understandable terminal environment.
A real conversation
Tell me what you have in mind
I read these emails myself. Tell me what you are making, changing, exploring, or trying to repair. It helps to include:
- what already exists and what is not working
- what you want to change or make possible
- the timing and approximate budget or exchange you have in mind
- whether location, travel, shipping, or access to a hardware bench matters
Reaching out does not commit either of us to working together. It simply gives us a place to begin.