On this website we use cookies that are strictly necessary to make our website function correctly, as well as optional – analytics, performance and/or marketing - cookies which help us improve our website by collecting and reporting information on how the website is used, as well as help us to reach out to you with information about our organization or offer. If you do not wish to accept optional cookies when visiting our website, you may change the settings in the Cookie Settings. For more information go to Cookie Settings.

Skip to content

Intelligence officers get no champagne rooms

Nov 17, 2015 - 2 minutes read

Objectivity Blog 416 306
Piotr Torończak
Recently a Software Engineer in Support. SQL Server practitioner and former DBA. In Objectivity Blog I write about a Support life and problem solving techniques. Privately a guy with no passion, but many interests. A hiker, an MTB rider, a reader and jazz music aficionado.
See all Piotr's posts
Dataops Ebook 416X300

Share

The myth says that unfulfilled developers end up in support. You’d agree to that, wouldn’t you?

We don’t like it, but we don’t care much about it either. And apart from that, you don’t tend to hear much else about us, do you?

Well, you will – when a major failure occurs and you hear those rumors about a spectacular fine the company had to pay to rectify it (deal with it developers – after a while we have way cooler stories to tell! If we can… both we, and the CIA, have confidentiality agreements inked on our foreheads.)

As we’re spies support analysts, quite often the effects of our job are not visible.
SUPPORT: “Have your major systems worked smoothly for the past month?”
END USER: “Well, isn’t it supposed to?”
SUPPORT: “Did you notice that some data arrived a bit later than usual because of a major ETL failure?”
END USER: “What are you talking about?”
Exactly. Of course you didn’t know. Why? Because a bunch of rocket-science-level engineers spent half the night restoring it.

Working in support requires a specific mind-set. One similar to a surgeon’s. Or an intelligence officer. Our job requires both technical and soft skills. It requires chess master abilities that allow us to foresee what will happen if a certain operation is restarted in a production environment (mistakes are hardly forgiven – not by your boss, but by the system you work on. You can worry about your boss later). We take responsibility for our actions. Show complete transparency. It is as simple as having a fellow colleague behind your back when you run the simplest script (not because you’re an idiot, because small mistakes cause big failures and things are so delicate in our world). Being willing to pick up a phone call overnight and carry your laptop on your back while shopping with your wife. Taking the time to go step by step through that over engineered piece of code created by Mr. Nobody and figuring out what failed (or what may fail).

Welcome to the world of support, where what is delivered is so obvious and unnoticeable that your client does not even know you exist.

PT

PS: But we party hard. Have you noticed me limping around with crutches for the last few weeks? A bone fracture. After a support team party.

Dataops Ebook 416X300
Piotr Torończak
Recently a Software Engineer in Support. SQL Server practitioner and former DBA. In Objectivity Blog I write about a Support life and problem solving techniques. Privately a guy with no passion, but many interests. A hiker, an MTB rider, a reader and jazz music aficionado.
See all Piotr's posts

Contact

Start your project with Objectivity

CTA Pattern - Contact - Middle