When Slack SSO works for staff but not guest accounts: adding Google sign-in as a gated fallback, re-keying users on email, preserving Slack mentions for users who never sign in with Slack, and enforcing who may use which door.
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.
Replacing an in-memory mock with local Postgres: Docker, a Drizzle schema and first migration, seeding, swapping the data layer, and designing for private-network cloud access.
A new design draft and a fresh requirements list arrived mid-build. How I triaged them against priority, deferred the integration-heavy features without stalling, kept the plan doc as the source of truth, and decided the schema was finally stable enough to stand up the database.
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.
Concrete gotchas from building the UI of a status-driven workflow tool on Next.js 16 and React 19: intercepting + parallel routes for modals, the React Hook Form + Zod typing trap with default values, gating a stepper by status and role, and pinning a gantt with the one legitimate inline-style exception.
A fullstack workflow tool for designers receiving creative work requests, built with Next.js 16, Drizzle on Cloud SQL Postgres, and Slack SSO. Deployed to Cloud Run with GitHub Actions CI/CD. Covers stack planning, AI-assisted development setup, and GCP infrastructure.
A Slack bot powered by Vertex AI Gemini with GCS-based knowledge base, deployed to Cloud Run with GitHub Actions CI/CD. Covers Python dev setup with uv, Flask REST APIs, Gemini integration, and cloud infrastructure.
Four internal operations automations driven by Slack Workflow Builder forms, wired to Google Sheets, Google Calendar, GitHub, and an AI coding agent. A Flask + slack-bolt bot on Cloud Run reads each form submission and turns it into the right action: a private DM, a spreadsheet row plus calendar event, an owner mention, or an auto-generated pull request.
AWS, K8s, GHA, Docker
Node.js, Python
React, Next.js, TypeScript
End-to-end features
Monitoring, Datadog
