Selected technical work

Things I have built

I love taking a messy problem and turning it into something another person can actually use and understand.

This is a small selection of public work. I chose projects that show different parts of how I think, including mobile development, repository systems, embedded firmware, documentation, testing, and the practical decisions that hold all of it together.

Current selection

The problem, what I made, and why it mattered

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 problem: Development from an Android phone loses momentum when reopening the right repository, remembering its state, and rebuilding a terminal workspace takes too many steps.
What I made: I built a Git-aware shell workflow that shows pinned and recent projects, opens the selected repository, and creates or rejoins its tmux workspace. I also added linting and smoke tests for the behavior I depend on.
Why it mattered: Now a short phone session can become useful work instead of setup time. The workflow stays local, visible, and understandable rather than hiding the terminal behind a separate service.

The repository is public to read, but it does not currently include a license granting reuse rights.

View Termux Dashboard

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.

The problem: Branch setup, AI handoffs, CI review, releases, and pull-request finishing are easy to perform inconsistently, especially when I am working from a phone.
What I made: I created a documented library of shell helpers with explicit safety checks, machine-readable metadata, and a shared test harness. The patterns can be carried into other repositories without pretending every project has the same needs.
Why it mattered: These helpers save me from rethinking the same GitHub steps in every project. They keep important decisions visible and make it easier to work carefully from a phone without trusting a black box.

Licensed under Apache-2.0. The public helper surface is still stabilizing.

View Repo Automation Template

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.

The problem: The workshop needed a control system with clear operating states, local interfaces, and useful event records without depending on a cloud service.
What I made: I designed and documented the ESP32 firmware architecture, operating state machine, setup flow, NFC and browser controls, local event logging, and automated compile checks through the implemented milestones.
Why it mattered: The project shows how hardware-facing software can remain understandable and testable. Its core architecture is designed to operate locally, name its states and faults clearly, and perform its essential work without a remote service.

Licensed under Apache-2.0. Later milestones are paused before bench testing resumes.

View the firmware repository

A note about status and reuse

What the labels mean

Open source: The linked repository has a license that grants reuse rights. Read that repository’s license for the actual terms.
Public-readable: You can read the source, but the absence of a license means I am not granting reuse rights.
Usable alpha: The project works for real use, although installation, interfaces, or documentation may still change.
Paused: Meaningful work has been implemented, but later milestones or physical testing are not moving right now.

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.

Email Schuyler GitHub LinkedIn