<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>15x1976 · Articles</title><description>Ideas on engineering, data platforms, software, AI and complex systems.</description><link>https://15x1976.neocities.org/</link><language>en</language><item><title>AI-Augmented Teams: turning individual knowledge into collective capability</title><link>https://15x1976.neocities.org/en/writing/ai-augmented-teams-turning-individual-knowledge-into-collective-capability/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/ai-augmented-teams-turning-individual-knowledge-into-collective-capability/</guid><description>Giving every team member an AI assistant can make individuals faster while fragmenting the team. The real challenge is turning that additional capability into shared context, decisions, and knowledge.</description><pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate><category>AI</category><category>Engineering Culture</category><category>Architecture</category></item><item><title>AI-Native Engineering: from using AI to designing with it</title><link>https://15x1976.neocities.org/en/writing/ai-native-engineering-from-using-ai-to-designing-with-it/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/ai-native-engineering-from-using-ai-to-designing-with-it/</guid><description>AI-Native work is not about asking a model for more code. It means redesigning the engineering process so analysis, decisions, artifacts, and construction can evolve with AI without giving up human judgment.</description><pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate><category>AI</category><category>Software Engineering</category><category>Engineering Culture</category></item><item><title>Snowflake and Databricks: where they converge and which differences matter when designing a platform</title><link>https://15x1976.neocities.org/en/writing/snowflake-and-databricks-where-they-converge-and-which-differences-matter-when-designing-a-platform/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/snowflake-and-databricks-where-they-converge-and-which-differences-matter-when-designing-a-platform/</guid><description>Snowflake and Databricks converge across many capabilities, but differences in execution, storage, operations, and engineering experience still matter when designing a Data Platform.</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate><category>Snowflake</category><category>Databricks</category><category>Data Architecture</category></item><item><title>From Databricks to Snowflake: preserving deployment discipline with CLI and DCM Projects</title><link>https://15x1976.neocities.org/en/writing/from-databricks-to-snowflake-preserving-deployment-discipline-with-cli-and-dcm-projects/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/from-databricks-to-snowflake-preserving-deployment-discipline-with-cli-and-dcm-projects/</guid><description>The deployment discipline learned with Databricks Asset Bundles can transfer to Snowflake without forcing equivalence, using CLI and DCM Projects to version and deploy resources repeatably.</description><pubDate>Tue, 11 Aug 2026 00:00:00 GMT</pubDate><category>Snowflake</category><category>Databricks</category><category>Software Engineering</category></item><item><title>Snowpark: using Python on Snowflake while understanding where the work runs</title><link>https://15x1976.neocities.org/en/writing/snowpark-using-python-on-snowflake-while-understanding-where-the-work-runs/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/snowpark-using-python-on-snowflake-while-understanding-where-the-work-runs/</guid><description>Snowpark lets us express transformations in Python while keeping much of the work inside Snowflake; understanding where each piece runs prevents unnecessary movement of data and resources.</description><pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate><category>Snowflake</category><category>Data Engineering</category><category>Software Engineering</category></item><item><title>From Databricks to Snowflake: what knowledge to transfer and what assumptions to revisit</title><link>https://15x1976.neocities.org/en/writing/from-databricks-to-snowflake-what-knowledge-to-transfer-and-what-assumptions-to-revisit/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/from-databricks-to-snowflake-what-knowledge-to-transfer-and-what-assumptions-to-revisit/</guid><description>Moving from Databricks to Snowflake lets us reuse substantial data engineering judgment, but it requires revisiting assumptions about execution, storage, incremental processing, and platform management.</description><pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate><category>Snowflake</category><category>Databricks</category><category>Data Architecture</category></item><item><title>Mastering Databricks: the decisions behind its advanced capabilities</title><link>https://15x1976.neocities.org/en/writing/mastering-databricks-the-decisions-behind-its-advanced-capabilities/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/mastering-databricks-the-decisions-behind-its-advanced-capabilities/</guid><description>Mastering Databricks is not about knowing every feature, but understanding what problem each capability solves, what it delegates to the platform, and what responsibility remains in the design.</description><pubDate>Fri, 26 Jun 2026 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Architecture</category><category>Data Engineering</category></item><item><title>Databricks capabilities worth evaluating before building your own solution</title><link>https://15x1976.neocities.org/en/writing/databricks-capabilities-worth-evaluating-before-building-your-own-solution/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/databricks-capabilities-worth-evaluating-before-building-your-own-solution/</guid><description>Before building custom infrastructure, it is worth reviewing which responsibilities Databricks can already assume and which controls our architecture genuinely needs to retain.</description><pubDate>Thu, 11 Jun 2026 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Architecture</category><category>Software Engineering</category></item><item><title>Bronze without an extra copy: what guarantees we need before pointing to existing data</title><link>https://15x1976.neocities.org/en/writing/bronze-without-an-extra-copy-what-guarantees-we-need-before-pointing-to-existing-data/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/bronze-without-an-extra-copy-what-guarantees-we-need-before-pointing-to-existing-data/</guid><description>Avoiding an extra physical copy in Bronze can save work, but it is safe only when existing data provides enough stability, identity, retention, and recovery guarantees.</description><pubDate>Fri, 22 May 2026 00:00:00 GMT</pubDate><category>Data Architecture</category><category>Data Engineering</category><category>Databricks</category></item><item><title>Serverless in Databricks: delegating compute without losing operational control</title><link>https://15x1976.neocities.org/en/writing/serverless-in-databricks-delegating-compute-without-losing-operational-control/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/serverless-in-databricks-delegating-compute-without-losing-operational-control/</guid><description>Serverless delegates infrastructure decisions to Databricks, but reliable operations still require boundaries, observability, understandable costs, and clear workload contracts.</description><pubDate>Fri, 08 May 2026 00:00:00 GMT</pubDate><category>Databricks</category><category>Cloud</category><category>Data Engineering</category></item><item><title>Photon in Databricks: how the vectorized engine works and when it improves pipeline cost</title><link>https://15x1976.neocities.org/en/writing/photon-in-databricks-how-the-vectorized-engine-works-and-when-it-improves-pipeline-cost/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/photon-in-databricks-how-the-vectorized-engine-works-and-when-it-improves-pipeline-cost/</guid><description>Photon accelerates certain workloads through vectorized execution, but faster performance reduces cost only when we understand what work it accelerates and how compute is billed.</description><pubDate>Thu, 23 Apr 2026 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Engineering</category><category>Cloud</category></item><item><title>Liquid Clustering in Databricks: organizing data to read less and evolve the design</title><link>https://15x1976.neocities.org/en/writing/liquid-clustering-in-databricks-organizing-data-to-read-less-and-evolve-the-design/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/liquid-clustering-in-databricks-organizing-data-to-read-less-and-evolve-the-design/</guid><description>Liquid Clustering changes how we think about the physical organization of Delta tables: it aims to reduce data read while allowing the design to evolve beyond rigid partitions.</description><pubDate>Thu, 09 Apr 2026 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Engineering</category><category>Data Architecture</category></item><item><title>Advanced engineering in Databricks: the judgment behind a reliable platform</title><link>https://15x1976.neocities.org/en/writing/advanced-engineering-in-databricks-the-judgment-behind-a-reliable-platform/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/advanced-engineering-in-databricks-the-judgment-behind-a-reliable-platform/</guid><description>Advanced engineering in Databricks depends less on accumulating features and more on applying judgment to reliability, operations, cost, and the boundaries of each platform capability.</description><pubDate>Tue, 31 Mar 2026 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Architecture</category><category>Data Engineering</category></item><item><title>Refactoring pipelines in Databricks: improving performance and operations without losing data meaning</title><link>https://15x1976.neocities.org/en/writing/refactoring-pipelines-in-databricks-improving-performance-and-operations-without-losing-data-meaning/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/refactoring-pipelines-in-databricks-improving-performance-and-operations-without-losing-data-meaning/</guid><description>Refactoring a pipeline is not only about making it faster: performance and operations must improve without changing contracts, grain, or data meaning.</description><pubDate>Fri, 20 Mar 2026 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Engineering</category><category>Software Engineering</category></item><item><title>From Delta Live Tables to Lakeflow: when a declarative pipeline makes sense</title><link>https://15x1976.neocities.org/en/writing/from-delta-live-tables-to-lakeflow-when-a-declarative-pipeline-makes-sense/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/from-delta-live-tables-to-lakeflow-when-a-declarative-pipeline-makes-sense/</guid><description>Delta Live Tables evolved into Lakeflow Declarative Pipelines. The important decision is not the name, but when to delegate dependencies, incremental processing, and operations to a declarative framework.</description><pubDate>Tue, 10 Mar 2026 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Engineering</category><category>Data Architecture</category></item><item><title>From the broker to the Lakehouse: what changes with Lakeflow Connect and what we still need to design</title><link>https://15x1976.neocities.org/en/writing/from-the-broker-to-the-lakehouse-what-changes-with-lakeflow-connect/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/from-the-broker-to-the-lakehouse-what-changes-with-lakeflow-connect/</guid><description>Lakeflow Connect can simplify ingestion from brokers, but it does not remove decisions about delivery, recovery, publication, and data meaning inside the Lakehouse.</description><pubDate>Fri, 27 Feb 2026 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Architecture</category><category>Data Engineering</category></item><item><title>The cost of ingesting data in Databricks: discover, process, wait</title><link>https://15x1976.neocities.org/en/writing/the-cost-of-ingesting-data-in-databricks-discover-process-wait/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/the-cost-of-ingesting-data-in-databricks-discover-process-wait/</guid><description>Ingestion cost is not only compute: it also includes file discovery, idle capacity, and repeated work. Optimization requires looking at the entire path.</description><pubDate>Tue, 17 Feb 2026 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Engineering</category><category>Cloud</category></item><item><title>Asynchrony in Databricks: from file arrival to trusted data publication</title><link>https://15x1976.neocities.org/en/writing/asynchrony-in-databricks-from-file-arrival-to-trusted-data/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/asynchrony-in-databricks-from-file-arrival-to-trusted-data/</guid><description>A pipeline can finish green and still publish incomplete data. Designing asynchrony in Databricks means separating arrival, processing, completeness, and trusted publication.</description><pubDate>Thu, 05 Feb 2026 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Engineering</category><category>Data Architecture</category></item><item><title>Event Brokers: queues, streams, and the guarantees your architecture needs</title><link>https://15x1976.neocities.org/en/writing/event-brokers-queues-streams-and-architectural-guarantees/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/event-brokers-queues-streams-and-architectural-guarantees/</guid><description>Queues and streams solve different problems; sound Event Broker design requires understanding delivery, ordering, replay, acknowledgments, and idempotency before choosing technology.</description><pubDate>Mon, 26 Jan 2026 00:00:00 GMT</pubDate><category>Architecture</category><category>Data Engineering</category><category>Software Engineering</category></item><item><title>Asynchrony in ELT: when data is actually ready</title><link>https://15x1976.neocities.org/en/writing/asynchrony-in-elt-when-data-is-actually-ready/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/asynchrony-in-elt-when-data-is-actually-ready/</guid><description>Asynchrony can reduce waiting in ELT, but it also requires explicit states, dependencies, and publication conditions to know when data is actually ready.</description><pubDate>Thu, 08 Jan 2026 00:00:00 GMT</pubDate><category>Data Engineering</category><category>Architecture</category><category>Software Engineering</category></item><item><title>The Champion Is Not Handed Over</title><link>https://15x1976.neocities.org/en/writing/the-champion-is-not-handed-over/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/the-champion-is-not-handed-over/</guid><description>The blind handoff between Data Science and Data Engineering is replaced by a frozen Champion, contract, joint code review, refactoring, and shared validation.</description><pubDate>Mon, 22 Dec 2025 00:00:00 GMT</pubDate><category>AI</category><category>Data Engineering</category><category>Software Engineering</category></item><item><title>When Every Ticket Solves the Same Problem Again</title><link>https://15x1976.neocities.org/en/writing/when-every-ticket-solves-the-same-problem-again/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/when-every-ticket-solves-the-same-problem-again/</guid><description>Industrializing a data factory means turning repeated decisions into reusable capabilities and reserving engineering for what is genuinely new.</description><pubDate>Tue, 09 Dec 2025 00:00:00 GMT</pubDate><category>Data Architecture</category><category>Databricks</category><category>Software Engineering</category></item><item><title>When Every New Table Means a New Pipeline</title><link>https://15x1976.neocities.org/en/writing/when-every-new-table-means-a-new-pipeline/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/when-every-new-table-means-a-new-pipeline/</guid><description>An SAP ingestion platform grew by creating a pipeline for every new table. The alternative was changing the unit of growth from tables and pipelines to reusable extraction patterns.</description><pubDate>Tue, 25 Nov 2025 00:00:00 GMT</pubDate><category>Data Architecture</category><category>Data Engineering</category></item><item><title>What does Data Mesh actually mean?</title><link>https://15x1976.neocities.org/en/writing/what-the-hell-is-data-mesh-and-why-is-everyone-talking-about-it/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/what-the-hell-is-data-mesh-and-why-is-everyone-talking-about-it/</guid><description>Data Mesh is not “putting data into domains.” It redistributes responsibility through domain ownership, data products, self-service and federated governance.</description><pubDate>Tue, 11 Nov 2025 00:00:00 GMT</pubDate><category>Data Architecture</category><category>Engineering Culture</category></item><item><title>Everything Is Green and the Model Is Wrong</title><link>https://15x1976.neocities.org/en/writing/everything-is-green-and-the-model-is-wrong/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/everything-is-green-and-the-model-is-wrong/</guid><description>A green job proves the code finished. It does not prove the data is correct or the model is still useful. ML observability has multiple layers.</description><pubDate>Wed, 29 Oct 2025 00:00:00 GMT</pubDate><category>AI</category><category>Data Engineering</category><category>Engineering Culture</category></item><item><title>Training on the Past Without Looking Into the Future</title><link>https://15x1976.neocities.org/en/writing/training-on-the-past-without-looking-into-the-future/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/training-on-the-past-without-looking-into-the-future/</guid><description>Training on old records is not enough. We need to reconstruct what information would actually have been available at the moment each prediction was made.</description><pubDate>Fri, 17 Oct 2025 00:00:00 GMT</pubDate><category>AI</category><category>Data Engineering</category><category>Data Architecture</category></item><item><title>Could You Reproduce the Model You Put Into Production Six Months Ago?</title><link>https://15x1976.neocities.org/en/writing/could-you-reproduce-the-model-you-put-into-production-six-months-ago/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/could-you-reproduce-the-model-you-put-into-production-six-months-ago/</guid><description>Saving the model artifact is not enough to reproduce an experiment. Data, features, parameters, configuration, dependencies and code all participate in the result.</description><pubDate>Mon, 06 Oct 2025 00:00:00 GMT</pubDate><category>AI</category><category>Data Engineering</category><category>Software Engineering</category></item><item><title>&quot;It Works in My Notebook&quot;: From Experiment to Product</title><link>https://15x1976.neocities.org/en/writing/it-works-in-my-notebook-from-experiment-to-product/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/it-works-in-my-notebook-from-experiment-to-product/</guid><description>A model working in a notebook proves a hypothesis. A product must preserve that meaning while adding repeatability, recovery and operation.</description><pubDate>Tue, 23 Sep 2025 00:00:00 GMT</pubDate><category>Software Engineering</category><category>Data Engineering</category><category>AI</category></item><item><title>From Notebooks to Software: Professionalizing Databricks with Asset Bundles</title><link>https://15x1976.neocities.org/en/writing/from-notebooks-to-software-professionalizing-databricks-with-asset-bundles/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/from-notebooks-to-software-professionalizing-databricks-with-asset-bundles/</guid><description>As a data platform grows, jobs, configuration and deployment deserve software discipline too. Asset Bundles are one mechanism for that discipline, not the thesis itself.</description><pubDate>Tue, 09 Sep 2025 00:00:00 GMT</pubDate><category>Databricks</category><category>Software Engineering</category><category>Data Engineering</category></item><item><title>ADF vs Databricks Workflows: The False Orchestrator War</title><link>https://15x1976.neocities.org/en/writing/adf-vs-databricks-workflows-the-false-orchestrator-war/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/adf-vs-databricks-workflows-the-false-orchestrator-war/</guid><description>ADF and Databricks Workflows overlap, but choosing a universal winner is less useful than deciding where each responsibility starts and ends.</description><pubDate>Wed, 27 Aug 2025 00:00:00 GMT</pubDate><category>Cloud</category><category>Databricks</category><category>Data Engineering</category></item><item><title>Show Me How You Tag Your Workloads and I Will Show You Where You Lose Money</title><link>https://15x1976.neocities.org/en/writing/show-me-how-you-tag-your-workloads-and-i-will-show-you-where-you-lose-money/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/show-me-how-you-tag-your-workloads-and-i-will-show-you-where-you-lose-money/</guid><description>Cost optimization without attribution is guesswork. Before reducing spend, connect compute to workloads, owners and value.</description><pubDate>Thu, 14 Aug 2025 00:00:00 GMT</pubDate><category>Cloud</category><category>Data Engineering</category><category>Engineering Culture</category></item><item><title>Your Platform Does Not Need More Alerts. It Needs Better Alerts.</title><link>https://15x1976.neocities.org/en/writing/your-platform-does-not-need-more-alerts-it-needs-better-alerts/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/your-platform-does-not-need-more-alerts-it-needs-better-alerts/</guid><description>Hundreds of alerts can make a platform less observable than twenty good ones. The goal is not to detect events; it is to identify what requires action and why.</description><pubDate>Mon, 04 Aug 2025 00:00:00 GMT</pubDate><category>Engineering Culture</category><category>Data Engineering</category><category>Cloud</category></item><item><title>Data Governance Does Not Mean Setting Permissions</title><link>https://15x1976.neocities.org/en/writing/data-governance-does-not-mean-setting-permissions/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/data-governance-does-not-mean-setting-permissions/</guid><description>Access control is security. Governance goes further: what does the data mean, who owns that meaning, and under what conditions can it be trusted?</description><pubDate>Mon, 21 Jul 2025 00:00:00 GMT</pubDate><category>Data Architecture</category><category>Engineering Culture</category><category>Cloud</category></item><item><title>When Lineage Is Missing, Everyone Becomes a Detective</title><link>https://15x1976.neocities.org/en/writing/when-lineage-is-missing-everyone-becomes-a-detective/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/when-lineage-is-missing-everyone-becomes-a-detective/</guid><description>Without lineage, every important change becomes detective work: who produces this table, who consumes it, and what breaks if we change it?</description><pubDate>Mon, 07 Jul 2025 00:00:00 GMT</pubDate><category>Data Architecture</category><category>Data Engineering</category><category>Engineering Culture</category></item><item><title>Credentials in Code Are Technical Debt with an Expiration Date</title><link>https://15x1976.neocities.org/en/writing/credentials-in-code-are-technical-debt-with-an-expiration-date/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/credentials-in-code-are-technical-debt-with-an-expiration-date/</guid><description>A hardcoded password solves a connection in seconds and can create a problem that lasts for years. Maturity means reducing how much secret material the application needs to know.</description><pubDate>Wed, 25 Jun 2025 00:00:00 GMT</pubDate><category>Cloud</category><category>Software Engineering</category><category>Engineering Culture</category></item><item><title>Your Sources Will Change. Design for It.</title><link>https://15x1976.neocities.org/en/writing/your-sources-will-change-design-for-it/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/your-sources-will-change-design-for-it/</guid><description>Sources change even when our pipelines do not. Good boundaries make schema, data and semantic drift observable before they become silently wrong data.</description><pubDate>Tue, 10 Jun 2025 00:00:00 GMT</pubDate><category>Data Engineering</category><category>Architecture</category></item><item><title>Hard REST APIs: Surviving Pagination, Tokens, and Retries</title><link>https://15x1976.neocities.org/en/writing/hard-rest-apis-surviving-pagination-tokens-and-retries/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/hard-rest-apis-surviving-pagination-tokens-and-retries/</guid><description>An API is not reliable because one request returned 200. Production engineering begins when pagination, token expiry, rate limits and partial recovery become part of the contract.</description><pubDate>Thu, 29 May 2025 00:00:00 GMT</pubDate><category>Software Engineering</category><category>Data Engineering</category></item><item><title>How One Query Can Ruin Everyone&apos;s Morning</title><link>https://15x1976.neocities.org/en/writing/how-one-query-can-ruin-everyone-s-morning/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/how-one-query-can-ruin-everyone-s-morning/</guid><description>A hard-to-maintain query is often hard to optimize for the same reason: nobody can explain where the work is happening. Breaking the problem apart restores visibility before it adds machinery.</description><pubDate>Fri, 16 May 2025 00:00:00 GMT</pubDate><category>Data Engineering</category><category>Software Engineering</category></item><item><title>Before Scaling the Cluster, Reduce the Work</title><link>https://15x1976.neocities.org/en/writing/before-scaling-the-cluster-reduce-the-work/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/before-scaling-the-cluster-reduce-the-work/</guid><description>More compute can accelerate a poor strategy, but rarely turns it into a good one. Before scaling the cluster, remove work that never needed to happen.</description><pubDate>Mon, 05 May 2025 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Engineering</category></item><item><title>Small Files and Partitioning: When Physical Design Sends the Bill</title><link>https://15x1976.neocities.org/en/writing/small-files-and-partitioning-when-physical-design-sends-the-bill/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/small-files-and-partitioning-when-physical-design-sends-the-bill/</guid><description>A table can contain the right data and still perform badly. How those bytes are physically distributed can matter as much as the transformation that produced them.</description><pubDate>Thu, 24 Apr 2025 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Engineering</category><category>Data Architecture</category></item><item><title>Idempotency: Execution Is Part of the Design</title><link>https://15x1976.neocities.org/en/writing/idempotency-execution-is-part-of-the-design/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/idempotency-execution-is-part-of-the-design/</guid><description>A pipeline that works once is not necessarily finished. The real design shows up when the same unit of work must be executed again without corrupting state.</description><pubDate>Tue, 08 Apr 2025 00:00:00 GMT</pubDate><category>Data Engineering</category><category>Software Engineering</category><category>Architecture</category></item><item><title>Time Travel: Nobody Misses It Until Five Minutes After the Wrong Overwrite</title><link>https://15x1976.neocities.org/en/writing/time-travel-nobody-misses-it-until-five-minutes-after-the-wrong-overwrite/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/time-travel-nobody-misses-it-until-five-minutes-after-the-wrong-overwrite/</guid><description>Time Travel feels optional until the first bad overwrite. Then it becomes a powerful recovery tool—while still not being an infinite backup.</description><pubDate>Thu, 27 Mar 2025 00:00:00 GMT</pubDate><category>Databricks</category><category>Data Engineering</category></item><item><title>Streaming Does Not Mean Real Time</title><link>https://15x1976.neocities.org/en/writing/streaming-does-not-mean-real-time/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/streaming-does-not-mean-real-time/</guid><description>Streaming describes a processing model; real time describes a latency expectation. Confusing the two can buy complexity without buying business value.</description><pubDate>Fri, 14 Mar 2025 00:00:00 GMT</pubDate><category>Data Engineering</category><category>Architecture</category></item><item><title>CDC: Stop Reading What You Know Did Not Change</title><link>https://15x1976.neocities.org/en/writing/cdc-stop-reading-what-you-know-did-not-change/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/cdc-stop-reading-what-you-know-did-not-change/</guid><description>Reading everything again can be the right strategy. It becomes questionable when we know what changed and still pay to ignore that information.</description><pubDate>Mon, 03 Mar 2025 00:00:00 GMT</pubDate><category>Data Engineering</category><category>Data Architecture</category></item><item><title>The Data Warehouse Mistakes We Keep Repeating in the Data Lake</title><link>https://15x1976.neocities.org/en/writing/the-data-warehouse-mistakes-we-keep-repeating-in-the-data-lake/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/the-data-warehouse-mistakes-we-keep-repeating-in-the-data-lake/</guid><description>Moving from a Data Warehouse to a Lake does not automatically remove old constraints. If we copy every old decision without revisiting its purpose, we only relocate them.</description><pubDate>Tue, 18 Feb 2025 00:00:00 GMT</pubDate><category>Data Architecture</category><category>Data Engineering</category></item><item><title>The Medallion Model Is Not a Religion</title><link>https://15x1976.neocities.org/en/writing/the-medallion-model-is-not-a-religion/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/the-medallion-model-is-not-a-religion/</guid><description>Bronze, Silver and Gold are useful when each layer owns a responsibility. When data is copied only to satisfy the diagram, the pattern stops helping us think.</description><pubDate>Tue, 04 Feb 2025 00:00:00 GMT</pubDate><category>Data Architecture</category><category>Data Engineering</category><category>Databricks</category></item><item><title>Architecture Does Not End in PowerPoint</title><link>https://15x1976.neocities.org/en/writing/architecture-does-not-end-in-powerpoint/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/architecture-does-not-end-in-powerpoint/</guid><description>Architecture does not end when the diagram looks convincing. It earns its value through decisions, proofs, standards, implementation and operation.</description><pubDate>Thu, 23 Jan 2025 00:00:00 GMT</pubDate><category>Architecture</category><category>Engineering Culture</category></item><item><title>The Notebook Is Not the Application</title><link>https://15x1976.neocities.org/en/writing/the-notebook-is-not-the-application/</link><guid isPermaLink="true">https://15x1976.neocities.org/en/writing/the-notebook-is-not-the-application/</guid><description>A notebook can be an excellent interface without also owning configuration, secrets, business logic, orchestration and recovery.</description><pubDate>Mon, 06 Jan 2025 00:00:00 GMT</pubDate><category>Software Engineering</category><category>Data Engineering</category><category>Databricks</category></item></channel></rss>