Lightstep from ServiceNow Logo





Lightstep from ServiceNow Logo
< all blogs

How to deploy on Friday and feel good about it

Oh, the joys of a deploy. There’s ups, and downs, and more downs. Did you test on staging enough? Is the person who is on call actually going to answer if anything happens? (Hint: something may happen) Is it safe to deploy? How about now? (Hint: probably not) Now?? And, then guess what? You waited too long and now you have to deploy on Friday. Bad news.

Note to self: Don't deploy on Fridays

— Twitter Engineering (@TwitterEng) February 7, 2020February 7, 2020

To get a better sense of what engineers go through when deploying, we interviewed three of them. (Thankfully, this was not a whiteboard interview.)

Question: What is the best thing about deploying?

  1. The best is when everything goes smoothly. 

  2. I like the idea of something new coming out of each deployment.

  3. Being able to see my hard work come to life is a great feeling. 

Q: How do you feel about being on call?

  1. As long as I know who deployed and who wrote the code, it’s fine.

  2. I feel like I can handle whatever comes up.

  3. I love it. I want to be able to help in any way I can.

Q: What's the worst day to deploy

  1. Friday, at 4:00 to be exact, when I should be home.

  2. Fridays are the most difficult, but as long as things go well it’s alright.

  3. My energy levels are too low to deploy on Fridays. I really need to be in the right mindset.

Q: How can you plan ahead?

  1. Develop a rollback plan that only works if you solve the series of riddles that are hidden in an undisclosed location.

  2. You have to be confident in the code you wrote and be ready to create a rollback that matches that.

  3. I have a 23-step plan in case anything happens.

Q: What would you rather do instead of pushing a deploy?

  1. Have lunch with my mother-in-law.

  2. Picking up dog poop at the National Dog Show.

  3. Being on American Ninja Warrior. That show really frightens me.

As we dove further into this interview, we saw the fear and doubt in the eyes of the interviewees. Why does deploying have to be so unpleasant?

Short answer: It doesn't.

Long answer: Lightstep’s new Service Health for DeploymentsService Health for Deployments feature is here to help. You can automatically see what impacted your service’s performance during and after a deployment — and surface why it happened.

Lightstep gives you the confidence to deploy every day of the week. If you want to see Lightstep in action, you can play in our SandboxSandbox.

Interested in joining our team? See our open positions herehere.

February 27, 2020
3 min read

Share this article

About the author

Lindsay Neeson

Lindsay Neeson

Read moreRead more

The origin of cloud native observability

Jason English | Jan 23, 2023

Almost every company that depends on digital capabilities is betting on cloud native development and observability. Jason English, Principal Analyst at Intellyx, looks at the origins of both and their growing role in operational efficiency.

Learn moreLearn more

Gain agility through observability

Heather Waters | Jan 19, 2023

As we navigate geopolitical challenges, macroeconomic headwinds, and the post-pandemic comedown, there is pressure to drive transformation, reduce costs, and be more efficient. See how observability can help you rise to the challenge and be more agile.

Learn moreLearn more

Developing a culture of observability

Doug Odegaard | Jan 4, 2023

Businesses must deliver remarkable customer experiences, release reliable products fast, and reduce costs to achieve consistent growth. See how observability can help.

Learn moreLearn more

Lightstep sounds like a lovely idea

Monitoring and observability for the world’s most reliable systems