4 ms·

This is completely backwards. As someone that has been an SRE and DevOps engineer. Almost all of the questions can be simply answered with: "This is a NFR that

This is completely backwards. As someone that has been an SRE and DevOps engineer. Almost all of the questions can be simply answered with: "This is a NFR that was created by SRE". The important thing is to collaborate with each team and be there when architectural and design decisions are being made in the first place! All of these questions are post-hoc, coming after the thing has been built. You would never need to ask these questions, if you help drive initial design. Embed yourself with your teams. Ask to be part of design discussions. Remember: 50% eng 50% ops. You have no excuse!

KronisLV 4y ago
> Embed yourself with your teams. Ask to be part of design discussions. I agree that this should happen, most successful projects have people with all sorts of knowledge contributing to it, without too many silos in place. > You have no excuse! However, the Ops people don't always get that power or a say in the matter. In many dysfunctional environments they'll simply be given an apparently finished service and will be told to put it in prod. Please don't dismiss that these circumstances exist altogether and don't shift the "blame" exclusively on the people who already have their lives be needlessly hard, this isn't likely to encourage a positive outlook.
- jamesrom 4y ago
  > Please don't dismiss that these circumstances exist altogether and don't shift the "blame" exclusively on the people who already have their lives be needlessly hard, this isn't likely to encourage a positive outlook. Au contraire, OP was blaming engineers with a "holier than thou" attitude. That exact attitude is the kind of thing that leads to the dysfunctional environments that you speak of. Should SWE consider SRE at design time? Absolutely. Should SRE consider SWE at design time? Absolutely.

4 ms·

This is completely backwards. As someone that has been an SRE and DevOps engineer. Almost all of the questions can be simply answered with: "This is a NFR that

by jamesrom 4y ago

KronisLV 4y ago
> Embed yourself with your teams. Ask to be part of design discussions. I agree that this should happen, most successful projects have people with all sorts of knowledge contributing to it, without too many silos in place. > You have no excuse! However, the Ops people don't always get that power or a say in the matter. In many dysfunctional environments they'll simply be given an apparently finished service and will be told to put it in prod. Please don't dismiss that these circumstances exist altogether and don't shift the "blame" exclusively on the people who already have their lives be needlessly hard, this isn't likely to encourage a positive outlook.
- jamesrom 4y ago
  > Please don't dismiss that these circumstances exist altogether and don't shift the "blame" exclusively on the people who already have their lives be needlessly hard, this isn't likely to encourage a positive outlook. Au contraire, OP was blaming engineers with a "holier than thou" attitude. That exact attitude is the kind of thing that leads to the dysfunctional environments that you speak of. Should SWE consider SRE at design time? Absolutely. Should SRE consider SWE at design time? Absolutely.