
Voodoo.js: breakthrough or a return to a simpler web?
A deep look at Voodoo.js: HTML-first without a build, JSX in markup, reactivity without a Virtual DOM, honest benchmarks, and why the idea matters more than speed in the AI-coding era.
Developer news without the noise — My Dev News in Telegram.

Tag
All blog posts with this tag.

A deep look at Voodoo.js: HTML-first without a build, JSX in markup, reactivity without a Virtual DOM, honest benchmarks, and why the idea matters more than speed in the AI-coding era.

Reverse engineering Voodoo.js: from the browser HTML parser’s DOM to a lexer, Pratt AST, tree-walking interpreter, Proxy effects, and direct node writes—without eval.

A layer map of Voodoo.js: walker, scope, reactivity, the cost of skipping a build, bundle size, feature creep, and HTML as an artifact for AI coding.

A practical path from single-digit classification to sequence recognition on real paper forms: CNN, CTC, CRNN, TrOCR, labels from your database, experiments, and a production pipeline without the wrong model.

GoF digest: patterns as named solutions, Strategy and Observer today, pattern fever trap, AI cargo-cult — with cases and actions for today.

Production RAG cannot leave authorization to the model. How to isolate tenants, apply access lists before retrieval, close hidden leak channels, and measure recall under tight filters.

A production ingest pipeline for RAG: immutable originals, PDF and scan parsing, tables that keep their headers, parser quarantine, versioning, and idempotent replay.

There are no universally fast data structures. How to count storage, access, mutation, and movement costs — and pick a structure for the actual workload.

Proxy dual-run, #shared core, adapters, and agents: lovable.dev left Vercel for its own stack at 42M MAU.

How text becomes tokens and vectors, what a Transformer actually does, why training is not RAG, and how to grow a Markdown knowledge base into retrieval.

A practical map of LLM adaptation: what changes model weights, what plugs in knowledge and tools, and how to choose an approach without “fine-tuning on PDFs.”

Why distilled models spawn extra tool calls, how benchmarks mislead, and which metrics beat price-per-million for agent TCO.

Five-layer problem specs for AI coding: invariants, data contracts, concurrency, fault topology, and observability—before you prompt.

LLM quality checks: public task sets, arenas, model judges, safety, product regression, and online signals — what each test measures and what it cannot see.

Qdrant, Pinecone, Weaviate, pgvector, and Milvus compared for agent memory: filtering, hybrid search, tenancy, and quantization.

A real-app walkthrough: Fabric and JSI, where work runs, bare vs Expo, keyboards on complex forms, and where AI actually helps in RN.

Make the specification the primary artifact: spec → plan → agent code → verify, 2026 tools, vs TDD/BDD, and where SDD breaks.

How to run a vector database as an index layer: ANN algorithms, filters, tenancy, operations, and when pgvector beats a dedicated store.

64 agents moved Bun's core in 11 days. The rewrite taboo was about cost, not metaphysics — and review debt did not disappear.

A feature is an investment that does not end at release. How to account for build, verification, support, and failure cost — and why you should test in proportion to blast radius, not coverage percentage.

Twelve software engineering books worth reading: selection criteria, who each is for, core ideas, and a forthcoming digest series on this blog.

Build an AI evaluation harness that connects golden datasets, retrieval and generation metrics, CI regression gates, shadow traffic, release controls, observability, and LLM gateway FinOps.

A practical operating model for putting AI agents and RAG systems into production: policy-as-code, narrowly scoped tools, human approvals, adversarial testing, and audit evidence that engineers can actually use.

Build LLM failover playbooks with bounded retries and honest degraded modes.

A practical 2026 guide to LLM gateways and FinOps: request taxonomy, model routing, token budgets, caching caveats, failover, multi-provider contracts, chargeback, security, observability, and a 90-day rollout plan.

Design stable model routes around workload contracts rather than provider labels.

Build a multi-tenant semantic cache without cross-tenant exposure or stale authorization.

Set token budgets and chargeback using useful-work metrics and clear ownership.

A practical guide to production RAG architecture: ingestion, chunking, hybrid retrieval, reranking, evaluation, observability, security, and staged delivery for engineering teams.

A production security model for prompt injection: treat retrieved documents, web pages, tool results, and MCP resources as hostile input; isolate context, constrain egress and tools, sandbox execution, and test layered defenses.

Run controlled chunking experiments while preserving document structure and citations.

Build a representative, versioned golden dataset for RAG retrieval and answer evaluation.

Combine BM25, vector retrieval, and reciprocal-rank fusion with measurable production guardrails.

Operate a RAG reranking stage with explicit quality, latency, and cost budgets.

A realistic Go growth map: the Junior foundation, Middle-level idioms and production work, then Senior architecture and responsibility—without needless frameworks or checklist theater.

A practical guide to Model Context Protocol after the 2026-07-28 release: no sessions, MRTR, header-based routing, auth hardening, shadow MCP, and servers that survive real load.

How to design scalable RAG for many data sources, millions of documents, and access-controlled enterprise knowledge.

How to design a scalable enterprise AI platform where knowledge, security, and integrations matter more than any individual model.

Arcovia analyzes React and Next.js projects, maps dependencies, explains its architecture score, and highlights refactoring priorities.

How interviews, process analysis, and knowledge discovery prepare an enterprise AI project for sound design.

Why an enterprise AI project starts with business needs, knowledge, and security—not with a model or server choice.

How to build an enterprise AI platform that can outlive changing models, vendors, and data formats.

AI already writes working functions, but a product is architecture, context, risk, and accountability. The boundary between code and engineering, a 15-year legacy case study, and developer skills in 2026.

Millions of lines, hundreds of tables, dozens of integrations: what AI grasps in hours, where it fails, how teams deploy RAG and repo indexing, and why expert + model beats either alone.

The full HTTP request journey — DNS, TLS, CDN, load balancer, Nginx, backend, Redis, queues, PostgreSQL, and back to the browser. A practical guide for developers and architects.

Metadata Driven Architecture, platform engines, frontend stack, and migration strategy — how to build an ERP that evolves for decades without a rewrite every five years.

Why systems die from early architectural decisions, not outdated tech — and how to design for change, not features: module boundaries, domain modeling, data, ADRs, and a decade-long checklist.

Entity–Attribute–Value looks perfect at the start: flexibility without migrations. Why JOINs, indexes, and reports break ERP years later — and where EAV fits, and where it does not.

Why the illusion of universality turns ERP into an EAV monster: lost performance, typing, and business meaning — and how to build around the domain, not abstract entities.

From server-side rendering in 2005 to AI apps and edge computing: how web architectures changed, why past choices were not mistakes, and how to pick an approach in 2026.

The ERP success paradox: exceptions, technical debt, a single database, and the distributed monolith. Why the monster follows business growth and how to slow decay.