It's completely normal to feel a little overwhelmed and stressed out at work these days. Technology has collaboration moving at the speed of light, and time away from screens is at an all-time low, blurring the lines between work and personal time. Plus, it's hard to ignore the multitude of tech outages that have been making headlines lately, leaving teams anxiously on edge. When you are a professional with on-call cycles, the potential of outages adds another level of complexity to the mix.

We’ve come a long way from the first On-call schedule editor we built, and this new release takes the user experience for Zenduty Schedules a hundred steps further! (…103 steps further precisely, says our internal changelog)

On Tuesday, March 5th, Facebook, Instagram and Google Ads experienced widespread outages that lasted for nearly two hours, affecting thousands of users worldwide. More than 550,000 reports poured in from Facebook users, and Instagram received 92,000 similar complaints, as reported by Reuters. As Meta stated on their newest platform, Threads: ”Earlier today, a technical issue caused people to have difficulty accessing some of our services.

Is your DevOps tool stack out of control? I feel like every day, I talk to someone who feels this pain. The technological golden age of the past few years created a lot of niche tools, but now that CFOs and boards alike are demanding budget restraint, many of these tools are being scrutinized. The reality of the situation is that it’s not good enough for a tool to do one thing anymore.

With our SIGNL4 March Update, we are speeding up and have once again completed some innovations for you. This time, we have further developed our design and color scheme slightly and made changes for better readability. In our mobile app, you can now also quickly and easily set up a stand-in, should a person unexpectedly be absent from duty. Furthermore, in certain SIGNL4 plans, the data retention period can now be flexibly adjusted to the respective company requirements.

It’s 3am. You wake up to a blaring alarm, the sound burned into your soul from countless sleepless nights. You reach for your phone, ‘press 4 to acknowledge’ and bleary eyed, you open your laptop, grab a coffee and get to work. The next hour is a whirlwind—bringing services back online, keeping colleagues in the loop, maintaining a list of action items, updating a status page that will be seen by millions of customers. Potentially for the fifth time this month.

The financial services industry is experiencing a profound shift. Customers now demand a flawless experience across all touchpoints, including online platforms, mobile devices, ATMs, and physical branches. Any lapse in performance or reliability in these channels can lead to dissatisfaction. Moreover, the competition is intensifying as technology-focused companies, more nimble and innovative than traditional counterparts, are continuously disrupting the market.

There was recently some confusion in the office that I thought was worth researching and addressing. Depending on who you are talking to, you may hear the acronym DORA in one of two contexts. (OK, three if you’re talking to a preschooler!) It might be in relation to DORA metrics–that is, a set of metrics associated with DevOps Research and Assessment.

The pressure to constantly innovate and release new features can often clash with the need for a stable and reliable product. While there might be some temporary cutbacks in testing time to achieve high feature velocity, ensuring reliability doesn't have to be an afterthought. We reached out to industry experts to gather their insights on ensuring reliability during phases that demand high feature velocity. Here's what they had to say.

In the ever-evolving landscape of APIs, ensuring seamless interactions and managing changes becomes crucial. While innovation and adaptability are essential, maintaining backward compatibility is equally important to avoid disruption for existing users. This is where REST API versioning comes into play. Versioning allows you to introduce new features or changes to your API in a controlled manner, while simultaneously keeping older versions running smoothly.