#gcs

How I built a unified events timeline that aggregates four heterogeneous data sources — GCS manifest history, step traces, and database assignments — into one debuggable pipeline observability UI.

How I replaced a rigid two-level sector/occupation taxonomy with an L(n) extensible type system, YAML version-gated seeding, GCS compare-and-swap storage, a full admin tree editor, and backward-compatible API adapters — without breaking existing pipeline consumers.

Two race conditions in distributed step leasing where stale workers deleted fresh locks — fixed with GCS generation-based optimistic concurrency.

Provider-service architecture with hot-swappable GCS and Prisma backends, run manifests, unified 13-node pipeline, and desktop-parity task detail pages.

stack: Google Cloud Storage Workload Identity Federation Service Accounts Static Site...

Compare Direct GCS hosting and Load Balancer setups to find the best way to deploy static websites on Google Cloud.

Have you ever worked on applications that interact with multiple cloud providers to store or retrieve...

In this module, I'm going to take the data I wrote in the last post, "API to GCP with Mage", from...

Uploading files is full of pain, especially in Python. A large file uploading will block a request fo...

I recently tried out using Rails 6's new Action Text feature for a simple blog page. One thing I like...