HOW I BUILD
Most solo developers don't build QA infrastructure. I did. Every system in the Granite ecosystem goes through a rigorous build-test-deploy pipeline before it touches production.
THE WORKFLOW
Every feature starts with database design. Tables and columns are defined and created before a single route or template is written. Run PRAGMA table_info() to verify before writing queries.
All new code goes to a working copy — never directly to production. The working file gets syntax checked, tested, and verified before it replaces anything live.
Routes are hit with real HTTP requests. Pages are loaded in the browser. Column mismatches and template errors only surface at runtime — syntax checks alone aren't enough.
The centralized testing platform runs automated integration tests against live endpoints. Generates a Production Readiness Report with letter grades (A through F) and phase-by-phase scoring.
Working copy is verified to match production via byte-level comparison. File sync across 5 checkpoint locations. Only after all checks pass does the new code go live.
Every session ends with zero temp files. No leftover scripts, no orphaned test data. Clean workspace, clean codebase.
THE TOOLS
Tracks what's been built, what's in progress, and what's next across the entire ecosystem. Prevents duplicate work and keeps priorities straight.
Defines pass/fail criteria for every system. BUG, WARNING, and INFO severity levels with automated findings engine following Google SWE/SRE PRR standards.
Maintains continuity between development sessions. Every session starts by reading the handoff doc. Every session ends by updating it. No context is ever lost.
Systematic debugging approach: reproduce, isolate, fix in temp, verify, deploy. No guessing, no "try this and see."
Automated test generation and execution. Wipe and re-seed database before final test runs. Account for seeded default IDs. Include reject buttons alongside approve.