Teams | Collaboration | Customer Service | Project Management

Messaging has surged in popularity and become a go-to channel for many consumers since the COVID-19 pandemic. It looks like the trend is here to stay—74 percent of customers who messaged with companies in 2020 plan to continue doing so. Research also shows that 76 percent of consumers like to buy products using chat or messaging, and 72 percent are more likely to make a purchase online if they can ask questions in real-time. Google’s Business Messages enables buyers to do both.

We recently had the opportunity to speak to a student audience at Serverless Days and came up with some insights that we felt were worth sharing with a wider audience. Please take a look and let us know your thoughts @trycourier. Serverless architecture is relatively new, yet many startup developers prefer building their foundation on a Serverless framework. But what's with the hype?

How to Set Up Multi-Channel Notifications in Your AWS Stack In this article, we’ll walk through an example architecture for building your own notification service with AWS, and show you how to implement it in Node.js. We’ll also discuss a few considerations related to using AWS services for notifications. Let’s dive in!

Imagine a typical day at work that starts with checking Google Calendar to prepare for where you need to be and when. With engaging discussions, your teams create Google Docs to take notes on the important decisions coming out of the meetings and begin writing briefs to kick off your company’s next big project. Then you turn to Sheets to track the KPIs and leverage Slides to prepare the final presentation for your executive leadership by 4pm that day.

As we’ve previously written, old-fashioned employee time tracking methods such as paper timecards or Excel come with several downsides. First, the payroll process is time consuming and error prone, as you have to manually tally hours and overtime. Second, you don’t know if your employees are in fact on the job when they’re punching in, rather than a coworker (and those extra minutes or hours that employees report working can lead to a significant waste of money).

In the daily life of a Site Reliability Engineer, the main goal is to reduce all the work we call toil. But what is toil? Toil is the kind of work tied to running a production service that tends to be manual, repetitive, automatable, tactical, devoid of enduring value, and scales linearly as a service grows. This blog post describes our journey to automate our nodes rotation process when we have a new AMI release and the open source tools we built on this.