Hey there!
Jay here, host of On-Call Nightmares Podcast and Azure Cloud Advocate.
Are you currently on-call at your current role? Let's discuss some of the aspects of being on-call that you find are the most valuable. What are you loving right now about the on-call practice in your current role? I believe on-call is an incredible learning resource for teams in technology because it requires you to create some structure in how to handle failure.
Share with me and lets discuss more on how we can lift up on-call work and not make it feel like it's such a "nightmare." Leave your comments below!
While you're at it, make sure you check out the free Azure $200 in credits and 12 months of free services. That's a ton of cool resources to start demoing that app you might have! The tutorial, Create a Node.js web app in Azure is a great way to start learning.
Top comments (5)
I don't do on-call any more but I use to be on-call at night with the rest of my team incase the servers went down or had any issues. The hardest part about this was there was no schedule or communication, so if someone was already starting to fix the issue(s), you may not always have known it. My piece of advice for on-call teams is to make sure you have some form of schedule and communication about these issues. It can make a huge difference when working together to solve problems.
A rotation with a schedule and a plan for communication are critical.
Definitely. It forces a team to also really have a good understanding of permissions and not be in too many "call this one person who has permission" scenarios".
In terms of being on-call, I typically use my weekend support duties as a chance to do a bit of creative coding that doesn't really fit into some of my more hectic weekday work days.
we should talk about the things learned in expanding dev.to sometime!
hey all - leave the best aspects of your team's on-call here.