Where the eye came from
The Seed
Before I had the vocabulary for it, I saw data as shapes. Entities, relationships, the way information wants to organize itself — it arrived as a picture, not a list. It was a knack, not yet a discipline.
The knack became load-bearing in 2000.
Two days after I landed in this country, with about two years of experience to my name, the startup I had joined changed its stack overnight — ASP one day, Java the next. I was there as a data architect, and suddenly I was expected to help build something close to Amazon, in a language I did not know, with no fallback and no time to be afraid of it.
So I reached for the one thing I could see clearly. I could not yet write the Java, but I could see the data — the entities, the relationships, the shape the system needed underneath whatever language sat on top. I anchored the build on the part I understood and learned the rest in the gaps: late, fast, under pressure that did not care whether I was ready.
It worked.
And working under that kind of stress does something a calmer education never does — it fuses a natural instinct to your hands. The eye stopped being a knack I happened to have and became a craft I trusted: the ground I stood on, the first thing I reached for in every problem after.
When you survive on a skill, you do not just keep it. You believe in it.
That belief became the foundation everything else got built on. It was also — though it would take me years and one uncomfortable whiteboard to find out — the exact thing that would one day have to change.
But that comes later. This part of the story is just the seed: a way of seeing I was born with, and the pressure that turned it into something I could build on.