Pablo Mickael Quevedo

Backend

APIs, workers and processing in .NET, from the contract to what runs in production

Architecture

technical decisions in systems being born and, more often, in systems that already exist

Integrations

getting systems that were not built to talk to each other to talk, without losing an order along the way

Data

domain modeling, heavy queries, and the database that was already there before me

Applied AI

agents inside the engineering process, and models inside the product

Five .NET libraries I wrote and maintain, solving the problems that come back in every service. It is the part of my work you can open and read from the inside.

See the packages → PMQ.NotificationsPMQ.ErrorHandlingPMQ.MediatorPMQ.DomainPMQ.Identity

Rules in data, not in code

what changes every week becomes a record, not a deploy request

Idempotency for whatever comes from outside

an integration that can be redelivered is an integration that does not duplicate orders

Offline as a requirement

in an office, a network outage is an incident; on the shop floor it is Tuesday

Saying what I don't know

each skill states where it ends, and that is worth more than the list of what I know

1. Industrial operations eight years and eight months assembling products on a production line
2. Help desk the way into technology, and the landscape seen by someone who depends on it
3. Development from features to whole services, backend and frontend
4. Engineering platform, architecture and the standards other teams consume

The whole story →