4 ms·
> you could deploy it independently what exactly does this mean? you work on a team, team is responsible for the product. there is nothing "independent" about
by bdangubic 9mo ago
> you could deploy it independently
what exactly does this mean? you work on a team, team is responsible for the product. there is nothing "independent" about it. everyone does their job, everyone deploys to production. if you are at any place where "deploying to production" is an "event" then for sure I would advice either leave or if that is not an option work towards this goal. there should be no one on the team that can't "deploy to production" and there shouldn't really be anything "independent" thing going on in my opinion. I see a whole lot of discussion and struggles around this though...
- zmmmmm 9mo agoI can believe in certain domains things can work this way, but we have way too many complex stakeholders and dependencies to have random deploys to production constantly happening without notice by anybody who feels like it. At very least there is comms, stakeholder signoff, etc. How would you have eg: customer support staff able to operate if the very button they are telling the customer to press disappears or changes its text during the call?