Hacker News Reader

I can see that happening as a result of some other requirement, but I can't work out why you'd purposefully structure a team so that only one team member can push to production. To me, the downsides (single point of failure) outweigh the benefits (ease of deployment.) Is there something I'm missing?

View on HN

Well, each team member has their own set of skills.

Say ... Joe. Joe is good at looking at some mockup and turning it into html+css code.

So somewhere in the development process, Joe has an important role.

But why should Joe be able to push something to production?

I think the argument isn't so much that "everyone needs to be able to push to production" as much as "more than one person should be able to push to production". Bus factor is an important variable.

That's like saying a company needs two CEOs because of bus factor.

Somebody else can take over the role of being responsible for pushing to production any time.

Not if they've never done it before.

When it’s a no-tools manual process? Unlikely.

Yes. Money. You are missing that it's often missing.

Reply on news.ycombinator.com