


From /app to app.: A Safe, Phased Migration to a Dedicated Subdomain
Migrating a web app from a path-based URL (example.com/app) to a dedicated subdomain (app.example.com) sounds simple—until you touch authentication, routing, and API boundaries. The good news: with a deliberate plan and a phased rollout, it can be low-risk—even boring.
This post outlines a practical approach that worked for us, distilled into phases, traps to avoid, and a reusable checklist.
This approach is especially useful for SaaS products, dashboards, and SPAs that rely on hosted authentication providers and API-driven backends.

Local-First Web Apps: Why They're Making a Comeback (and How to Build One)

AI for Developers: A Practical, No-Hype Primer for AWS & Backend Engineers

How to Change Default branch to 'main'

Peoria, Illinois
Peoria, Illinois sits along the Illinois River in the heart of the Midwest and serves as a regional hub for central Illinois. Known historically for manufacturing and river commerce, the city has evolved into a blend of industry, healthcare, education, and outdoor recreation.
Peoria is perhaps best recognized as the longtime global headquarters of Caterpillar Inc., which shaped much of the city’s economic and engineering identity. That legacy still shows today through a strong presence of technical professionals, healthcare workers, and skilled trades.