DEV Community

Cover image for In case of doubt, ask for clarification
Dan Lebrero
Dan Lebrero

Posted on • Originally published at danlebrero.com on

6 1

In case of doubt, ask for clarification

As an example of what not to do, here I am earlier this year with a teammate, doing some Ops work (Unilog is a backend service, akvoflow-87 is a tenant of another backend service that depends on the Unilog):

Not so clear communication

I hope it is not obvious to you, as it was not for me, but what my teammate was actually asking was:

Can I completely decommission Unilog forever?

But what I understood was:

Can I stop Unilog for a minute?

Result: a massive slowdown of the whole system for a few hours.

We have been talking about decommissioning that Unilog service the whole week, so it even crossed my mind that maybe it was related to it, I thought he surely cannot be asking about decommissioning it.

Silly me for not asking.

Heroku

This site is built on Heroku

Join the ranks of developers at Salesforce, Airbase, DEV, and more who deploy their mission critical applications on Heroku. Sign up today and launch your first app!

Get Started

Top comments (0)

A Workflow Copilot. Tailored to You.

Pieces.app image

Our desktop app, with its intelligent copilot, streamlines coding by generating snippets, extracting code from screenshots, and accelerating problem-solving.

Read the docs