Today a second AI agent started up in a directory where another session was mid-work on a dirty branch. It was one git switch away from committing onto the wrong branch. Here's the boring, native fix.
La versión honesta del desarrollo con IA de madrugada: el agente abre pull requests, un humano hace el merge. Lo que amanece listo son borradores para revisar y correcciones que están listas cuando una verificación se pone en verde — jamás un push automático a producción. Este es el montaje que lo convierte en apalancamiento real y no en un riesgo.
The honest version of overnight AI development: the agent opens pull requests, a human merges. What ships by morning is reviewable drafts and done-when-green fixes — never an autonomous push to prod. Here's the setup that makes it real leverage instead of a liability.
The Astro 5 to 6 migration looked like a ten-minute security bump. Instead I hit three build failures back to back — every one of them in vendored theme code I never wrote. Here are the exact errors, the fixes, and why a themed site breaks where your own code doesn't.
A title tag and a meta description aren't an SEO setup — they're the part every template already gives you. The plumbing that compounds (JSON-LD, canonicals that don't 404, hreflang that doesn't backfire, a clean sitemap) is what portfolios skip. Here's my full Astro SEO setup, real code included.
Every new session with an AI coding assistant starts blind — it can't remember why you rejected that approach three weeks ago. The fix isn't a bigger context window, it's persistent memory across sessions, layered. Here's the pattern: native memory for the live thread, a file index for durable facts, and a semantic second brain for everything older.