Do you use release environments?
I’m curious about how much traditional development lifecycle people are using in their ICM builds and *why* they found that was the right level.
Do you bother with some kind of development > staging > production equivalent? If so, what does this look like in your setup?
For me, development is essentially a system playground folder where things are before they are ready and wired.
I’m using my “governance” settings as a cheap way to have staging without actually having staging - I dial back the permissions when something is released and see how it performs on several runs before loosening those off and letting it go more on its own without permissions - essentially prod.
Because what I’m currently building myself is for a user market of exactly one (me), this works exceptionally well.
But it’s on my mind - what are you all going for? And what’s the thinking behind it?
Yes, all the way
Nah, too much work
Sometimes depending on the build
What’s a release environment?
1 vote
3
4 comments
Mira Bradshaw
3
Do you use release environments?
Clief Notes
skool.com/cliefnotes
Jake Van Clief, giving you the Cliff notes on the new AI age.
Leaderboard (30-day)
Powered by