Dorian Chávez
Co-founder · Chief Executive Officer
Co-founder · Meet Inés Rodríguez
He has been programming professionally since 2000 and co-founded Hábil in 2006. Since then he has designed and run systems that cannot fail for banking, insurance and enterprises: integration with core systems and ERPs, payments and identity. He writes about architecture, integration and software projects, and in his newsletter «En construcción» he shares the practical skills that university does not teach.

Blog
- What decisions can AI make on its own?
- What to define before buying BI
- Before you move a piece of data, name its owner
- The AI pilot went well in the demo. How do I know it works before scaling it?
- Connecting SAP without touching it: how to integrate your store, your bank and your partners without leaving custom developments in the way
- The ERP went down on Saturday: what happens to the sales that came in meanwhile
- The test suite that ate the release: when raising the time limit hides the cause
- APIs an agent can use with control: a purchase from start to finish
- The structure of a project (1): the standard that wasn't a standard
- The structure of a project (2): passes on my machine, fails when installed
- The structure of a project (3): the function nobody could test
- Your company grew and is starting to lose control: four growth crises, with Mexican cases
- Your new system already works and nobody uses it: the eight steps of change, with Mexican cases
- The five stages of a small business and what its back office has to withstand
- Your dashboard says everything is fine. Where do those numbers come from?
- Everything is green until it blows up: why your team doesn't report red flags in time
- Which link should I invest in first in technology? Porter's value chain, read in days and pesos
- Your competition is not who you think it is: it is what your customer hires instead of you
- Not all your systems are worth the same: how much to invest in each one, depending on how critical it is
- Five backup techniques and none of them reliable: the night GitLab deleted its database
- Target Canada: empty shelves, full warehouses and data nobody asked to get right
- HealthCare.gov: what saved the site was not just adding more people
- 78 minutes of error, five days of outage: what CrowdStrike and Delta teach about recovering
- Knight Capital: 45 minutes, one server nobody updated and more than $460 million
- MGM case: identity and access governance
- TSB, April 2018: the weekend a bank could not go back
- The AI agent is already at the checkout door: what happens in your systems when the buyer is a machine
- Payments at Pix speed: the stress test for your close
- Insurance in a partner's app: what to decide to open the channel with operational and regulatory control
- From quote to collection: how to reduce dependence on long IT projects
- AI customer service with a reviewable trail, not a pretty demo
- Shadow AI: if your teams already use AI, where does your data end up?
- Modernizing core systems: the case for the committee, not the technical guide
- Your best salesperson has years of answers in their WhatsApp: RAG or fine-tuning?
- HTTP status codes in a business API: what to return when someone looks up a contact, and what a wrong answer costs
- Why bank reconciliation does not add up at a Mexican company
- Build, configure or buy: how a committee decides with clear criteria
- The order is not lost; the trail is
- The error on the first change of the day is almost never bad luck
- One app or two? What AI changed in your mobile channel decision
- Electronic invoicing end to end: one sale, three or four CFDIs and what changed in 2026
- Your software project fails for the same reasons a surprise party does
- Payment complement and cancellations: where the SAT finds the mismatch
- Digital payments: what the committee report really demands of your reconciliation
- Online or asynchronous? How to choose how to integrate your systems
- REST or gRPC: when to use each, and why your core speaks neither
- APIs ready for AI agents: what your system needs so an agent can use it with control
- Native Java: when to use it, when not to, and what suits cloud native
- API security for the CTO: identity, gateway and tokens, without trusting blindly
- Telemetry without the mystery: Prometheus, Loki, Tempo and Grafana, and why OpenTelemetry
- Tests that actually catch errors: beyond coverage and a green quality gate
- Waterfall or Scrum: how to choose the way to run your project
- Is your web application no longer enough?
- What a professional frontend needs and how to structure it
- Frontend paradigms: how to choose your web application's architecture
- Release without fear on your own infrastructure
- How to structure a Storybook that works as a contract
- How to build an MCP for your industry
- Agentforce and AI Agents in Mexico: a real signal for banking, insurance and enterprise
- Why Mexico Is a Solid Nearshore Option for Critical Software
- SSO with SAML 2.0 in Financial Services: Enterprise Implementation
- Kafka in Insurance Systems: Architecture for High Concurrency
Courses
- Web Fundamentals Course — from zero to a dashboard anyone can use
- Python course — from zero to a program that checks many services at once
- Go course — from zero to writing a good program
- Rust course — the second one, after Go
- TypeScript course — from zero to a program that holds up
- Java course — from modern Java to a program that checks many services at once
- Tensors from scratch
- Vault from scratch
- Errors that teach: HTTP status codes and Problem Details
- Docker course — package a service and operate it in real-world scenarios
- React course — from a one-component dashboard to an app that holds up
- Kubernetes with kind course — deploy, configure, scale and secure a service on your own machine