A look at how the industry is moving from rapid, conversational AI coding to structured, specification-first development and the tools driving that shift.

The Shift from Vibe Coding to Spec-Driven Development

How I improved Lighthouse performance on image-heavy blog posts using staged optimizations: lazy loading, WebP conversion, and LCP/CLS tuning.

Improving Lighthouse Performance with Image Optimization

Trimmed the 'Adjusting on the Fly' section to remove a verbose paragraph about next-mdx-remote vulnerabilities, cleaned up the comparison table, and added the OG/hero image.

Added coverage of the post-publish npm audit surprise — 21 HIGH severity vulnerabilities from next-mdx-remote v4 and a minimatch ReDoS — integrated into the main narrative rather than a separate postscript.

Fixed typos throughout, added the ArticleNote disclosure that the post was AI-generated, and restructured several paragraphs in the Results and What I Learned sections for clarity.

What it took to go from Next.js 9.5, 136 vulnerabilities, and an abandoned MDX plugin to a fully modern stack with zero vulnerabilities — using AI-assisted development.

Hello, I'm Tiago.

I'm a Software Engineer and this is my personal blog.

Hello, I'm Tiago.

I'm a Software Engineer and this is my personal blog.

Recent Posts

The Shift from Vibe Coding to Spec-Driven Development

Improving Lighthouse Performance with Image Optimization

Upgrading a 4-Year-Old Next.js Blog with AI