Over the past year, Spike.sh social media activity has been null. As a bunch of shy nerds in a small team working remotely across the world, we really never bothered with social media and our presence on it. We always kept our heads low and maneuvered around it. But no more. As of today, we are coming back on social media channels like LinkedIn, Twitter, and Reddit as well.
Our status page product started last year as an experiment. We built a status page product in a hurry over weekends, and to our surprise, it gained a lot of traction. People were using it and giving us feedback, which helped us improve the product over time. And this year, we're thrilled to announce that we have great things planned for our status page product! The new revemped dashboard is part of a larger plan for our status page product. Here's a quick gist of the multiple releases.
A neatly setup access control telling which user can do exactly what on an incident management platform can save a lot of time and hassle in the future. In the past, Spike.sh had only 2 roles - Admin and Member. The only difference in these roles were that only Admins can remove members. It was fairly simple and most users liked it. However, with larger teams coming onboard, it gets a little difficult to control for admins. So, we have empowered the existing system by adding two more roles.
Andon Cord catapulted Toyota into 40 years of unprecedented quality and domination. What is Andon Cord and how did they do it? In the early 1900s, Taiichi Ohno architected and introduced Andon cord in Toyota's manufacturing plants. The problem: This costs a lot of money. Production costs have always been high. In 1984, it cost NUMMI $15,000 per minute. That's $42,758 in today's value.
Over the last couple of years, Spike.sh has largely been a Simple Incident Management Platform helping engineering teams across the world. Our focus on simplicity has been well received by all of you and we couldn't be more happy about it. After speaking with users earlier this year, we quickly realised there is a lot we can do to help our responders and help them better than we currently are.
Incident management is easily one of the most annoying things anyone has to ever deal with. There will always be only a handful of people who would ever want to walk into the building on fire to mitigate. That’s the same with most engineering teams. Only a handful are willing to get in, find the root cause, and mitigate the incident.
Over the last few months, a number of our users have asked if we can add more context to their alerts. We spoke with them on our live chat on dashboard and brainstormed the idea of Title Remapper.
Add multiple responders to one or more incidents. Helps in gaining empathy, transparency, and future context for an incident that helps reduce MTTR.
Introduction As all companies become software driven, DevOps is becoming an important practice in enterprises and startups across the world. DevOps is about bringing velocity to delivering tech products and services, so you can delight customers and meet business goals. To achieve this velocity, development (dev) and operations (ops) teams work closely together across the software lifecycle - from planning to release. And this has led to a new role in engineering teams - DevOps Engineer.
Cloudflare is a global cloud services provider that is based all over the globe, from San Francisco, US to London, England to Sydney, Australia. Their mission, as stated front and center on their homepage, is to help build a better Internet. While that may read like hyperbole, their numbers are impressive - Cloudflare has over 126,000 paying customers and 95% of Internet Users in the developed world are within 50ms of their network.
