Sep 8, 2026 / Engineering A Shopify 3PL integration looks simple on a whiteboard: orders go out to the warehouse, tracking comes back, inventory stays in sync. In production it is where the most expensive commerce bugs live, because three systems disagree about the same physical pallet and the customer sees the disagreement first. This post lays out the integration patterns that hold up: using the FulfillmentOrder API instead of the legacy fulfillment model, deciding which system owns inventory truth, handling partial and split shipments, and treating tracking and inventory updates as event streams that will drop and duplicate. It covers the build versus connector decision honestly, and the failure modes (oversell, stuck fulfillments, ghost inventory) that separate a demo from a warehouse that ships on time.
Sep 8, 2026 / Engineering Shopify metafields are how you extend Shopify's data model without leaving the platform, and in a headless build they are the difference between a storefront that can express your catalog and one that is fighting the schema. The trouble is that teams reach for metafields as a dumping ground, scatter untyped key value pairs across products, and end up with data no query can trust. This guide covers the modeling decisions that actually matter in 2026: metafields versus metaobjects, why definitions and typed validation are not optional, how to structure data so a headless frontend can query it cleanly, and the mistakes (untyped values, reference sprawl, and treating metafields as a database) that make custom data a liability instead of an asset.
Sep 8, 2026 / Engineering Most Shopify QuickBooks integrations fail for the same reason: they treat the accounting system as a mirror of the storefront instead of a ledger with its own rules. Push every order in as an invoice and you get a QuickBooks file that no accountant trusts and no reconciliation ever balances. This post lays out the three ways teams connect Shopify to QuickBooks Online in 2026, the data model mismatch that causes most of the pain (orders are not invoices, payouts are not payments, and refunds are not deletions), and the API patterns that keep the two systems agreeing. It covers the prebuilt app route, the iPaaS route, and the custom build route, with an honest read on when each one is the right call and what each one costs you in fidelity, control, and maintenance.
Sep 8, 2026 / Engineering Migrating from WooCommerce to Shopify Plus is not a data export followed by a data import. It is a translation between two philosophies: a self hosted WordPress plugin where everything is a post in MySQL and every behavior is another plugin, and a hosted platform with an opinionated data model and a fixed checkout. The migrations that fail treat it as a file copy and discover too late that URLs changed, that a critical plugin has no Shopify equivalent, and that subscription customers silently stopped billing. This playbook walks the WooCommerce specific parts that actually decide the outcome: mapping the WordPress data model, preserving search rankings through redirects, achieving plugin parity, migrating the payment gateway without losing tokens, and running a cutover that does not drop orders.
Sep 7, 2026 / AI Tooling
SpaceX closed its 60 billion dollar all stock acquisition of Anysphere, the maker of Cursor, in mid August 2026, and within days Cursor shipped Origin, a code hosting platform built directly into the editor. Origin is not trying to be GitHub. It is a git host designed for the way AI agents actually use a repository: constant cloning, pushing, and parallel branches that collide and need merging. The early beta ships four pieces, repositories, pull requests, code browsing, and GitHub sync, and it is built on rearchitected technology from Cursor's December 2025 acquisition of Graphite. For teams already living inside Cursor with agents running most of the day, keeping the repo where the agents work removes a real seam. It also raises a real question, because your source now syncs into infrastructure owned by SpaceX, and the data terms are new. This post covers what Origin does, how it stacks against GitHub, and the trade you are actually making.
Sep 7, 2026 / Headless Commerce
The Shopify community spent 2026 arguing about a word. Hydrogen, Shopify's framework for custom storefronts, is marketed as headless commerce, but a growing number of developers push back that it is something narrower: frontend flexible, Shopify native commerce. The distinction is not pedantry, it decides whether a Hydrogen build gives you what you actually wanted. The part most people miss is that going headless with Shopify does not decouple you from Shopify. Checkout, payments, and the commerce engine stay exactly where they were. What you buy is control over the frontend, not platform independence. In 2026 Hydrogen runs on React Router v7 with Vite, and Shopify has even opened it to run on other stacks including Next.js, which sharpens the question rather than settling it. This post separates what Hydrogen headless genuinely delivers from what the label implies, and gives you a decision framework for when that trade is worth making on a Plus build.
Sep 7, 2026 / AI Infrastructure
MiniMax M2.5 is the open weight coding model that made the closed frontier explain itself. It is a 230B mixture of experts with only 10B active parameters per token, and it scores 80.2 on SWE-Bench Verified, which lands within 0.6 points of Claude Opus 4.6 at 80.8. It also takes first place on Multi-SWE-Bench at 51.3, so the multilingual result is not a fluke. The weights are on Hugging Face, and hosted access runs around fifteen cents per million tokens, roughly a tenth of what a frontier closed model costs to run at volume. That combination, near frontier coding at open weights and a fraction of the price, is the reason M2.5 keeps showing up in build versus buy conversations. This post reads the benchmarks honestly, explains what the 10B active design does to your serving costs, and lays out where an open weight model like this belongs in a real stack and where it does not.
Sep 7, 2026 / AI Infrastructure
Perplexity open sourced Lily, the local inference engine it built for hybrid compute in Perplexity Computer, and the numbers are worth a close look. Lily is a single process runtime: a Rust layer loads the checkpoint and drives the generation loop, hand written Metal kernels execute the model, and an OpenAI compatible endpoint streams tokens. It is specialized, not general. It runs one model family, Qwen3.6-35B-A3B, and it treats prompt prefill and token by token decode as two different workloads with different bottlenecks. On an M5 Max MacBook Pro, Perplexity reports 1.23x higher prefill throughput and 1.35x higher decode throughput than MLX-LM, with output quality effectively unchanged. That is a real gain from specialization on the same hardware. This deep dive reads the benchmark, explains why splitting prefill and decode buys that much, and shows where a narrow engine like Lily belongs next to a general runtime like MLX-LM.
Sep 7, 2026 / AI Tooling
SWE-Bench asks a model to produce a patch that passes tests. Terminal-Bench asks an agent to sit at a terminal and actually get the job done: compile the code, train the model, fix the broken environment, verify the result. That difference in framing is why the two benchmarks rank agents differently, and why Terminal-Bench has become the number people quote when they argue about which coding agent to run. On Terminal-Bench 2.0 the frontier now clears the high 80s and low 90s, but the score hides most of what matters. The benchmark measures a scaffold plus a model, not a model alone, so the same model can move ten points depending on the harness around it. This post explains the task design, reads the current 2026 leaderboard, and shows how to weight the number against your own stack rather than treating it as a single ranking of raw model strength.
Sep 6, 2026 / AI Infrastructure
Both Claude Code and Cursor now let you run several coding agents at once, and the marketing makes them sound interchangeable. They are not. Cursor 3 spawns up to eight agents, each in its own git worktree on a separate branch, so the isolation happens at the filesystem. Claude Code Agent Teams runs multiple model instances that a lead session coordinates, assigning subtasks and merging results, with isolation happening in each agent's context window. That difference decides which work parallelizes cleanly on each tool, how you avoid agents clobbering each other, and where the coordination overhead eats your throughput gains. This post breaks down the two parallelism models, the honest speedups you can expect, and a rule for when parallel agents are worth the orchestration cost at all.
Sep 6, 2026 / AI Infrastructure
On June 2, 2026, Cognition renamed Windsurf to Devin Desktop and pushed it as an over the air update, no reinstall, no migration wizard, settings ported automatically. The surface change is a name and a logo. The real change is strategic: Windsurf was a standalone agentic IDE, and Devin Desktop is now the local half of a lineup whose other half is the cloud Devin agent. That framing, one desktop IDE plus one autonomous cloud engineer sharing a brand and increasingly a protocol, is what the rebrand is actually about. This post separates what changed from what did not, explains how the Agent Client Protocol fits, and places Devin Desktop against Cursor and Claude Code so you can decide whether the rename means anything for your team.
Sep 6, 2026 / AI Infrastructure
Meta released Muse Spark 1.3 on September 2, 2026, and it lands in the top ten of the Artificial Analysis Intelligence Index while charging 1.25 dollars per million input tokens and 4.25 per million output. That is a small fraction of what GPT-6 Astra and Claude Opus 5 cost, and the model posts near perfect retrieval on a million token context where most competitors fade into the 60s and 70s. The catch is that a headline intelligence rank and a cheap sticker price do not tell you where a model belongs in a production stack. This post works through the real numbers: the pricing tiers including the contributor discount that trades your data for a lower rate, the long context retrieval results, and the agent benchmarks where Opus 5 still leads. The point is not that Muse Spark 1.3 is the best model. It is that at this price it changes which jobs you should stop paying a frontier rate for.