Reusable solutions and practices that emerge from applying Organic Flow. These patterns help you work more effectively with the methodology.
No patterns have been harvested yet in this repository. Below are example patterns to illustrate the concept.
Match your energy level to appropriate tasks for optimal flow
Example
Morning (High Energy): Architecture design, complex problem solving Afternoon (Medium Energy): Regular development, code reviews Evening (Low Energy): Documentation, simple fixes, organization
Consistent format for harvesting learnings from experiments
Example
## What We Learned - [Specific discovery] ## What Worked - [Successful approaches] ## What Didn't Work - [Failed approaches and why] ## Recommendations - [Actionable next steps]
Clear branch names that communicate intent
Example
experiment/[hypothesis-keyword] Example: experiment/parallel-tests Example: experiment/redis-caching Example: experiment/websocket-sync
Every failed experiment contains valuable insights
Example
Document: - Why the approach seemed promising - What specific issues were encountered - Alternative approaches discovered - Constraints that were uncovered
Workflows and procedures that make Organic Flow more effective. Examples: Knowledge PR templates, experiment lifecycle, harvest protocols.
Code organization and architecture patterns discovered through experiments. Examples: API design, testing strategies, performance optimizations.
Collaboration practices for teams using Organic Flow. Examples: Review processes, knowledge sharing, onboarding flows.
Mental models and approaches that support knowledge-first development. Examples: Embracing failure, curiosity-driven development, learning loops.
Patterns emerge from experiments. When you discover a reusable solution:
patterns/