Re:We saved $50k/year with a Go microservice coded in a hack...
by toddBarkus on Tuesday April 10, 2018 @09:01PM
(#16807176)
I think this is a case for the return of the traditional "sysadmin" as "devops"/"SRE" is now the role of unblocking deploying a solution instead of questioning it's complexity/fitness.
[ Parent
| on HN ]
Re:We saved $50k/year with a Go microservice coded in a hack...
by cookiecaper on Tuesday April 10, 2018 @09:33PM
(#16807311)
While I agree, I also think that overt gating and approval processes create a high tension dynamic that frequently breaks down, whether it's ops v. dev, security v. dev, or others. It's easy for people to get their pride wounded, and they end up encouraged to find workarounds to the process. The simple answers to this are pretty much imaginary, unfortunately.
Re:We saved $50k/year with a Go microservice coded in a hack...
by toddBarkus on Wednesday April 11, 2018 @08:08AM
(#16810272)
Sure, of course. I was hoping to point out that there's an increasingly overlooked value in having someone question complexity. The "no, you don't need React" of the frontend dev or the "our data is actually relational" of the back end dev.
Re:We saved $50k/year with a Go microservice coded in a hack...
by rbranson on Tuesday April 10, 2018 @11:27PM
(#16807801)
If your “SRE” team is only “unblocking deploying a solution” then I’m sad to say they are an operations team who has rebranded themselves to appear more relevant.
Re:We saved $50k/year with a Go microservice coded in a hack...
by toddBarkus on Wednesday April 11, 2018 @08:05AM
(#16810260)
That's most "SRE" -- it's a title arms race in that field between the underqualified and those that wish to convey they know how to do more than write system scripts in DSLs