Episode 4: Mooving to... Successful Engineering in the Remote World
Episode 4, Mooving to… Successful Engineering in the Remote World offers a unique perspective on work-life balance and expectations.
Episode 4, Mooving to… Successful Engineering in the Remote World offers a unique perspective on work-life balance and expectations.
Here at incident.io, we provide a Slack-based incident response tool. The product is powered by a monolithic Go backend service, serving an API that powers Slack interactions, serves an API for our web dashboard, and runs background jobs that help run our customers incidents. Incidents are high-stakes, and we want to know when something has gone wrong. One of the tools we use is Sentry, which is where our Go backend send its errors.
The cloud is easy and powerful—until it’s not. Once companies have customers, commitments, and compliance concerns, they often have to create cloud operations teams to manage the cloud on behalf of their fellow employees. Often, organizations that migrate to the cloud find themselves hampered by inefficient cloud operations if they haven’t standardized their IT procedures for operability.
During major incidents, it’s crucial that all stakeholders are provided with the status updates they need. Those communications however need to be tailored to what the stakeholder actually needs, and provided in a streamlined format that works best for them. Just like alert fatigue, communication fatigue can be detrimental during an outage or other service reliability issue.
With our April update, we ship some great improvements for Signl categories, category-based alerting and duty scheduling. All details are available in this blog article.
The effects of BigPanda’s most recent round of funding—amounting to $190 million—will be reverberating throughout the company for years to come. And it’s not just BigPanda employees who have experienced a surge of enthusiasm in the wake of our Unicorn status. Our customers are thrilled at the prospect of more innovation from our team and new products that help them automate and evolve.
When incidents inevitably occur in your software stack, managing them well could be the difference between losing customers and building trust with them. In this article, we’ll give you and your team some best practices on how to prepare for managing incidents. It’s crucial to define service ownership, a declaration process, and practice all of it. With a little planning now, you'll be able to cut your incident response time drastically.
This is Part 1 of a two-part series on Blameless Postmortems. Today, we'll discuss why blameless postmortems are so important and their implications for your team; the second part will go into detail on how to set them up as a process and make them successful. Somebody wise may have once told you that how we handle adversity shows our character. Being able to acknowledge and admit mistakes is the first step towards learning - it's a key part of success both in personal relationships and in large companies.