Insights

Ideas to build and operate better.

Guides, analysis and lessons on product, artificial intelligence, growth, communications and cloud.

Editorial themes

Software and SaaS development

Digital products that solve, scale and evolve.

AI, automation and data

AI systems for real-world processes.

Marketing, ecommerce and marketplaces

Demand, catalogue, partners and conversion.

Communications and customer care

Every conversation in the right channel.

Cloud, infrastructure and operations

Available, observable and ready services.

results

8 results

Diagram of an application reusing temporarily stored data between a user and a database

Desarrollo de software y SaaS6 min

When to Use a Cache in an Application: How to Decide Without Adding Unnecessary Complexity

A cache can reduce latency and load, but it also introduces stale data and operational overhead. Learn when it pays off, what to store, and how to measure the results.

↗

Diagram of an application distributing data validation across the interface, server, and an asynchronous process.

Desarrollo de software y SaaS7 min

Where to Validate Data in an Application: The Interface, Server, or an Asynchronous Process

Decide where to validate each piece of data based on user experience, authority, and the cost of errors. A practical framework for combining the interface, server, and asynchronous processes.

↗

Digital product interface with options to undo, restore, or correct an action

Estrategia y evolución de producto digital7 min

How to Choose Which Actions Users Should Be Able to Undo in an Application

A practical framework for deciding when to let users undo, restore, or correct actions based on their impact, recovery costs, and effects on connected systems.

↗

Diagram of a retry policy that classifies failures and routes expired messages to discard, manual review, or compensation.

Operación, observabilidad y mejora continua7 min

How Long to Retry Failed Messages: A Policy That Protects Operations

Set retry windows for failed messages according to their cause, urgency, and validity. A clear policy reduces duplicates, delays, and unnecessary manual reviews.

↗

Diagram showing an API distributing usage quotas among different clients and operations

Integraciones, APIs y sistemas conectados7 min

API Rate Limits: How to Set Quotas Without Blocking Legitimate Integrations

Set API quotas according to the consumer, operation, and available capacity. Learn how to respond when limits are exceeded and refine policies using metrics.

↗

Diagram of an API using an idempotency key to recognize retries and prevent an operation from being duplicated.

Integraciones, APIs y sistemas conectados7 min

Idempotency in APIs: How to Prevent Duplicates Without Hiding Errors

An idempotency key lets you retry sensitive operations without repeating their effects. Learn how to define its scope, handle concurrency, and respond to errors.

↗

Team reviewing a spreadsheet and a digital operational workflow to decide whether to move to a system.

Operación, observabilidad y mejora continua8 min

When a Spreadsheet Stops Being Enough and It’s Time to Move to a System

A spreadsheet can support useful processes for years. This framework helps identify when its flexibility becomes an operational risk.

↗

Diagram of web application load testing with user journeys

Software y SaaS6 min

Load testing based on real user journeys: find the limit before users do

Design web application load tests with real user journeys, verifiable thresholds, and useful evidence to make decisions before a usage spike.

↗