Artículos sobre productos AI-native, design systems, ingeniería web, economía SaaS e infraestructura moderna. Nuevas publicaciones cada semana, con fuentes.
Siete errores que vemos repetirse en apps Claude en producción. Algunos te cuestan tokens, algunos te cuestan dinero, uno o dos te pueden costar la empresa. Cada uno tiene una solución simple.
Leer el artículoPágina 4 de 5
Article, BreadcrumbList, Organization, Person, WebSite, FAQPage, HowTo. Which schema types still earn rich results in 2026, and which are pure AI citation fuel.
Side-by-side on web SaaS billing: subscriptions, proration, entitlements, fees. The decision broken down by stack and revenue stage.
Cascade layers, container queries, and color functions are now production defaults. What modern CSS in 2026 actually delivers and where it falls short.
A practical playbook for governing a design system across many consumer projects: contribution model, versioning, codemods, and adoption tracking.
Seven Claude Code workflow patterns we run daily to ship production code: plan mode, CLAUDE.md, hooks, subagents, parallel sessions, slash commands, MCP.
llms.txt is a markdown index that hands LLMs a curated map of your site. Here is what to put in it and whether it actually moves AI citations.
How to ship usage-based billing in a SaaS without breaking trust: meter design, idempotency, hybrid plans, and the platform choice.
We have shipped both Next.js and Astro this year. For SaaS specifically, Next.js stays our default. Here is the honest tradeoff in 2026.
Buttons multiply, tokens drift, components fork. The 10 design system mistakes that quietly turn a product into a parts bin, and the fixes.
Self-hosting an MCP server costs $50k to $150k per integration per year. Buying solves 80% of cases, building wins the rest. Here is how to decide.
The first 30% of an article drives 44% of AI citations. A practical guide to an opener ChatGPT, Claude and Perplexity quote cleanly.
Most early-stage SaaS teams pay 20-30% more than they should because work lives across 10+ vendors. Here is the case for one team and one invoice.
Artículos para diseñadores e ingenieros que hacen el trabajo.
Artículos para founders y equipos que eligen un partner.