GPS Data Gets Ugly Fast: A Fleet GPS Data Pipeline That Stays Queryable

Telematics devices lie in specific, documented ways: stale fixes reported as new, zero coordinates after reboot, and buffered records replayed days late. Here is how to build a fleet GPS data pipeline on PostgreSQL, PostGIS and TimescaleDB that survives all three and still answers trip and geofence queries fast.

Continue ReadingGPS Data Gets Ugly Fast: A Fleet GPS Data Pipeline That Stays Queryable

Building an Ecommerce Recommendation Pipeline on AWS: The Parts That Bite

An idle Amazon Personalize setup does not throw errors. It just bills. A practical walkthrough of the five decisions that shape an AWS ecommerce recommendation pipeline: domain recommenders versus custom recipes, bulk versus streaming ingestion, schema limits, training cadence, and real-time versus batch serving, with the failure modes that stay invisible until the invoice arrives.

Continue ReadingBuilding an Ecommerce Recommendation Pipeline on AWS: The Parts That Bite

Parquet vs JSON vs CSV: What Each Format Actually Costs You

Format choice shows up as a bill, not a performance complaint. A working breakdown of where the money actually goes across Parquet, JSON and CSV: column pruning, row-group skipping, the gzip splittability trap, and request overhead. Includes a procedure for measuring the difference on your own data, and an honest account of where Parquet costs you.

Continue ReadingParquet vs JSON vs CSV: What Each Format Actually Costs You

One Customer, Four Systems: Unifying Shopify, Stripe, CRM and Support Data

Three CRM records, one person, and nothing in the logs to explain it. A practical walkthrough of what actually breaks when you unify Shopify, Stripe, CRM and support data: guest-checkout identity, duplicate and out-of-order webhooks, revenue that never ties to payouts, deletion requests that miss half your copies, and reverse ETL write loops. Organized by failure family, with schema and handler patterns you can apply directly.

Continue ReadingOne Customer, Four Systems: Unifying Shopify, Stripe, CRM and Support Data

As-Planned vs As-Built Analysis: Building a Platform That Survives Cross-Examination

Most as-planned vs as-built analysis compares the baseline to the last P6 update and calls the result an as-built. It isn't one. This is how to build the data layer underneath a delay analysis: versioned XER ingestion, activity identity across renumbering, a first-appearance table that proves when every actual date entered the record, calendar-safe float, and record linking that proposes candidates instead of asserting cause.

Continue ReadingAs-Planned vs As-Built Analysis: Building a Platform That Survives Cross-Examination

Extracting Clauses, Parties, Dates and Obligations with Amazon Bedrock

Valid JSON is not correct data. A practical guide to extracting clauses, parties, dates and obligations from contracts with Amazon Bedrock: the two build paths, schema design, the three failure families that produce confident wrong answers, and the validation layer that catches them.

Continue ReadingExtracting Clauses, Parties, Dates and Obligations with Amazon Bedrock