ADITHIYA

The problems I like are the ones nobody has framed yet. My first job on a vague one is to give it a shape other people can argue with, then to kill the versions that do not survive the evidence. Two of my own ideas died that way before I built anything.

I wrote control and instrumentation specs for more than two years before I ever wrote a product requirement, then spent a year reading support tickets to find what customers meant rather than what they typed. Having sat on both sides, I translate before a misunderstanding hardens.

In a power plant a wrong assumption does not surface at the design review, it surfaces at commissioning. Over two years of that taught me to understand how a system behaves before changing any part of it, and the habit came with me when I changed careers.

Every team has work that only lives in one person's head: the corrections, the reconciliation, the checks nobody wrote down. At CIRRANTIC that work is tariff and charging data, and the job is to get it specced into modules before the person holding it moves on.