AI Engineer · August 3, 2026

Building Turbopuffer: Gergely Orosz (@pragmaticengineer ) × Simon Eskildsen (CEO)

Building Turbopuffer: Gergely Orosz (@pragmaticengineer ) × Simon Eskildsen (CEO) video thumbnail
Why it matters

Gergely Orosz and Simon Eskildsen discuss the engineering decisions behind Turbopuffer, from dependency failures at Shopify to the economics of search infrastructure. Eskildsen explains using Toxiproxy to exercise real database connections under faults, checking performance assumptions against hardware limits, and combining object storage with faster storage tiers. The conversation connects infrastructure design with product costs and operational experience.

My takeaway: Write down how an application should degrade when dependencies fail, then test through real drivers. Compare measured latency and cost with hardware-based estimates before committing to a search architecture.
Keep exploring

More curated notes connected through AI Engineering.

Google Cloud Security Blog · tool

Now in preview: Find and fix software vulnerabilities with CodeMender

Google opened a preview of CodeMender, an AI code-security agent delivered through Gemini Enterprise Agent Platform and AI Threat Defense. It is designed to inspect code, identify and validate potentially exploitable defects, and produce targeted fixes, with Google’s specialized Gemini 3.5 Flash Cyber model initially restricted to governments and trusted partners.

AWS Security Blog · guide

Transforming Bedrock Guardrails events into OCSF with CloudWatch

AWS provides an implementation guide for a Lambda pipeline that converts Bedrock Guardrails intervention logs into OCSF Detection Findings in the CloudWatch unified data store. It includes field mapping and queries that correlate guardrail events with identity and network activity.

Google DeepMind Blog · framework

Piloting the world's first double-blind AI evaluations

Google DeepMind, Singapore's AI Safety Institute, OpenMined, AVERI, and MLCommons are piloting an external evaluation in a confidential-computing environment. The evaluator's hidden tests and Google's Gemini Flash Lite weights remain private from one another, reducing benchmark contamination without transferring either sensitive asset.