How I sped up CI and release pipelines for a large Next.js app: disabling inline ESLint and type checking in next build, running them as parallel jobs, linting only changed files, and fixing broken caches.
A Cloud Run service kept hitting its memory limit at startup. The cause: uv run re-syncs the environment by default, reinstalling the dev dependency group at runtime even though the image was built with --no-dev. The fix is --no-sync (and --no-install-project for better layer caching).
Moving the app off its default *.run.app URL onto a company subdomain with Cloud Run domain mappings: the domain-verification step the runbooks skip, why a zone apex takes A/AAAA records instead of a CNAME, why the cutover order matters when an OIDC audience is involved, and a 502 that looked like a broken deploy but was a TLS cert still propagating.
The cloud half of the DB: enabling GCP APIs, choosing the cheapest Cloud SQL tier and why, Private Service Connect with no public IP, serverless VPC egress, and migrating a database you cannot reach from your laptop.
Deploying the still-mock-backed app to Cloud Run gated two ways (Slack SSO at the app layer and an office-IP allowlist) with a standalone container and keyless GitHub Actions via Workload Identity Federation. Plus the cost call between an app-layer IP check and Cloud Armor, and the auth gate that forced collapsing an internal self-fetch.
