StatusCake

Meet the StatusCake Team – Week Commencing 14th October 2019

ssl monitoring

This week the StatusCake.com are going to be at the following events.  Do please get in touch by email us or by live chat on the StatusCake website if you’d like to meet us.

Monday 14th October 2019

Business Ideas & The Best Internet Strategies to Start Your Business

Mario Giraldo our Head of Partnerships will be the meet-up this evening hoping to meet individuals and companies that are looking to start a business online or already have a business and are looking to find more customers or other ways of monetising their traffic.

Thursday 17th October 2019

HireCon: Tech Skills Summit, London

Hemm Kerrai our head of tech will be at the HireCon: Tech Skills Summit at the Oval Space this coming Thursday.  We currently have multiple roles open at StatusCake for PHP and GoLang devs as well as a DevOps so if you’d like to meet and discuss any of those opportunities email us to arrange a time to meet.

DevOps Underground – 2 Presentations: Kubernetes Ingress & DevOps and Microservices Better Together

Our dev team will be at the Skills Matter DevOps Underground meet-up on Thursday evening.  The meet-up has two presentations; the first from Mark Boddington looking at the history of containers and have Docker has become the go-to app for application packaging.  It will also look at Kubernetes and how this has itself become top dog, beating Docker even, for all things orchestration and finishing off looking at the Ingress Specification and the NGINX Ingress Controller.

The second presentation by Sean Farmer “DevOps & Microservices Better Together” takes a look at what it takes to successfully transform your DevOps team and functions.  Looking at everything from testing and deploying work, how your DevOps team works within the wider business teams, and how you can reduce the lead time of rolling out those all important new features.  The presentation will help you identify what things might hold you back, and what you can do to overcome those obstacles and succeed.

Speakers: @farmar & Mark Boddington of @nginx.

Share this

More from StatusCake

Alerting Is a Socio-Technical System

3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting

Designing Alerts for Action

3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams

A Notification List Is Not a Team

3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years

Alert Noise Isn’t an Accident — It’s a Design Decision

3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.

The Incident Checklist: Reducing Cognitive Load When It Matters Most

4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already

When Things Go Wrong, Systems Should Help Humans — Not Fight Them

3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,

Want to know how much website downtime costs, and the impact it can have on your business?

Find out everything you need to know in our new uptime monitoring whitepaper 2021

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.