
Director, Site Reliability Engineering at Intercontinental Exchange; formerly @ProtectWiseInc, @SendGrid. Cyclist. Opinions my own. Now @tarrall.bsky.social
Atlanta
Joined October 2008
- Tweets2.7K
- Following550
- Followers260
- Likes11.2K
#DevOps was just step 1. – at Denver, CO
Robert Tarrall, Salty Reliability Engineer retweeted
Beginning the response and learning the incident has not been properly scoped...
Robert Tarrall, Salty Reliability Engineer retweeted
I worked on a product that could ship hourly, and had to comply with European banking regulations about traceability. Your arguments about why you can't deploy on Friday are invalid. Listen to Charity. – at Dexter, MI
Replying to @mipsytipsy
If you're scared of pushing to production on Fridays, I recommend reassigning all your developer cycles off of feature development and onto your CI/CD process and observability tooling for as long as it takes to ✨fix that✨.
Robert Tarrall, Salty Reliability Engineer retweeted
I meditated 15 hours a day for 6 months straight with one of the toughest Buddhist monks on the planet.
Here's what I learned:
Running through my follows trying to add as many to Mastodon as I can.
All the Infosec and SRE peeps are there, of course. But I'm gonna miss all the "secondary" stuff I follow -- friends from devrel, sales, PMO; random meme queens, local businesses.
1/2
1
Robert Tarrall, Salty Reliability Engineer retweeted
61. TFW you find a job that pays you to identify problems that nobody's responsible for and fix them, thereby improving the way everything works for everybody while satisfying your need to optimize systems.
But what’s considered “excessive”? I rarely went over 500 pages/day; that’s not excessive right?
Right?
Replying to @mykola
56. TFW you read that "excessive childhood reading" is considered a form of dissociation.
Robert Tarrall, Salty Reliability Engineer retweeted
So cryptocurrency is enriching the same group of billionaires and corporate elites as the traditional banking system.
And it mirrors the same unregulated banking system that caused the 2008 crash.
AND when it crashes, working people are the ones losing their life savings.
I woulda said it’s a geek tragedy, but otherwise this thread is spot on.
Replying to @sarahmei
More seriously, I think it’s truly sad that there are people who think so little of themselves, deep down, that they will intentionally sacrifice their time and relationships and energy…just to make somebody else rich.
It’s a goddamn greek tragedy
1
Robert Tarrall, Salty Reliability Engineer retweeted
twitter employee: you’re back early
elon musk: backend’s haunted
twitter employee: what?
elon musk: *loading flamethrower and going back into the data center* backend’s haunted
Infosec friends, please… someone’s GOTTA make this happen.
1
Robert Tarrall, Salty Reliability Engineer retweeted
I don’t think many people realize how there’s a huge Big Tech software engineering slowdown upon us and the secondary and tertiary effects this will have on so many things.
Eg how new grads will be hit far harder in finding their first job - anywhere, not just at Big Tech.
Robert Tarrall, Salty Reliability Engineer retweeted
A common problem with long queues in distributed systems is that they make recovery time worse: by the time a system recovers, it has built up a long backlog of work that needs to be done before new work succeeds. LIFO queues (stacks) are sometimes a good way to avoid that, but..
Robert Tarrall, Salty Reliability Engineer retweeted
"Look, if we launch a service/API in prod, that thing needs to STAY. There's no option to retire it on any short-term time horizon, even if it's making a huge loss."
- from a software engineer at AWS.
The biggest difference between GCP and AWS: GCP did not have this principle.



















