Editorial cluster
Software architecture
A pillar page that organizes posts about system design, legacy modernization, full stack decisions, and applied AI with production judgment.
Modernization and legacy
How to move existing systems without breaking operations or inventing heroic migrations.
Full stack architecture
Next.js, backend, data, and clear boundaries between product, platform, and operations.
Applied AI with judgment
Agents, models, and automation when they improve a real, auditable workflow.
Recommended reads
Initial selection based on thematic search. Fine-grained cluster assignment belongs in the next sprint.
TensorFlow: the ML elephant that's still standing
TensorFlow isn't sexy in 2025, but it's still the serious infrastructure behind deployment at scale. Why it made the list and when you actually need it.
lode: Reimplementing DVC's core in Go without breaking the format
lode reimplements DVC's hot path in Go with a non-negotiable invariant: byte-identical compatibility with DVC 3.x. Static binary, parallel hashing, state DB that avoids re-hashing. No migration, no lock-in. But pipelines are out of scope and benchmarks have context. Here's why that perimeter is an honest technical decision, not a limitation to hide.
OWASP LLM Top 10 in Production: How I Audited My TypeScript Agent Pipeline Against All 10 Risks — and What I Found
Running the OWASP LLM Top 10 as a real audit is a completely different experience than reading it as a checklist. I ran it against my TypeScript agent stack with system prompts, MCP tools, and Cline — and the findings were uncomfortable.
pnpm workspaces in a monorepo: the setup that survived CI on Railway and the problems the docs don't warn you about
pnpm workspaces is the best option for TypeScript monorepos in 2026. But the happy path in the docs hides three traps that only show up in CI with real deployments: phantom dependencies, broken hoisting on Railway, and script filtering that doesn't filter what you think it does.
Spring Boot Actuator: What to Expose, What to Hide, and What to Check Before Adding Endpoints
Actuator isn't the problem. Enabling it without a clear exposure policy is. A practical guide to using it as an operational tool without turning it into unnecessary public attack surface.
OpenTelemetry in Next.js: traces that survive the edge/server boundary without losing context
OpenTelemetry in Next.js works, but the default propagator silently breaks the trace at the edge/node boundary. Here's what you need to configure explicitly so context doesn't vanish between Middleware, Server Components, and Server Actions.