#Laravel

11 posts tagged with #Laravel

frontend-engineering · Aug 27 · 13 min

I Do Not Add a Second Chart Stack Mid-Sprint

A green chart lockfile is not permission to add ECharts beside ApexCharts. Name a rollback owner and one failing chart fixture before anyone ships a second visualization stack.

frontend-engineering · Jul 31 · 12 min

A UI kit lockfile bump is change control, not cosmetics

shadcn-vue 2.8.1 looks like a quiet patch until registry entries, icon maps, message-scroller gutters, and number-field styles hit a real admin surface. Treat the lockfile bump as a release decision with an owner, smoke list, and rollback.

backend-infrastructure · Jul 30 · 13 min

PHP 8.5.9 is a runtime patch contract, not an app deploy

PHP 8.5.9 fixes CVE-2026-17543 in pgsql and other security issues. A green Laravel deploy does not prove the hosts, CI images, workers, and base containers actually run the patched binary.

ai-agents · Jul 28 · 13 min

The Schema Change an AI Coding Agent Cannot Safely Guess

A generated migration that runs locally is not a production contract. Before an AI coding agent rewrites columns, require expand steps, dual-read boundaries, backfill evidence, worker compatibility, and an explicit rollback decision.

backend-infrastructure · Jul 25 · 12 min

The Rollback Path Is the Real AI Coding Feature

A clean AI-generated diff is not ready for production until a team can disable it, restore its data path, and prove the prior behavior returned. Build rollback evidence into the change before the model writes the patch.

frontend-engineering · Jul 22 · 12 min

Vue Query Cache Invalidation Is a Contract, Not a Refetch Button

A successful Laravel mutation does not prove a Vue admin screen is fresh. Define query-key ownership, invalidation, rollback, and hydration as one cache contract.

ai-agents · Jul 19 · 15 min

AI Agent Frameworks in 2026 — What the Comparison Charts Don't Tell You

A production evaluation guide for LangGraph, AutoGen, CrewAI, and LangChain: define state, proof, rollback, and maintenance exit criteria before an agent framework reaches a real SaaS workflow.

laravel · Jul 16 · 15 min

Laravel Image Processing Is an Adoption Contract, Not an Upload Feature

A Laravel image workflow should preserve originals, produce deterministic variants, isolate processing behind a seam, and remain operable after the demo is gone.

tutorial · Jul 15 · 14 min

The Request Boundary Is Your Compatibility Contract

Treat Laravel and Inertia request boundaries as explicit compatibility contracts: validate and normalize input, serialize durable job payloads, lock responses with fixtures, and leave a clean rollback seam.

developer-tools · Jul 14 · 12 min

A Small Diff Is Not a Small Change: Review AI Patches by Code Entity

A short AI-generated diff can cross validation, request, persistence, and test boundaries. Review the named code entities, the evidence, and the rollback seam—not only the lines that changed.

devops · Jul 6 · 14 min

Zero-Cost Observability for Agent Crons

A low-cost observability pattern for agent crons using logs, artifacts, summaries, and delivery checks before adding paid monitoring tools.

Also see: #Coding-Agents #Laravel #Vue #Change-Control #Code-Review