I’m Paul Gydos. I’m exploring computer science through tools for writing, study, sound, and community life. My projects connect phone-based development, local software, AI-assisted work, and a simple habit: keep the source, the decisions, and the learning visible.
Seven public project repositories, plus this website. Some contain working tools, others document environments or early ideas. Each entry links to the evidence and makes its stage clear. Repository coverage reviewed September 17, 2026.
A corrected meeting flyer became an exercise in requirements, source preservation, editable graphics, automated rendering, and human review. The public record includes original images, an SVG source, PDF and PNG outputs, design decisions, and a reviewed session report.
A public guide to using an Android phone as a development workstation with Termux, tmux, Neovim, Rust, Python, C/C++, and AI coding tools. It makes development under mobile constraints a subject worth documenting and studying.
Stage: environment documentation. The public repository currently contains the setup guide; APK examples and a verified app-build walkthrough remain next steps.
A lean local knowledge pack for becoming sharper with Codex, especially on storage-constrained Android / Termux setups. It collects power-user paths, prompting patterns, config and permissions notes, AGENTS.md / skills guidance, lean-stack habits, tooling pairings, and reusable playbooks.
A platform-neutral Rust command-line application that selects one KJV passage for the current
local calendar day. The order is deterministic by year, while a separate POSIX /bin/sh
implementation keeps the idea close to the vishgit path.
A Windows-first, local-first console instrument for generated meditative/electronic soundscapes, live frequency changes, rhythm and synthesis variation, Piper text-to-speech, pasted readings, and KJV / Meta-V scripture loading. This is a prototype: combined speech-and-music export is incomplete, and the README flags export behavior for further verification.
A local C# application for turning scattered writing into a reverse-chronological HTML reading surface, served on a local network. The documented core reads text, Markdown, and Vim files; Word documents and Google Docs integration remain extensions to develop.
A seed-stage project for a free-of-cost, manifest-driven creative toolchain: music, spoken word, Scripture-aware text workflows, attribution tracking, and local-first experiments. There is not a build to present yet. The repository separates Windows-origin and Android/Termux-origin workspaces, each currently documented with a README.
A small static website connecting the projects, their source, and the lessons behind them. Plain HTML and CSS keep it easy to read, edit, and publish with GitHub Pages.
First Step Beginners flyer · September 2026. A concrete community need brings the whole process into view: understand the problem, preserve the evidence, build an editable solution, check the result, and publish a useful record.
The meeting entrance information had changed. The new flyer needed confirmed directions, readable copy, useful entrance imagery, and a map, all on one US Letter page.
Original images stayed intact. The owner supplied the entrance facts and reviewed successive designs. Editable SVG and a rendering script produced the print PDF and 300-DPI PNG. Named fallback versions preserved accepted work as revisions continued.
Originals · Editable source · Documentation · Decisions · Session reports
Across these projects, I’m practicing several connected parts of computer science: data modeling and deterministic selection in Verse of the Day; document processing in Siftlog; audio and command interfaces in Soundbox; development environments on Android; and reproducible pipelines and human review in the flyer project. Readable source and visible history connect them.
Make each project easier to enter with a concrete example, an accurate status, and a repeatable path from source to result. Smellinux / vishgit remains a future environment concept centered on editing with vim, executing with sh, and remembering with git; it has no standalone public repository yet.
My Chief Technology Officer for my startup gydos-dot-org and myself.
The best public entry point is the GitHub profile and the project repositories. For project-related contact, use the public Gydos.org email listed with the repositories.