FAQ
Direct answers to the questions this site's format tends to raise: private repos, maturity labels, location, availability, why so many systems.
Anything not covered here, ask directly: [email protected].
- Why are some repos private?
-
Two different reasons. kanon is private by choice — it's not yet hardened for public traffic, even though five other repos on this site depend on it in production; its case-study page exists so the design thinking is visible without the source. Systems I built in employment belong to that employer and are described only as professional experience, never presented as portfolio.
- What does a label like 'pre-alpha' or 'Phase 4 blocked on hardware' actually mean?
-
It means exactly what it says, quoted from the repo's own current status line, never rounded up. The rule behind every badge on this site: a system says what state it's in, not what it aspires to. That's a credibility argument, not an apology — a demo paired with an honest limit is more convincing than a demo that hides one.
- Are you open to relocation or remote work?
-
Remote-first, based in Austin, Texas. Happy to talk specifics directly.
- What's the comp range or availability?
-
Depends on the role and scope. Short version: in a W2 search alongside a part-time consulting engagement through October. Ask directly at /contact/ and I'll give a straight answer.
- Why so many independent systems instead of one thing?
-
Because the thing being demonstrated is a systems-engineering practice, not a single startup pitch. The same standards, gates, and naming discipline gets applied across every system at /systems/ — on purpose, so the pattern is visible across domains instead of being a one-off feature of a single codebase. That's the thesis of the whole site, stated once, here, plainly.