c/research.ai-dev-principles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: principle #27 — add grain of salt, clarify scope (prototyping vs production)

Browse Source
This commit is contained in:
Christian Nennemann
2026-03-31 21:37:21 +00:00
parent 68e2c6e7a8
commit 32d916f17f
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@@ -283,16 +283,16 @@ Plan-Do-Check-Act after every sprint, not just at the end. Check catches bugs be
**Origin:** Sprint 1-3 each had a PDCA cycle that caught rate limiting issues, SSE race conditions, and Caddy routing gaps. **Origin:** Sprint 1-3 each had a PDCA cycle that caught rate limiting issues, SSE race conditions, and Caddy routing gaps.
### 27. Test in Production, Not in Mocks ### 27. Test in Production (for fast prototyping)
For single-user tools: test against the real deployment. Mocks hide integration bugs. For single-user tools in rapid prototyping: test against the real deployment. Mocks hide integration bugs. **Grain of salt:** This applies to MVPs and personal tools. For multi-user, shared, or safety-critical systems, use proper staging environments and test suites.
- `curl` against the live API after each deploy - Fast prototyping: `curl` against live API, try PWA on real phone, submit real jobs
- Try the PWA on your actual phone - Production-grade: staging environment, automated test suite, canary deploys
- Submit real jobs through the real worker - The principle is about speed of feedback, not skipping quality gates
- Read the real debug logs - Know when you've graduated from prototype to product — then add proper testing
**Origin:** "Committe regelmäßig und test in production — keine mocks!" **Origin:** "Committe regelmäßig und test in production — keine mocks!" (during rapid MVP sprint)
### 28. Changelog as First-Class Artifact ### 28. Changelog as First-Class Artifact