Category
Honest software development: code that lasts and stays with you.
El concepto de Agent OS pasó del slide al despliegue en 2025. Seis meses en producción dejan patrones visibles: qué arquitecturas funcionan, dónde se rompe el modelo y qué aporta frente a correr agentes sobre pila existente.
A year after GraphRAG left the lab, one statistic holds: it works where corporate information has dense relational structure, fails where there are only loose documents. Patterns, ingestion costs, and architectural decisions that have survived a year of real deployment.
The AI tool stack a developer uses in 2026 looks nothing like it did eighteen months ago. Agentic editors, review tools, terminal agents, and test assistants have settled into recognizable roles. A practical guide by category.
Twenty months after the initial announcement, Model Context Protocol went from curiosity to de-facto standard among agent clients and servers. What is available, which servers are worth it, which problems remain open, and how it compares to earlier protocol maps.
After the 2023-2024 hype cycle led by Apple Vision Pro, the 2025 valley of disillusionment, and the quiet but real consolidation of Meta Quest 3S and the WebXR stack, it is time to assess honestly where extended reality stands. What works, what has died, what is still alive.
WASI preview 3 llegó como estándar estable a finales de 2025 y ha tenido unos meses para demostrar si realmente desbloquea los casos que preview 2 se quedaba cortos. Recorrido honesto por adopciones reales, bibliotecas maduras y patrones que empiezan a funcionar en producción.
After two years watching every product invent its own interface for talking to an agent, by January 2026 a stable design consensus is emerging about which patterns work, which do not, and what the average user already expects. Time to write down what has settled.
Con 1.34 liberado en agosto de 2025 y el ciclo de 1.35 en su última fase de congelación de funciones, qué llegará estable, qué quedará en beta, qué nos interesa a quienes mantenemos clústeres pequeños o medianos y qué podemos ignorar sin culpa hasta el siguiente ciclo.
La integración de WebAssembly dentro de containerd como tiempo de ejecución alternativo ha madurado. Ya es posible desplegar cargas mixtas Linux y Wasm en el mismo clúster de Kubernetes con argumentos operativos sólidos. Cuándo compensa y cuándo no.
La obligación del EAA entró en vigor el 28 de junio de 2025. Seis meses después tenemos ya primeros expedientes sancionadores, criterios de enforcement y lecciones operativas para equipos que aún corren detrás del calendario. Lo que sí se audita y lo que todavía no.
gVisor interpone un kernel en espacio de usuario entre el contenedor y el anfitrión. Después de años en producción en Google y adopción creciente en plataformas serverless, merece una lectura honesta sobre cuándo compensa frente a microVMs y runtimes clásicos.
A caching proxy in front of a language model can cut the token bill significantly, but it introduces subtle risks if the design is not careful. Which cache types work in production, where the usual traps sit, and how to add them without degrading the experience.
Wolfi turned three as a public project and has become the base for Chainguard container images and much of the industry chasing clean software supply chains. A field-tested review of what it offers against Alpine and Debian slim.
Kata Containers has spent years promising VM-grade container isolation without giving up Docker ergonomics. With the 3.x series now mature under the OpenInfra Foundation, the technical story finally holds together and there is a clear niche where adopting it pays off.
Accessibility overlays were sold as a magic fix for WCAG and the European EAA directive in one step. In 2025 lawsuits against them have grown and disabled users are speaking out more critically than ever. A look at why they fail and what to do instead.
Model Context Protocol turns ten months old since Anthropic's announcement, and it is no longer just a proposal: hundreds of servers, cross-vendor implementations and a public registry now back it. A look at what has worked, what is still weak, and why 2025 marks the shift from curiosity to basic infrastructure.
Astro 5 has spent nine months in production and has settled into a place of its own in the JavaScript world. Its bet on typed content and friction-free mixed rendering puts it halfway between Next.js and the static-site generators. A time-tested assessment.
Distributed SQL databases have moved from promise to production reality. YugabyteDB and CockroachDB lead the segment from different angles. Choosing between them demands understanding what each design compromises and what horizontal scaling costs in practice.
Kafka 4.0 llegó en marzo con la promesa cumplida: el clúster se autoadministra sin ZooKeeper. Después de meses operando clústeres KRaft y de la migración obligada, qué cambia de verdad, dónde duelen las diferencias y qué hay que saber antes de migrar.
Qwik has spent two years promising apps that start instantly because, instead of hydrating, they resume execution serialized on the server. With the 1.x series settled and real cases published, this guide checks whether resumability is worth the learning curve and which products benefit most from that client-side JavaScript saving.
TypeScript 5.5 llegó con inferencia de predicados, tipos de expresiones regulares estrictos y mejoras de declaraciones aisladas. Un año de uso real para separar lo que cambia el código diario de lo que es novedad cosmética, y cuándo conviene actualizar.
Open table formats over data lakes have moved from curiosity to backbone of many analytics architectures. Delta Lake 4.0 and Apache Iceberg 1.9 are the two with the most weight in 2025. We review where each one stands and which criteria make sense when choosing between them.
HTMX has carved out a niche in small and mid-sized web applications with a clear proposal: less JavaScript, more server. With version 2.0 stable for a year now, it is time to review which enterprise applications benefit and which still need a classic client-side framework.
Polars lleva dos años pidiendo relevo a pandas. Con Polars 1.x estable y una comunidad creciente, toca revisar dónde de verdad compensa migrar, dónde pandas sigue ganando y cómo convivir entre ambos sin pagar dos veces.
A year after chat stopped being the only acceptable way to talk to an agent, UI patterns built specifically for agent tasks are emerging. I go through the ones starting to stick and the ones that are just cycle fashion.
Valkey 8.1 salió el 31 de marzo y marca el momento en que la alternativa comunitaria de Redis deja de ser experimento. Cuenta una migración real: qué cambió, qué se mantuvo igual, y dónde hubo sobresaltos.
Rust Edition 2024 became stable on February 20, 2025 alongside Rust 1.85. Seven weeks later, the changes that actually matter for daily work are three: more granular variable capture in closures and Return Position Impl Trait, an expanded prelude with Future and AsyncFn, and unsafe now mandatory in extern blocks.
Kubernetes 1.33 (Octarine) lands April 23. In-place pod resize moves to beta and ships on by default, sidecar containers finally reach GA, and several endpoint and security deprecations arrive that operators should review before upgrading from 1.32.
Desde que Microsoft abrió GraphRAG, el patrón de usar grafos sobre tus propios datos ha pasado de experimento académico a técnica con aplicaciones prácticas. Reflexión sobre cuándo compensa, cómo se monta y qué errores se repiten.
The AI features Figma has rolled out since Config 2024 are changing how product design teams work. A look at what each feature delivers, what remains human work, and which habits are taking hold across teams.
JuiceFS is a distributed, POSIX-compliant file system that separates data, stored in an S3-compatible object store, from metadata, stored in a database such as PostgreSQL or Redis. This guide installs JuiceFS on a three-node Linux cluster to share files without relying on NFS.
Hybrid search combines BM25 and vector retrieval to cover what each misses alone. Vectors fail on exact identifiers like SKUs or CVEs; BM25 fails when query and document use different vocabulary for the same idea. Reciprocal Rank Fusion (RRF) merges both rankings without depending on their score scales.
Model Context Protocol (MCP) is the open standard Anthropic published on 25 November 2024 to connect language models with external data and tools over JSON-RPC 2.0. It does not replace function calling: it standardises the server side, aiming to become for context what the Language Server Protocol is for code editors.
MariaDB 11.7 (November 2024) adds native vector search with an HNSW index, JSON improvements via JSON_OBJECT_AGG, and 5-15% faster read workloads versus 11.5. Against MySQL 8, the edge is not depending on HeatWave for embeddings; against PostgreSQL, it still trails on JSON depth and data types.
Rust 1.75 stabilises async fn in traits, return-position impl Trait, and several byte-level pointer methods such as byte_add. Rust 1.76 adds an ABI guarantee between char and u32, plus convenience utilities like Result::inspect and type_name_of_val. Two releases that add real ergonomics without flashy gestures.
DuckDB es el motor analítico embebido que ha cambiado el panorama. Lee Parquet y CSV directamente, vectoriza la ejecución y cabe dentro de tu proceso Python. Un repaso a cuándo sustituye de verdad a un data warehouse.
Figma Dev Mode is the developer-facing view inside a Figma file: it generates ready CSS, exposes exact measurements, maps variables to tokens, and, with Code Connect, links each component to the real codebase snippet. It solves most of the design-to-code handoff friction, but it does not replace human judgment on accessibility, performance, or responsive behavior.
GitHub Copilot Workspace, in technical preview since April 2024, proposes task-oriented development: describe the problem in a GitHub issue and the AI reads the codebase, generates an editable multi-file plan, and implements it. It competes with Cursor Composer, though with more latency; its edge is native integration with PRs, issues, and GitHub history.
vLLM serves language models on GPU using PagedAttention and continuous batching, two techniques that multiply throughput compared with a naive server. It exposes an OpenAI-compatible API, so migrating an existing application only requires changing the base URL and deploying the right binary.
Tras dos años de RAG en producción, patrones claros emergen: chunking inteligente, hybrid search, re-ranking, evaluación continua. Qué evitar.
Qwik bets on resumability instead of hydration: the server serialises state into the HTML itself and the client downloads nothing until the user actually interacts, so the initial application bundle is zero kilobytes. In Lighthouse that means a TTI below 0.5 seconds, though it does not pay off for teams already invested in React or for apps with heavy realtime collaborative state.
OpenAI's Assistants API offers persistent threads, sandboxed code execution, and managed document search, but OpenAI is shutting it down completely on August 26, 2026 in favor of the Responses API. We look at when it used to pay off against Chat Completions with your own infrastructure, and what to do if your project still depends on it.
Almost two years after 1.0, SvelteKit works in production: 30-50% lighter bundles than React, file-based routing, and no-lock-in deployment. It wins for small teams with stack freedom; it loses to Next.js when a team has heavy existing React investment or needs to hire fast.
Litestream is an open-source tool that replicates a SQLite database to an S3 bucket in near real time by reading the WAL SQLite already writes. It offers point-in-time recovery, overhead of only 1 to 3% CPU, and replaces the need for a separate database server in small apps.
Kubernetes 1.31 brings no fireworks, but it closes old debts: AppArmor reaches GA, native sidecars now run enabled by default on their way to stable in 1.33, and DRA moves through alpha toward beta. A practical review from the perspective of someone operating clusters in production.
OpenTelemetry declared logs signals stable in July 2024. The third pillar of modern observability finally joins metrics and traces under a single protocol and a shared data model.
HTMX returns HTML instead of JSON and makes the server the source of truth for the interface. Where it fits, where it does not, and why version 2.0 leaves it ready for serious projects.
App Router went stable in Next.js 13.4 (May 2023), bringing Server Components, layered caching, and Server Actions, but it demands rethinking the application's mental model. Migrating from Pages Router pays off for new projects and read-only routes; for large applications, the realistic path is incremental, route by route, over several months.
This guide installs PostgreSQL 16 with pgvector on Debian or Ubuntu using the official PGDG repository, creates a dedicated role and database, tunes memory for production, and explains when the HNSW index beats IVFFlat depending on vector volume and the available maintenance window.
containerd is the runtime that runs containers in most modern Kubernetes clusters, and almost nobody notices. It manages the full container lifecycle: pulling the image, starting it, networking, and mounting the filesystem. It became the default runtime after Kubernetes 1.24 removed dockershim in May 2022.
Event-driven architecture decouples services through message brokers. Each component publishes events when something changes, instead of calling other services directly. It reduces coupling and improves resilience. It adds real value in domains with multiple consumers and natural asynchronous processing, but introduces operational complexity worth evaluating before adoption.
pgvector turns PostgreSQL into a fully functional vector database without adding a separate service to the stack. It extends Postgres with the vector type, IVFFlat indexes for approximate nearest-neighbour search (ANN), and the ability to combine relational SQL filters with vector ranking in a single query. For most RAG projects and internal chatbots, those limits never become a problem.
A practical guide for development teams who need to meet WCAG 2.1 without turning accessibility into an endless project. Three layers, a set of proven tools, and 2-3 months of disciplined work are enough for most teams.
