AvailableTaking on architecture and development work.
The hard part is understanding how a business runs and modeling it right. Two years in electronic invoicing, a marketplace in production, and a repair-shop system on the way.
They fail when the model doesn’t look like the operation. When a quote and an order live in the same table. When transport is a cost hidden inside the product. When yesterday’s price changes today’s invoice.
No refactor or new library fixes that kind of mistake. You avoid it before writing code: sitting with the people who run the operation, naming every thing, and drawing boundaries that hold.
That’s what I do. The rest (frontend, backend, infrastructure) follows from it, and I do that too.
Five steps. The order matters more than the tools.
I talk to whoever runs the operation and learn what an order means to them, not to the ORM.
What belongs to whom. A quote knows nothing about invoices; an order does.
Frontend, backend and data on the same model, with no translation halfway.
Boring infrastructure: repeatable deploys, backups, and nothing that depends on my memory.
The operation changes and the model follows. I build for change, not speculation.
Two systems of my own. One is in production; the other hasn’t left the shop yet.
Sunber looked like an ecommerce. It wasn’t.
Selling a panel is simple. Selling something that may need installation, a site visit, transport, coverage by municipality, a quote and then an invoice changes the problem quite a bit.
Much of the work has been turning that operation into pieces that make sense inside the system.
Software for repair shops that stays out of the way while you work.
The idea came from something simple: record what was done to a car and charge for it without turning every service into an admin session.
I’m designing it around compact information and fast actions. It has to work as well at a desk as standing next to the car with greasy hands.
Sedan 2.0 · A7B-318
In progressNo line items yet. Add a quick charge.
Quick charge
Total
Short, dated, and not padded.
2018 – 2023
Benemérita Universidad Autónoma de Puebla
The theory. And in the last two years, real servers too, in the faculty lab.
2022 – 2023
Ontological Engineering Lab, FCC BUAP
Stood up and maintained Ubuntu servers, backed up machines, and built a web app that loads ontologies and draws their graph and taxonomy.
2023 – 2025
Egrid · electronic invoicing
Applications on .NET Core, Express, React and MongoDB inside the CFDI domain: issuing, fiscal stamping, and the supplements each line of business requires. That’s where I learned the tax authority doesn’t forgive a sloppy model.
Today
Sunber · Valtro
Sunber in production. Valtro in development.
What I build and operate with, by layer. I’m not married to any tool; I am to each one having a reason to be there.
Tell me how it works and we’ll figure out what system it needs. Two addresses, depending on the subject; I answer both.
