Loading…
Latest reads
Every post, summarised
Grounded summaries of engineering blogs, newest first. Each links to the original.
- 4,671 posts
- 20 companies
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Latest posts
Frontend Engineering at Palantir: Engineering Multilingual Collaboration
Palantir describes the frontend work behind adding read-only translation mode to Dossier, a collaborative rich-text editor used in multilingual, restrictive environments where public translation services may be unavailable or disallowed. The design lets users choose source and target languages, view a complete document in translation, copy text, and add comments while routing requests through the in-house Language Model Service. Engineers extracted shared translation components, added a Redux state slice and per-element cache, chunked content by paragraphs and other blocks, and used Intersection Observer, batching, debouncing, and caching to translate visible content incrementally; edits invalidate affected translations and trigger retranslation. To preserve sentence-level quality, inline formatting is stripped before translation, so the current translated view is plain text. The resulting mode is available in every Dossier, translating content lazily as users scroll and updating translated blocks when collaborators edit the document.
Announcing Fin for Sales: A new role for Fin Customer Agent
Fin for Sales is a new role for Fin Customer Agent that handles inbound sales from initial engagement through qualification, routing, and conversion. It starts conversations across messenger and email, uses page context and smart suggestions, and applies playbooks, knowledge, enrichment, and memory to answer questions, handle objections, and personalize discovery. Fin qualifies prospects in real time by collecting details about use case, budget, fit, and timing, syncing structured context and conversation history to a CRM, and directing leads to sales teams or self-serve paths. It can book meetings through Chili Piper or Calendly, initiate trials or subscriptions, and hand off an AI-generated summary to representatives. The announcement reports early results including Fellow booking 18 previously unreachable meetings in January at around 48% conversion, while positioning Fin for Sales as part of a shared Customer Agent platform.
ClickHouse integrates with Lakehouse Runtime Catalog
ClickHouse 26.2 introduced a beta integration with Google's Lakehouse Runtime Catalog, enabling direct queries on Google Cloud Lakehouse Apache Iceberg tables without data movement or metadata syncing. The system communicates with Google Cloud Storage through the Iceberg REST Catalog endpoint at BigLake using Google Application Default Credentials for OAuth authentication. Users create a database using the DataLakeCatalog engine configured either with a local credentials JSON file or with explicit inline OAuth parameters. Once connected, analysts can query external Iceberg tables directly or ingest datasets into native MergeTree tables for repeated, low-latency workloads. Upcoming enhancements will add write capabilities for Iceberg tables and dedicated connection management tools inside the ClickHouse Cloud interface.
ClickHouse Cloud on Google Cloud Now Powered by Google Axion Processors: 30–55% Faster Queries, ~15% Fewer Compute Credits
ClickHouse Cloud transitioned its Google Cloud infrastructure from x86 N2D instances to Arm-based Google Axion C4A instances to resolve CPU throttling and performance ceilings under peak query loads. The migration leverages Axion's dedicated physical cores per vCPU, higher memory bandwidth, local SSDs, and improved thermal and clock frequency stability. In automated ClickBench testing across 100 million rows, every query in the 43-query benchmark improved by 30% to 55%, while data load times decreased by approximately half. A production analysis of 38 migrated customer services demonstrated an average 15% reduction in compute credits consumed per query across diverse production workloads. ClickHouse Cloud executed this rollout using automated validation checks, scheduled maintenance windows, and capacity coordination with Google Cloud.
Beyond the spreadsheet: How Databricks is delivering the modern CFO in financial services
Financial-services CFOs are being asked to act as Strategists and Catalysts, but fragmented legacy systems, T+1 batch processing, opaque reporting logic, and mismatched business semantics keep them focused on stewardship and retrospective operations. The proposed answer is Databricks as a unified, governed platform combining real-time streaming, centralized lineage, data and AI, with Unity Catalog, Lakeflow, Genie, and Agent Bricks addressing trust, latency, access, and model reproducibility. Unity Catalog can connect semantic definitions and end-to-end lineage from transactions through regulatory reports and models, while Lakeflow supports continuous ledger and liquidity processing. The post cites a global bank reducing liquidity-reporting processing from 10 hours to 8 minutes and Nationwide Insurance reporting a 5-point combined-ratio improvement and 3-point expense-ratio improvement. It presents a Lakehouse-based CFO stack as a shift from reporting historical results toward real-time capital management and previews AI-driven deposit and PPNR modeling.
AI App Development: Guide To Building AI-Powered Apps
Production-grade AI app development combines model orchestration, transactional state, governance, security, and live-data integration rather than only interface construction. The guide recommends defining users, outcomes, success metrics, timelines, and AI-relevant journeys, then shipping must-have features before enhancements. It evaluates builders by end-to-end support, technical audience, platform integration, code export, CI/CD, data connections, pricing, and deployment limits. For Databricks teams, it describes Databricks Apps, Declarative Automation Bundles, and Lakebase: serverless app compute, version-controlled deployment, and managed PostgreSQL with synced Unity Catalog Delta tables. It also recommends monitoring outputs, collecting correction feedback, refining prompts with automated evaluations, and governing models through MLflow, concluding that integrated infrastructure can leave teams focused on production AI workflows.
IoT in Manufacturing: Strategy, Components, Use Cases, and Challenges
IoT in manufacturing is presented as an operational architecture for collecting machine data, improving production and supply-chain visibility, and preventing equipment failures under strict latency, reliability, and safety requirements. The guide covers device selection, sensor placement, tiered sampling, edge-to-cloud pipelines, platform criteria, security, compliance, workforce training, and a phased deployment roadmap. Its technical split sends high-frequency vibration and acoustic signals to edge gateways for local processing while cloud systems support stateful analytics, predictive maintenance scoring, and model training; protocols such as MQTT, OPC-UA, AMQP, and Modbus are evaluation criteria. Reported examples include multi-factory OEE monitoring across more than 200 production lines, reducing reporting lag from 24 hours to under five minutes, digital twins for maintenance simulation, and IoT logistics routing. The action plan recommends starting with predictive maintenance and OEE monitoring on one line before scaling.
Multimodal Data Integration: Production Architectures for Healthcare AI
Production healthcare AI often depends on combining genomics, imaging, clinical notes, and wearables, but separate modality stacks can leave initiatives stalled before deployment. A lakehouse pattern addresses this by landing each modality in governed Delta tables under Unity Catalog controls while supporting cross-modal features, lineage, time travel, and reproducible training sets. Genomics processing can use Glow on Spark, imaging embeddings can feed governed tables and vector search, notes can become temporally aware entities, and wearables can flow through Lakeflow Spark Declarative Pipelines for streaming feature windows. The post compares early, intermediate, late, and attention-based fusion, matching them to dimensionality, temporal, and availability constraints, with late fusion presented as a practical baseline when modalities are missing. It argues that modality masking, sparse attention, and transfer learning are recommended responses because incomplete data is the default and connects the architecture to governed tumor board review, faster cohort assembly, and more clinical workflows.
Stop hand-coding change data capture pipelines
Hand-coded change data capture (CDC) and slowly changing dimension (SCD) pipelines become fragile as they handle out-of-order updates, duplicate events, deletes, late-arriving data, retries, backfills, and schema evolution. The post presents AutoCDC in Lakeflow Spark Declarative Pipelines as a declarative alternative: engineers specify keys, sequencing, delete conditions, and SCD Type 1 or Type 2 semantics while the platform manages ordering, state, deduplication, versioning, and incremental processing. Examples show a current-state table that keeps Mercedes’s latest city and removes deleted user 123, alongside a Type 2 table that preserves validity windows through __START_AT and __END_AT. The supplied comparison reports roughly 6–10 lines of declarative definition versus 40–200+ lines of custom logic, and says AutoCDC supports both change data feeds and snapshot-based CDC.
Supabase is now ISO 27001 certified
Supabase announces certification to ISO/IEC 27001:2022, covering its information security management system across Database, Auth, Storage, Realtime, Edge Functions, and the Data API. The post explains that ISO 27001 defines how an ISMS manages information risk through documented policies, processes, and controls, with certification awarded by an accredited third-party auditor after documentation review, interviews, evidence sampling, and control testing. Preparation included formalizing informal policies, documenting risk assessments, running internal audits, selecting an auditor, and mapping existing SOC 2 controls to ISO 27001 Annex A to avoid duplicate evidence collection. The certificate is valid for three years with annual surveillance audits, and Team or Enterprise customers can request it from their dashboard; the certification is presented alongside existing SOC 2 and HIPAA support.
Personalization Strategies for Media Companies
Media companies are expected to tailor content and messaging across channels, with personalization programs typically targeting lower churn, deeper sessions, and higher subscription revenue. The proposed foundation starts with an audit of CRM, email, warehouse, and customer data platform sources, followed by required-field definitions, ownership mapping, consent tagging, and ingestion-quality checks. Teams then map segment behaviors and conversion or retention paths, including negative signals, before selecting a CDP with real-time ingestion, identity resolution, unified profiles, segmentation, activation, and governance. Identity rules should connect anonymous and authenticated activity across web, mobile, and connected TV, while event-level streaming delivers messages through email, push, in-app, and advertising channels with minimal latency. The roadmap recommends an MVP comprising unified ingestion, a homepage recommendation surface, and triggered re-engagement email, with performance, churn, revenue lift, and model drift monitored through iteration.
A Modern AI Risk Management Framework
AI systems introduce probabilistic behavior, model drift, adversarial manipulation, bias, and auditability challenges that traditional IT risk practices may not address. The framework described combines NIST AI RMF, EU AI Act, and ISO/IEC 23894:2023, using Govern, Map, Measure, and Manage as its operational structure while recognizing regulatory and societal context. It recommends cross-functional governance, clear risk ownership, an AI-BOM covering systems, data flows, dependencies, and accountability, plus continuous measurement of fairness, explainability, data quality, security vulnerabilities, and harm likelihood and severity. Across the AI lifecycle, the text identifies risks including data poisoning, model drift, malicious library injection, prompt injection, hallucinations, and platform vulnerabilities, and points to the AI RMF Playbook for checklists, timelines, and governance artifacts.
Flow generation through natural language: An agentic modeling approach
Shopify built a tool-calling agent for Sidekick that converts natural-language requests into Shopify Flow workflows, addressing the cold-start problem by working backward from thousands of anonymized production workflows. The team generated synthetic queries and tool trajectories, fine-tuned Qwen3-32B, and changed Flow’s nested JSON DSL into an equivalent Python representation connected by a round-trip transpiler. Using Python improved syntactic correctness by 22 points and semantic correctness by 13 points on a 300-example benchmark, while matching production tool names, ordering, responses, and prompts proved essential to avoid degradation. Production evaluation exposed a 35% gap masked by benchmark parity, so Shopify built a weekly feedback loop that scores conversations, filters training data, identifies slice gaps, retrains, and deploys. The resulting agent serves most production traffic, runs 2.2 times faster at 68% lower cost, and outperforms closed models.
Using the ClickHouse MCP server with Google Antigravity
Google Antigravity integrates with the ClickHouse Model Context Protocol server to provide agent-driven analytics within the developer environment. Users install the server from Antigravity's MCP Store panel and authenticate via OAuth, granting the agent read-only access to organizations, services, databases, and tables according to account permissions. When prompted with natural language, the agent uses tools like get_services_list and list_tables to inspect schemas, translating user requests into functional ClickHouse SQL executed through the run_select_query tool. Antigravity can also generate interactive React charts as Artifacts, test UI interactions with screen recordings and screenshots in an integrated browser, and refine queries based on visual area comments. This setup allows engineers and analysts to explore datasets interactively without switching between external database clients and ticketing workflows.
How Yelp Keeps Server-Driven UI Consistent Across Four Platforms
Yelp maintains two major applications across Web, iOS, and Android, which previously led to fragmented server-driven UI implementations with mismatched backend component representations. To unify its server-driven UI framework, CHAOS, with its cross-platform design system, Cookbook, Yelp built an automated bridge library called Konbini. Konbini reads centralized JSON interface definitions through Jenkins pipelines to automatically generate synchronized libraries for Python, Kotlin, Swift, and TypeScript. These generated libraries handle component serialization on the backend and deserialization on client platforms. To maintain backward compatibility when component interfaces introduce breaking changes, client requests pass versioned spec identifiers, prompting the backend to execute migration methods that downcast newer component models to older supported versions.
Leveraging AI to build a faster iOS CI system
iOS continuous integration at Thumbtack previously required 30 to 40 minutes per pull request because every change triggered all 400 or more tests for an affected app. To solve node exhaustion and prepare for increased AI-generated code volume, the infrastructure team built Smart Test Selection. The system relies on a nightly pipeline that executes the full test suite with coverage instrumentation to generate a JSON map connecting source files to test classes. When a pull request opens, the pipeline looks up changed files in this map and runs only the relevant tests instead of the full suite. Built using Groovy, Ruby, and Bash, the tool reduces typical continuous integration time by approximately 50 percent while cutting documentation-only validation by about 90 percent.
Machine Learning Solutions: A Complete Implementation Guide
The guide presents machine learning delivery as a lifecycle problem, arguing that failures arise more often from planning, scoping, communication, and expectations than from algorithmic limitations. It recommends assessing data readiness before development by inventorying sources, checking quality and coverage, planning labeling, and engineering features. Once a measurable business outcome is defined, teams should match the learning paradigm and model complexity to the problem, establish cross-validation and holdout or temporal validation, and estimate compute and storage early. Baselines, reproducible experiments, deployment monitoring, model versioning, CI/CD, and retraining workflows support the transition from prototype to production. The guide also calls for representative proof of concepts and A/B testing or control groups to attribute business impact before scaling.
AI is approving our pull requests: Here’s how we made it safe
Intercom describes how it uses an AI PR review Agent to approve some pull requests amid a workflow where more than 93% are Agent-driven and engineers deploy hundreds of times daily. The system decomposes review into specialist sub-Agents that assess problem descriptions, intent alignment, safety, logic, best practices, and execution paths, while applying Intercom-specific guidance and enforcing smaller changes. In a pilot of more than 100 PRs, AI-approved changes had zero reverts and approval time improved 6–16 times at the 75th percentile; in four rollout weeks, 497 PRs went fully autonomous. Reported revert rates were lower for AI-authored than human-authored code in both backend and frontend comparisons, though the source says zero reverts will not necessarily persist. The process remains auditable, allows human review requests, and keeps the shipping engineer accountable for production behavior and rollback.
Data Governance Platforms: Evaluation & Feature Guide
This guide presents a framework for evaluating data governance platforms for enterprise deployment, distinguishing governance—the policies, roles, and controls for data use—from data management, the operational execution of those policies. It recommends assessing metadata-centered capabilities including continuous data profiling, catalog search and enrichment, end-to-end lineage, RBAC and ABAC, sensitive-data detection, masking, audit trails, compliance reporting, and data-subject request workflows. Vendor assessment should also cover pre-built connectors, REST APIs and SDKs, near-real-time metadata synchronization, schema-drift handling, cross-cloud federation, usability, support, implementation timelines, and three-to-five-year total cost of ownership. The proposed decision process selects three leading candidates, pilots them with representative structured and unstructured datasets, defines quality, lineage, adoption, and exit metrics, and uses executive review before procurement; governance is framed as an ongoing program that expands with AI workloads and regulatory change.
Introducing the Databricks Excel add-in for business users
Databricks has introduced the Excel Add-in, now in public preview, to let business users import and analyze lakehouse data directly in Excel without writing SQL or configuring ODBC drivers. Built on Databricks SQL and Unity Catalog, it provides point-and-click access to tables and metric views, native Excel pivot tables, refreshable results, reusable Workspace queries, and optional saved SQL. Metric views let data teams define business semantics once while Unity Catalog centrally manages permissions and controls, helping avoid duplicated logic and metric drift. The preview supports selecting tables and metric views, parameterized custom functions, manual refreshes, pivot-table filtering, query reuse, and workspace changes; scheduled refresh, AI integrations, and other usability improvements are planned next.
Top topics
- Architecture834
- Performance816
- LLMs660
- Machine Learning622
- Open Source563
- AI Agents553
- AI470
- Developer Experience448
Weekly digest
The best engineering reads, once a week.