Category
Honest software development: code that lasts and stays with you.
The idea of UI generated on the fly instead of pre-built reached production in 2025. After a year of real-world use, the balance is more nuanced than the initial enthusiasm suggested.
Claude Code leads long-horizon agentic work, Cursor wins for fast daily interactive editing, Aider dominates CI-pipeline automation, and GitHub Copilot fits teams built around GitHub PRs; Windsurf competes with fresh traction. After a year using all five hard, the most productive combination for most people is still Claude Code plus Cursor.
Kubernetes 1.35 GA consolidates three releases of work: native sidecars with full lifecycle management, generalised DRA for FPGAs and NPUs, and a scheduler that cuts resource waste by 15-25% in heterogeneous clusters. An operations-side balance sheet: what to enable now, what to watch before migrating, and what path to follow from 1.30.
Skills package reusable capabilities; subagents isolate bounded-task execution. Together they form the most effective pattern for composing complex agents in 2026.
The Model Context Protocol, proposed by Anthropic in late 2024 and adopted through 2025-2026 by Anthropic, OpenAI, Google, and the open-source community, already has proven operational patterns: separating generic servers from custom ones, explicit per-tool policies, credentials kept outside the model, prefixed composition, and contract tests. This is the state of the art in 2026.
Hybrid RAG in 2026 combines dense and lexical search fused with RRF, cross-encoder reranking over the top-50 candidates, structure-aware chunking, and continuous evaluation with Ragas or TruLens. It is the pattern that survives in serious production systems three years after the initial embeddings boom.
Kubernetes won the orchestration battle, but Docker Swarm stays maintained inside Docker Engine and makes real sense for small teams without dedicated SRE, self-hosted stacks on 1-5 VPS, and edge mini-clusters. In those contexts, Swarm's minimal learning curve and low operational cost outweigh Kubernetes's advanced features.
An Agent OS is a runtime layer built to run AI agents rather than ordinary applications, and after six months of production deployments the trade-off is clear. A dedicated agent stack starts slower but stays stable; Kubernetes with orchestration bolted on top moves faster early, then hits observability and policy limits. It pays off from five active agents.
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.
Platform engineering worked where teams built on concrete, painful problems and offered golden paths developers actually wanted, run with a product mindset. It stalled where the output was an empty Backstage portal: technically correct, unvisited, solving no operational problem. Three years after the Gartner hype of 2023, that split separates the winners from the sunk cost.
Four and a half years after Rust officially entered Linux 6.1, with real Apple GPU and NVMe drivers in production and several public conflicts between maintainers, it is time for a sober technical balance. What works, what still costs, and where the next phase is heading.
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 was stabilized in late 2025 and adds what preview 2 lacked: native async, bidirectional streams, and inter-component concurrency with specified semantics. Portability and async are no longer a trade-off, since one async component runs unchanged on wasmtime, WasmEdge, JCO and the main commercial runtimes. API gateways and SaaS extension plugins are the strongest production cases.
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.
Six months after A2A landed at the Linux Foundation, and after several implementation cycles from Google, Microsoft, and open projects, what version 1 of the protocol means and whether it is safe to build on yet.
Kubernetes 1.35 has reached feature freeze, and three items matter. CEL-based admission policies go stable, replacing admission webhooks with expressions evaluated inside the control plane and removing an external failure point. Dynamic Resource Allocation goes stable for GPUs, NPUs and other accelerators. The new KubeletConfigSource API pushes kubelet configuration without restarting the node.
containerd Wasm support is production ready: the runwasi shim ships in containerd 2.0 and is backported to 1.7.7 and 1.6.25, so WasmEdge or wasmtime workloads run beside ordinary Linux containers on one Kubernetes cluster, selected per pod through RuntimeClass. Wasm wins on cold start, image size and kernel-free sandboxing, but not every workload fits.
The European Accessibility Act became enforceable on 28 June 2025, and the first six months produced sanction files in Spain, Germany and the Netherlands along with several forced mass-remediation projects. Directive 2019/882 covers consumer-facing products and services, and the technical bar regulators apply is EN 301 549, which takes WCAG 2.1 level AA as its baseline.
With MCP solving the agent-to-tool layer, a parallel problem surfaces: how do two agents from different vendors communicate with each other. Google's Agent2Agent protocol, donated to the Linux Foundation in June 2025, tries to fill that gap with an open standard.
Neural processing units have stopped being a marketing label on Snapdragon, Apple Silicon and AMD Ryzen AI laptops. Here is what you can actually do from code today, which tools are mature, and when it pays off to target the NPU instead of the CPU or GPU.
gVisor isolates containers by inserting Sentry, a kernel written in Go, between the container process and the real host kernel, shrinking the system-call surface a hostile tenant can reach. Its OCI-compatible runsc runtime drops in where runc used to sit. Use systrap mode, the default since 2023: portable, no special hardware required.
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.
An inference router decides which model answers each incoming request, weighing cost, latency and how hard the request actually is. Well-built inference routers cut total token spend by 30 to 70 percent with no quality loss the user can perceive. Four patterns cover most cases: length, task type, an auxiliary classifier, and learned routing.
TigerBeetle is a distributed database written in Zig, specialized in one specific kind of workload: high-volume double-entry accounting with strong consistency guarantees. It does not aim to replace Postgres; it aims to be the right tool when the problem is counting financial transactions at millions per second without subtle failures.
After three years of expansion and an overheated ecosystem around the term, platform engineering enters 2025 in a consolidation phase. The internal platforms that survive are the ones that understood their real function; those that mistook the label for the solution are dismantling their teams or cutting them drastically.
Citus is a Postgres extension that spreads tables across worker nodes while the cluster still looks like a single Postgres server to your application. The coordinator intercepts query planning and distributes the work. Picking the distribution key is the decision that matters most, since every later query inherits its consequences.
SQLite in production is a sound choice for small and mid-sized web applications once WAL mode is enabled, since concurrency on typical web loads improves by roughly two orders of magnitude. Litestream streams the WAL to S3-compatible object storage for point-in-time restore, and NVMe disks on cheap VPS plans removed the old disk objection.
After years of promising an open lakehouse, Apache Iceberg with REST catalogs plus dbt on top has jelled in 2025 into the reference stack. I break down what it solves, where it still hurts, and why the clean split between table, engine and transformation matters more than it looks.
DuckDB has spent two or three years quietly working its way into data architectures. It is no longer just the embedded database for local analytics: in 2025 it keeps turning up in concrete enterprise cases where it replaces far pricier pieces. A tour of the real patterns.
The term Agent OS has spent a year gaining traction across research and product circles. It describes a layer that goes well beyond an agent library: request scheduling, context management, persistent memory, and isolation. A look at the real state of that concept.
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.
Free threading in Python became real with 3.13 and PEP 703, which makes the GIL optional at build time: the standard binary keeps it, while the separate python3.13t binary removes it. Thread-heavy orchestration code gains most; NumPy-style work that already released the GIL barely changes. Single-thread performance on that build drops around 40 percent.
Generative AI helps user research most in transcription, where it reliably saves hours, and in early note synthesis and discussion guide drafting. It does not replace real participants: synthetic personas return plausible answers rather than the genuine surprises interviews produce. Verify every quote in a final deliverable against the original transcript before anyone acts on it.
Redpanda promises Kafka-protocol compatibility without the JVM, without ZooKeeper, and with a thread-per-core architecture. By 2025 there are already serious production deployments. It is worth understanding where the switch pays off and where it does not.
Kubernetes 1.34 ships with Dynamic Resource Allocation (DRA) graduating to stable, scheduler improvements, and CEL-based mutating admission policies that replace webhooks. A practical rundown of what is safe to upgrade now, what can wait, and what actually changes for teams running production clusters.
Redis 8.2 ships vector search as a native data type. The real question is whether it replaces a dedicated engine like Qdrant, Weaviate, or pgvector on workloads with millions of vectors and tight latency budgets, or only works as a bonus on top of the cache you already run.
Kafka 4.0, released on 18 March 2025, cannot start with ZooKeeper at all, so KRaft is the only option left. Metadata management now lives inside Kafka itself, a path that opened with KIP-500 in 2019 and became production-ready in Kafka 3.3. Migration is mandatory, and it shifts daily operations.
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, released in late June 2024, is a low-risk upgrade whose main wins are inferred type predicates in filter callbacks, which delete dozens of trivial annotations, and regular expressions checked at compile time. A year of daily use separates those from the cosmetic changes and from the spots where existing code needs adjusting.
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.
