schmudde

I'd like to encourage more domain exploration on our small team. A dev in the current flow implements a solution and deploys to production with guardrails (feature flags, admin privileges, etc...).

This has worked well, but has come with two costs:

1. Indicating and managing experimental code in both the pull request and production. 2. Bringing other team members along for the ride.

Both of these issues are mitigated with a more traditional flow of writing up a proposal in English, getting it approved by others, and then going into implementation.

Hopefully the tradeoffs are apparent to this crowd. Any thoughts on mitigating these two specific costs while enjoying the benefits of quick feedback loops?