Skip to content
Blog

Technical perspectives from the field

Reflections from those who build systems that cannot fail

  • Real-world experience
  • Practical approach
  • Leadership and technology

Knowledge we build together

Ideas and lessons from the Hábil team

Explore articles
Quality and testing

Beyond the happy path: how to design the test scenarios that actually find errors

Which test scenarios add value, which are almost always forgotten, and a step-by-step method to find them: limits, states, time, retries, permissions and more.

Technical teams

· 16 min

Frontend

The structure of a project (7): the button that moved on two screens

A React screen with TypeScript and Vite, sliced by feature: where each file lives, what ESLint stops and what we measured on the template.

Technical teams

· 21 min

AI

Reading documents with AI: from the ID and the bank statement to the customer file, without typing by hand

How to automate document capture with AI to read IDs, proofs of address and bank statements: confidence per field, review and control.

Leadership

· 8 min

AI

Before AI, your data: what has to be ready for a model to be useful to you

How to prepare your data for artificial intelligence: five questions on source, quality, freshness and use, before you choose the tool.

Leadership

· 10 min

Architecture and backend

The structure of a project (6): the kitchen that's set up the night before

The same orders API, from Spring Boot to Quarkus: what changes in each package, measured startup time and memory, and what a startup number doesn't tell you.

Technical teams

· 19 min

Architecture and backend

The structure of a project (5): the layer that did nothing

Four layers and a facade that just passes the call on. What goes in each package of a Spring Boot API, when to skip the facade, and a template that checks it.

Technical teams

· 16 min

Architecture and backend

The structure of a project (4): the import that compiles and doesn't start

Your tsconfig.json alias compiles and Node won't start, because Node never reads that file. What tsconfig decides, what package.json decides, and a template.

Technical teams

· 18 min

Integration and APIs

The ERP went down on Saturday: what happens to the sales that came in meanwhile

When the ERP goes down, the store keeps selling. Five pieces to avoid losing or duplicating sales, and how to catch up when it comes back.

Leadership

· 13 min

AI

What decisions can AI make on its own?

It is not decided by the technology, but by the impact and whether it can be undone. When AI acts on its own, when it proposes and when a person decides.

Leadership

· 10 min

Data

What to define before buying BI

If two areas calculate the same figure differently, a BI tool only displays the disagreement. What to write before choosing one: formula, source and owner.

Leadership

· 10 min

Data

Before you move a piece of data, name its owner

A data platform does not replace the agreement on who answers for each piece of data. Owner, agreement and quality rules, before loading.

Leadership

· 10 min

AI

The AI pilot went well in the demo. How do I know it works before scaling it?

A demo does not tell you whether an AI pilot works. How to measure it against today's work, with real cases and an exit criterion set before you start.

Leadership

· 11 min

Integration and APIs

Connecting SAP without touching it: how to integrate your store, your bank and your partners without leaving custom developments in the way

How to connect your store, your bank and your partners to SAP through the doors SAP supports, without developments that get in the way of upgrades.

Leadership

· 12 min

Quality and testing

The test suite that ate the release: when raising the time limit hides the cause

Five weeks of reasonable patches and a stalled release: why raising the build limit does not remove the cause, and three rules your committee should demand.

Leadership

· 16 min

AI

APIs an agent can use with control: a purchase from start to finish

A purchase designed for AI agents: propose and execute apart, approval outside the model, idempotency, RFC 9457 and a prompt-injection test.

Technical teams

· 18 min

Architecture and backend

The structure of a project (1): the standard that wasn't a standard

The most popular Go structure repo says it is not official. Go's guide asks for cmd/ and internal/, and the tool enforces only internal/. With a template.

Technical teams

· 15 min

Architecture and backend

The structure of a project (2): passes on my machine, fails when installed

Your tests pass and your package breaks for whoever installs it. PyPA's guide asks for src/, but an editable install also reads your folder. With a template.

Technical teams

· 14 min

Architecture and backend

The structure of a project (3): the function nobody could test

All your logic in main.rs and your tests/ can't import it, not even with pub. What goes in lib.rs, what stays private, and a template that checks it.

Technical teams

· 17 min

Architecture and backend

Your company grew and is starting to lose control: four growth crises, with Mexican cases

The four crises a growing company can face, with cases from Bimbo and Cemex, signals to locate yours and what your systems must withstand.

Leadership

· 18 min

Methodology and teams

Your new system already works and nobody uses it: the eight steps of change, with Mexican cases

Mexico's e-invoice 4.0, Cemex Go and Bimbo's ERP through Kotter's eight steps of change. Thresholds, costly mistakes and a decision sheet for your committee.

Leadership

· 18 min

Payments

The five stages of a small business and what its back office has to withstand

Existence, survival, success, take-off and maturity: how to tell your company's stage, what breaks in its back office at each one and what to decide first.

Leadership

· 20 min

Payments

Your dashboard says everything is fine. Where do those numbers come from?

The balanced scorecard fails when its indicators are put together by hand. A diagnostic with thresholds, VAT at risk and the sheet for your committee.

Leadership

· 19 min

Methodology and teams

Everything is green until it blows up: why your team doesn't report red flags in time

Edmondson's psychological safety, with a measurement made in Mexico: why red flags arrive late, how to spot it and what to decide before a project blows up.

Leadership

· 18 min

Architecture and backend

Which link should I invest in first in technology? Porter's value chain, read in days and pesos

Porter's value chain read in days and pesos: where money stalls between purchasing, operations, sales and collections, with Genomma Lab from 2016 to 2023.

Leadership

· 20 min

Products and pricing

Your competition is not who you think it is: it is what your customer hires instead of you

Your customers hire your product to do a job. A diagnostic with thresholds, the Volaris case and a job sheet for your next leadership meeting.

Leadership

· 19 min

Architecture and backend

Not all your systems are worth the same: how much to invest in each one, depending on how critical it is

Diagnostic with thresholds: which systems are support, factory, transition or strategic, what changes in budget and governance, and an inventory for your board.

Leadership

· 20 min

Cloud and operations

Five backup techniques and none of them reliable: the night GitLab deleted its database

In 2017 an accidental deletion at GitLab.com revealed its backups did not work. The real story, what changed and how to know if yours really restore.

Leadership

· 15 min

Integration and APIs

Target Canada: empty shelves, full warehouses and data nobody asked to get right

Target opened 133 stores in Canada and closed within two years: empty shelves, full warehouses. What it teaches about data and the trail of each order.

Leadership

· 16 min

Methodology and teams

HealthCare.gov: what saved the site was not just adding more people

On October 1, 2013, only six people managed to submit an application and choose a plan. How an integrated response recovered HealthCare.gov in two months.

Leadership

· 17 min

Cloud and operations

78 minutes of error, five days of outage: what CrowdStrike and Delta teach about recovering

On July 19, 2024 an update took down 8.5 million machines. Other airlines were back sooner; Delta took five days. What it teaches your company.

Leadership

· 16 min

Cloud and operations

Knight Capital: 45 minutes, one server nobody updated and more than $460 million

In 2012, an incomplete deployment cost Knight Capital more than $460 million in 45 minutes. What a director can learn and what to ask.

Leadership

· 16 min

Security

MGM case: identity and access governance

MGM reported disruptions and an estimated EBITDAR impact; three access governance questions

Leadership

· 9 min

Architecture and backend

TSB, April 2018: the weekend a bank could not go back

In 2018, TSB moved most of its operation to a new platform in one weekend, with no viable rollback. What failed and what your committee should ask.

Leadership

· 16 min

AI

The AI agent is already at the checkout door: what happens in your systems when the buyer is a machine

AI agents already prepare purchases up to payment. Identity, authorization, disputes, CFDI and fraud: what your company must solve before they arrive.

Leadership

· 11 min

Payments

Payments at Pix speed: the stress test for your close

Instant collection speeds up funds; reconciling, closing and handling claims needs a new pace. Brazil's experience with Pix and what to prepare in Mexico.

Leadership

· 11 min

Products and pricing

Insurance in a partner's app: what to decide to open the channel with operational and regulatory control

Selling insurance in a partner's app means quoting, issuing, collecting and handling claims with an audit trail. What the law asks and what to decide.

Leadership

· 12 min

Products and pricing

From quote to collection: how to reduce dependence on long IT projects

How to govern product and rate changes with traceability, without displacing the applicable actuarial, legal and regulatory reviews.

Leadership

· 9 min

AI

AI customer service with a reviewable trail, not a pretty demo

Why an AI assistant stays a demo, what it needs to resolve with control and what the new personal data law demands of you. Five questions.

Leadership

· 13 min

AI

Shadow AI: if your teams already use AI, where does your data end up?

AI may be entering your company outside approved tools. What the studies say and how to evaluate an alternative with control.

Leadership

· 10 min

Architecture and backend

Modernizing core systems: the case for the committee, not the technical guide

What a committee should ask for before authorizing the modernization of a core system: operational exposure, rollback conditions and business milestones.

Leadership

· 11 min

AI

Your best salesperson has years of answers in their WhatsApp: RAG or fine-tuning?

Leadership wants to "train an AI on the chats" of the top salesperson. What RAG and fine-tuning are, which to start with and what to watch.

Leadership

· 11 min

Integration and APIs

HTTP status codes in a business API: what to return when someone looks up a contact, and what a wrong answer costs

When to return 200, 404, 400, 422, 409, 429 or 503 on a contact lookup, and what a wrong choice costs: retries, misleading dashboards and agents.

Technical teams

· 20 min

Payments

Why bank reconciliation does not add up at a Mexican company

Why bank reconciliation does not add up in Mexico: deposits against CFDI, payment complements, installments, credit notes and fees. What automation changes.

Leadership

· 19 min

Architecture and backend

Build, configure or buy: how a committee decides with clear criteria

Three paths to a new system, when each makes sense and what to ask before signing custom development: ownership, licenses, acceptance and handover.

Leadership

· 18 min

Integration and APIs

The order is not lost; the trail is

Why nobody in omnichannel commerce can quickly answer "where is this order?", what not knowing costs and what leadership should demand.

Leadership

· 16 min

Cloud and operations

The error on the first change of the day is almost never bad luck

An error that shows up now and then, on the first change of the day, is often a sleeping connection. How to prove it, fix it and avoid broken data.

Leadership

· 14 min

Frontend

One app or two? What AI changed in your mobile channel decision

Airbnb left React Native and Shopify went back to native: different contexts, similar result. Five criteria to decide on your app and what AI changed.

Leadership

· 13 min

Payments

Electronic invoicing end to end: one sale, three or four CFDIs and what changed in 2026

A credit sale with two payments and a return generates three or four CFDIs. The full cycle, the costly mistakes and what changed in 2026.

Leadership

· 9 min

Methodology and teams

Your software project fails for the same reasons a surprise party does

Tasks without an owner, red flags seen too late and issues nobody decides. Six decisions to hit your date and six questions to ask your vendor.

Leadership

· 9 min

Payments

Payment complement and cancellations: where the SAT finds the mismatch

The payment complement and CFDI cancellation have deadlines and recipient acceptance. Where collection, invoice and complement fail to match.

Leadership

· 10 min

Payments

Digital payments: what the committee report really demands of your reconciliation

The digital payments law binds no one yet and has no penalties of its own. What the report says and what is worth reviewing in your reconciliation.

Leadership

· 10 min

Integration and APIs

Online or asynchronous? How to choose how to integrate your systems

A decision tree for leadership: online or asynchronous first; then REST or gRPC, or queue, callback or event, so the core does not go down.

Leadership

· 11 min

Integration and APIs

REST or gRPC: when to use each, and why your core speaks neither

REST at the edge, gRPC at the core and an adapter for legacy: criteria, gRPC-Web, transcoding, tools, Spring Boot, Quarkus and Protobuf.

Technical teams

· 15 min

AI

APIs ready for AI agents: what your system needs so an agent can use it with control

Errors that teach, retries without duplicates, machine identity and visible limits: what an API needs so an AI agent can use it with control.

Technical teams

· 15 min

Architecture and backend

Native Java: when to use it, when not to, and what suits cloud native

GraalVM, Quarkus, Spring Boot, Java 25's startup cache and CRaC: what each option gains and costs, and which fits your service and your cloud.

Technical teams

· 20 min

Security

API security for the CTO: identity, gateway and tokens, without trusting blindly

When to revalidate the token behind the gateway, how APIs call each other, introspection or local validation, logout and how long a token should last.

Technical teams

· 17 min

Cloud and operations

Telemetry without the mystery: Prometheus, Loki, Tempo and Grafana, and why OpenTelemetry

What Prometheus, Loki, Tempo and Grafana answer, how metrics, traces and logs connect, and when to read logs with an agent or instrument with OpenTelemetry.

Technical teams

· 17 min

Quality and testing

Tests that actually catch errors: beyond coverage and a green quality gate

High coverage and a green quality gate aren't enough: test types, doubles that hide failures, mutation, AI and documentation for tests that catch errors.

Technical teams

· 16 min

Methodology and teams

Waterfall or Scrum: how to choose the way to run your project

When to move in stages with deliverables (V-model) and when in sprints with Scrum, what each asks of your team, and how to combine them.

Leadership

· 7 min

Frontend

Is your web application no longer enough?

When a desktop application makes sense to connect printers, readers, scales or local files on Windows, macOS and Linux, without replacing your web system.

Leadership

· 4 min

Frontend

What a professional frontend needs and how to structure it

Components, design system, testing, accessibility, CI/CD, SEO, performance and security: what a CTO should demand of a frontend before launch.

Technical teams

· 11 min

Frontend

Frontend paradigms: how to choose your web application's architecture

SPA, server, static, islands, microfrontends, desktop and mobile: when each frontend architecture fits your business and how to migrate without rewriting.

Technical teams

· 11 min

Cloud and operations

Release without fear on your own infrastructure

What Mexican regulation really asks of infrastructure, what comes insecure out of the box in your own Kubernetes, and how to build a path to production your auditor can review.

Technical teams

· 6 min

Frontend

How to structure a Storybook that works as a contract

Storybook is not a gallery of buttons: it is the behavior reference between design, development and QA. How to organize it by layers, what to document in each story and what to review before publishing.

Technical teams

· 6 min

AI

How to build an MCP for your industry

What an MCP is, which controls it needs in a regulated industry, and how it applies to banking, insurance, ERP-run companies and retail. A guide for executives, with sources.

Technical teams

· 8 min

AI

Agentforce and AI Agents in Mexico: a real signal for banking, insurance and enterprise

The conversation is no longer whether generative AI can answer questions, but whether an organization is ready to operate with agents that understand context, data and real processes. For us, that was the most important message from Salesforce Agentforce World Tour Mexico 2026.

Leadership

· 7 min

Methodology and teams

Why Mexico Is a Solid Nearshore Option for Critical Software

Nearshore for critical software is not the same as generic outsourcing. The difference is not in the hourly rate — it is in domain knowledge density, real-time communication capability and regulatory alignment.

Leadership

· 7 min

Security

SSO with SAML 2.0 in Financial Services: Enterprise Implementation

Credential fragmentation is a security risk in financial services that SSO with SAML 2.0 helps reduce — but correct implementation has more nuances than tutorials show.

Technical teams

· 10 min

Integration and APIs

Kafka in Insurance Systems: Architecture for High Concurrency

Insurers process simultaneous transactions: enrollments, payments, claims. Kafka is not a trend — it is a pattern that decouples those flows; traceability and consistency are designed with it, they do not come on their own.

Technical teams

· 8 min

Courses

  • Web Fundamentals Course — from zero to a dashboard anyone can use

    Web and frontend

    From zero to a page anyone can use

    Plain HTML, CSS and JavaScript, no libraries: it teaches the web from the inside, before any framework.

    Beginner12 lessons
  • Python course — from zero to a program that checks many services at once

    Languages and backend

    For people who have never programmed

    It assumes nothing: it teaches programming by understanding why each line works, up to a complete program with tests.

    Beginner12 lessons
  • Go course — from zero to writing a good program

    Languages and backend

    From zero to your first complete program

    It doesn't teach syntax: it teaches you to see the errors you can't see.

    Intermediate8 lessons
  • Rust course — the second one, after Go

    Languages and backend

    The second step, after Go

    It teaches what Rust does differently from Go: who owns each piece of data and which errors the compiler catches before running.

    Intermediate9 lessons

    Before this course: Go

  • Vault from scratch

    Containers and cloud

    For people who already use the terminal and Docker

    It teaches keeping passwords and keys out of the code with Vault and OpenBao, its open-source fork: secrets with permissions, encryption without holding the key, and credentials that expire on their own.

    Intermediate4 lessons

    Before this course: The Terminal from Scratch and Docker

  • HTTP course — errors that teach: status codes and Problem Details

    Languages and backend

    For people who have already written an API

    It teaches choosing the right HTTP status code, returning machine-readable errors with Problem Details, and versioning an API with advance notice.

    Intermediate9 lessons
  • Not One Order Lost

    Practice: Languages and backend

    For anyone who already uses the terminal and Git, reads JSON and knows basic SQL

    An open, free systems integration practice: every order from a store reaches a REST API, an ERP and an EDI partner without being lost or duplicated.

    Intermediate33 lessons

    Before this course: The Terminal from Scratch

  • Docker course — package a service and operate it in real-world scenarios

    Containers and cloud

    For people who have already built a service

    It teaches turning a service into a small image that runs without privileges, with health checks and limits, and bringing it all up with Compose.

    Intermediate11 lessons

    Before this course: The Terminal from Scratch

  • Kubernetes with kind course — deploy, configure, scale and secure a service on your own machine

    Containers and cloud

    The next step, after Docker

    It teaches deploying a service on a local kind cluster: configuring, monitoring, exposing, securing and scaling it, measuring what fails and for how long.

    Intermediate11 lessons

    Before this course: Docker

  • Your store in your pocket: a native app for Android and iOS, from a ready setup to a sign-in that works on a real phone

    Mobile

    For anyone who already codes and wants to build a first mobile app

    Build a store's app in Kotlin and Compose, with Google or Microsoft sign-in and tests at every step. AI helps; you review.

    Intermediate10 lessons

    Before this course: The Terminal from Scratch

  • The Terminal from Scratch: working in Linux without a screen and without fear, in a practice container

    Containers and cloud

    For anyone who codes and has never worked in a terminal

    Practice happens in an Ubuntu container that starts with one command and checks your work. AI explains; commands that delete are typed by hand.

    Beginner3 lessons