undefined | Better HN

0 pointsraw_anon_11111mo ago0 comments

That’s exactly what it means , a person who reports to the infrastructure team who decides standards and is embedded with the devs as part of the project.

If you are just throwing things over the fence - you’re an “operations” team and get none of the benefits of DevOps

0 comments

mancerayder1mo ago

Understood, but so far what I observed is the embedded devops pressured/saying Yes/beholden to a PM running sprints, and the central infra team management constantly has to intervene to protect the embedded devops engineer politically.

Maybe my experience is a rare example, but my conclusion so far is that it's tricky to prevent this painful situation, and requires vigilance.

raw_anon_1111OP1mo ago

And once you have the infra team saying no all of the time and being antagonistic - you’re back to old school operations and you aren’t a DevOps shop.

mancerayder1mo ago

But if they never say no, how do you maintain central infrastructure standards?

If you say yes all the time, I feel like that's how you turn devops into Ops monkeys who are reactive, since people are operating on Sprint timelines instead of optimizing for long-term stability.

1 more reply

j / k navigate · click thread line to collapse

0 pointsraw_anon_11111mo ago0 comments

That’s exactly what it means , a person who reports to the infrastructure team who decides standards and is embedded with the devs as part of the project.

If you are just throwing things over the fence - you’re an “operations” team and get none of the benefits of DevOps

0 comments

mancerayder1mo ago

Maybe my experience is a rare example, but my conclusion so far is that it's tricky to prevent this painful situation, and requires vigilance.

raw_anon_1111OP1mo ago

And once you have the infra team saying no all of the time and being antagonistic - you’re back to old school operations and you aren’t a DevOps shop.

mancerayder1mo ago

But if they never say no, how do you maintain central infrastructure standards?

If you say yes all the time, I feel like that's how you turn devops into Ops monkeys who are reactive, since people are operating on Sprint timelines instead of optimizing for long-term stability.

1 more reply

j / k navigate · click thread line to collapse