Why I Migrated From Jest to Vitest
ESM packages broke Jest. Tried to fix it. Could not. Switched to Vitest.
A collection of technical deep dives, random experiments, and notes on software engineering.
ESM packages broke Jest. Tried to fix it. Could not. Switched to Vitest.
Baseline comparison across NestJS, Spring Boot, and Go at 1 CPU / 512MiB. Plus Express vs Fastify, virtual threads, and what surprised me.
The benchmark pipeline ran. The numbers looked reasonable. They were wrong six different ways.
The rewrite landed with 4 subcommands and consola. Three days later it had a live status bar, CPU pinning, profile system, and one less subcommand.
How the benchmark pipeline was rewritten from bash to a Bun CLI with typed subcommands, config, and a full pipeline orchestrator.
The benchmark kept growing. More backends, shared Postgres, sequential orchestration, a compare script. Each addition made sense. Together they outgrew the script.
How the Green Algeria Map benchmark pipeline started as a quick comparison between two backends and grew into something that needed a real CLI.
A hands-on tour of Java 25: flexible constructors, scoped values, and primitive patterns.
Why Green Algeria Map uses React 19, TanStack Router, NestJS, and Tailwind v4.
Run unit and integration tests from the same codebase with separate Vitest configs and file suffix conventions.
What it looks like to start a real project with React 19, TanStack Router, Tailwind CSS v4, shadcn/ui, and GitHub Actions from day one.
A quick map of how Java features move from JEP idea to general availability (GA) and how to try them without surprises.
My 2026 Java deep-dive plan: JVM behavior, performance habits, and consistent weekly output.