3 ms·
Love the idea! It always made me nervous when I was given access to other teams tools with the ability to inadvertently break them. It sounds like for now you
by teej 7y ago
Love the idea! It always made me nervous when I was given access to other teams tools with the ability to inadvertently break them.
It sounds like for now you could still end up with out-of-band changes because you can’t force folks to use a browser extension before twiddling switches on a confit page. What’s your long term vision for tackling that aspect of the problem?
- vikrum 7y agoAgreed that the surface area around the out-of-band changes is a concern. We find that educating our users around getting the extension installed team wide is the primary approach by way of policy (in GSuite orgs, you can install extensions team wide) or training (on-boarding docs/new hire orientation). Just as with source control we can commit straight to the main branch, it's through policy/training that we do things like mandatory pull-requests/reviews to not "allow" that. Long term we envision Gold Fig plugging in to your projects as a read-only member to pick up any other out-of-band changes.