The working archive / page 2
Blog
Dagster vs Airflow for a New Data Platform: Assets, Sensors, and Day-Two Operations
Dagster and Airflow compared on assets, sensors, partitions, backfills, retries, and observability, so you can choose the right core for a new platform.
Data Quality Gates with Great Expectations: Expectations, Checkpoints, and CI
Build a working data quality gate with Great Expectations: define an Expectation Suite, run it as a Checkpoint, store the results, and fail CI on bad data.
Incremental Models in dbt: Merge Strategies, Late Data, and Full-Refresh Discipline
Choose the right dbt incremental strategy, handle late-arriving data with lookback windows, and build the full-refresh habits that keep incremental models trustworthy.
dbt Tests and Data Contracts: Catching Upstream Breakage Before Your Stakeholders Do
Layer dbt generic, singular, and unit tests with enforced data contracts so upstream schema and logic changes fail in CI, not in a stakeholder's dashboard.
Change Data Capture with Debezium: From Postgres WAL to a Consumer That Keeps Up
Stand up Debezium on Postgres logical decoding, protect the replication slot, and write a consumer that handles snapshots, deletes, and schema changes without losing rows.
Auditing a Developer Onboarding Funnel: Signup to First API Call, Timed and Scored
A repeatable audit method for the developer onboarding funnel, with a scoring rubric and a clearly labelled illustrative walkthrough.
Diátaxis, Applied: Reorganising a Real Docs Site Without a Six-Month Rewrite
A field guide to applying the Diátaxis framework incrementally: audit what you have, split the pages that do two jobs, and move content in slices readers never notice.
Multi-Stage Docker Builds for Node and Python: Smaller Images, Fewer Surprises
Learn multi-stage Docker builds for Node and Python with cache mounts, slim runtime images, non-root users, and digest pinning to cut bloat and build risk.
Docs as Code, With Teeth: Linting, Link Checks, and Preview Builds in CI
Wire documentation into CI so quality is enforced, not hoped for: prose linting that respects writers, link checking without false alarms, and previews on every pull request.
Error Messages Are Documentation: A Field Guide to Writing Failures Users Can Fix
A practical method for writing error messages that name the problem, state the cause, and hand the user a fix they can actually perform.
No matches in this set.
Clear a filter or try another combination.