Telecommute - sgml/signature GitHub Wiki

Strategies without CI/CD

Manual test suites

Even without automated pipelines, maintain a shared set of manual test cases in text form. Both members can run them locally to validate consistency.

Version control discipline

Use Git (or any VCS) as the central coordination tool. Commit often, with clear messages. The repository becomes the “conversation” and the arbiter of decisions.

Text‑based decision logs

Keep a Markdown file in the repo documenting design choices. This substitutes for governance and ensures decisions are visible and revisitable.

Accessible formats only

Since one member is blind, avoid diagrams or screenshots. Use structured text, tables, and pseudocode that screen readers can parse.

Periodic checkpoints

Without CI/CD, schedule manual “sync points” where both members pull, build, and run the system to ensure alignment. This reduces drift.

Convention over invention

Stick to widely recognized patterns (file structures, naming conventions, API styles). This reduces the chance of isolated, idiosyncratic solutions.

Artifact reproducibility

Every decision should leave behind a reproducible artifact: a script, a config file, or a documented rationale. This makes the project self‑explaining even without communication.