Reply

Yeah I guess "don't take the piss" isn't quite as descriptive as it could be. Talking with your manager and seeing what's reasonable is best, but ie taking two weeks longer to do a "straightforward" task may not be the best

 Bookmark

Bookmarked How to Build Software like an SRE
Post details
I’ve been doing this “reliability” stuff for a little while now (~5 years), at companies ranging from about 20 developers to over 2,000. I’ve always cared primarily about the software elements I describe as living “outside” the application – like, how does it get its configuration? What kinds of instances does it run on, and are those the best kinds to use? What steps does it take on its path from “code in a repository” to “running in production”? And I’ve always kept track of what I liked – which mechanisms allowed fast iteration and which caused frustration, which led to outages and which prevented them.