I’m Yampier, a Forward Deployed Engineer based in Indianapolis. I work where software meets the business: the internal tools and last-mile automations that rarely get budget or time, yet quietly compound into serious productivity. Built on Next.js, Tailwind CSS, and AWS Amplify — delivered with spec-driven AI engineering using Kiro and Claude Code.
Spec-driven AI engineering, end to end.
Issue status, driven by the staging automation
Getting a Next.js 16 app with an Amplify Gen 2 backend onto Amplify Hosting SSR took six failed builds — each one surfacing a layer deeper than the last. Here is the full chain: lockfile drift, the 220 MB compute cap, the deployment-spec dead end, a missing xz binary, a non-root build user, and a layer/runtime mismatch — with the fix for each.
How to resolve the inotify_add_watch error when running Amplify Gen 2 sandbox on Linux systems - it is not about disk space, it is about file watcher limits
When your Lambda function needs both Cognito access AND is used as a data handler, use resourceGroupName: 'auth' in your function definition to avoid circular dependencies.
Lambda functions with their own package.json need dependencies installed before esbuild bundles them. Add a preBuild phase to amplify.yml that runs npm ci in each function directory. Also exclude amplify/**/* from your root tsconfig.json.