Home / Companies / Incident.io / Blog / December 2021

December 2021 Summaries

5 posts from Incident.io

Filter
Month: Year:
Post Summaries Back to Blog
The text discusses a pattern for mocking external client libraries in Go while keeping the code simple and ensuring all the code down a call stack uses the same mock client. This is achieved by generating a mock using tools like interfacer and gomock, and then injecting it with context.Context. The resulting test suite improves developer productivity when writing tests.
Dec 21, 2021 1,370 words in the original blog post.
Incident.io has successfully completed its Service Organization Control (SOC) 2 Type I audit, demonstrating that it meets high security standards for the management and operation of its software. SOC 2 is an information security standard focusing on controls for data security, availability, and privacy. The company uses Vanta to automate compliance by continuously monitoring its entire environment and providing real-time evidence to auditors. Incident.io plans to follow up with a Type II audit in the near future to confirm consistent adherence to these practices over time.
Dec 20, 2021 400 words in the original blog post.
Incident.io, a SaaS business, has an on-call rota to provide 24x7 coverage for their app. They believe everyone should be on-call as it helps tighten feedback loops between shipping and running the product, leading to better engineering decisions. The company compensates for the inconvenience of being on-call by paying a fixed amount per week, calculated automatically from schedules. They also aim to make overrides fair and avoid complex swaps of time. Incident.io cares about employees' home life and provides support during on-call shifts, including finding replacements when needed and encouraging communication about personal situations.
Dec 16, 2021 558 words in the original blog post.
Breaking down complex projects into smaller, shippable increments helps mitigate risks by allowing for early feedback collection and assumption validation before fully committing to a solution. Shipping smaller increments provides value delivery, gathers feedback, validates an approach, and offers clear achievable goals for the team. It also reduces uncertainty and provides natural pause-points for addressing unplanned work. To find shippable increments, consider use-cases that can be enabled with a subset of the original product. Prioritize based on value delivery, feedback gathering, and approach validation. Silent shipping is an alternative option when user-facing features are not feasible.
Dec 14, 2021 1,165 words in the original blog post.
Incident.io has introduced Workflows, a feature that allows users to configure their specific business processes and requirements into the platform. This extension point enables organizations to automate certain actions and behaviors based on specific triggers, making incident response more efficient and effective. The new feature includes practical applications such as automatic escalation of incidents, creation of bespoke runbooks, and triggering Decision Flows based on keywords or incident types.
Dec 01, 2021 1,223 words in the original blog post.