Hacker News new | past | comments | ask | show | jobs | submit login

As a person who builds, I am awfully grateful for the people who maintain, as my stuff would never work without them.



I think devs should be responsible for maintaining what they build. You get your incentives aligned better that way, and it removes the tension.


This is actually covered pretty well (imho) in Chapter 32. Many services start out wholly supported by their developers, and are only onboarded to SRE after they reach a certain level of maturity (and/or criticality to the business)

Even after SRE takes over operations of a service, developers remain closely involved, and in many cases have their own pager rotation for "something's really broken, SRE has stopped the user-visible bleeding, but we need a code owner to jump in and help solve the root issue."


Well, I haven't read the book yet, but the commentary seems to suggest the SRE's role is more to teach the devs how to make their software maintainable, scalable and reliable, and then verify it really meets all of those traits.

As a developer, that is a service I greatly value, and greatly respect those who have that knowledge and experience.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: