About
Before writing my first system, I spent eight years and eight months on the shop floor. Today I work in engineering building systems that, among other things, monitor an operation like the one I worked in. That experience still shapes the way I think about software, problems and decisions.
The path so far
Industrial operations → Help desk → Development → Engineering
It was eight years and eight months in production, nine months in support and then the move to development. It was not a very linear path, but each stage ended up bringing a different perspective to the work I do today.
My experience in operations taught me to look at a system not only for what it needs to do, but for who will depend on it when something goes wrong. Today that view shows up mainly in the systems that cut across different areas of the business.
The whole story is in Career path.
What I don’t know
My experience is stronger in enterprise systems, complex integrations and business rules than in very high throughput or low latency platforms.
I have not worked with .NET in extreme concurrency scenarios, and I do not yet have production experience with gRPC or Orleans.
I prefer to make that distinction explicit. In the Technology index, each technology shows what I have already applied in production, what I know and what I am still developing.