Abdul Samad SiddiquiSenior AI Engineer · Karachi

Field notes

Blog

Working notes from the parts of the job that are not demo-shaped: agent reliability, retrieval, evaluation, and the infrastructure underneath.

  1. A set of document fragments connected through a small knowledge graph, with one path highlighted from a question to its supporting sources.

    When GraphRAG earns its extra complexity

    Vector search finds similar passages. A graph can connect people, events, and dependencies across many passages. The useful question is when you need both.

  2. A large task block split into separate isolated context cards running side by side, with a shared state file below and a separate reviewer card checking the merged output.

    Why long tasks need workflows, not longer contexts

    A task that fails in one long conversation often succeeds when it is split into isolated subagents with explicit success criteria, external state, and an independent reviewer.

  3. Diagram of tokens flowing into a usage meter with a rising needle, connected to a bar chart labeled infrastructure bill.

    The meter is on, AI is becoming infrastructure spend

    AI assistants were sold as flat subscriptions, but long-running agents have variable inference cost. GitHub's move to usage-based Copilot billing is a sign AI spend is becoming cloud spend, here's how to budget for it.

  4. A grid of closed drawers representing an agent's tool library, with three drawers highlighted and pulled toward a magnifying glass feeding a small loaded-context window.

    More agent tools, less context with defer_loading

    Loading every tool definition upfront wrecks tool recall once an agent has more than a handful of tools. Anthropic's defer_loading keeps tools discoverable without bloating context, here's when it's worth using.

  5. Diagram of two cursors sending labeled insert and delete operation strips across dashed lines to a central sequencer that orders and transforms them.

    Collaborative editing works because changes become operations

    Last-write-wins and locking both fail for real-time text collaboration. The fix is turning every keystroke into an operation the server can order and transform, here's how, and what it isn't.

  6. A hand-drawn map with three dashed routes converging on a terminal window icon marked GSoC and open source.

    The third way I found into Google Summer of Code

    The usual advice for getting into GSoC is "have a strong profile" or "contribute for months first." I had neither, here's the third route that worked for me.

  7. Three parallel diagram lanes labeled deterministic code, LLM rubric and multimodal, showing a checkmark gate, a scored rubric sheet, and a camera-and-text extraction pipeline.

    Production evals are three systems, not one

    Treating evals as one pipeline is why they're slow and expensive. Splitting deterministic checks, LLM rubric judges, and multimodal extraction into three systems is what I run in production.

  8. Three side-by-side technical diagrams showing cache penetration, cache stampede and cache avalanche as distinct failure paths from client to origin database.

    Three Redis failures that look similar until production

    Cache penetration, stampede and avalanche all look like "Redis fell over," but each has a different cause and a different fix. Here's how to tell them apart.

  9. Line drawing of a faceless hotel doorman under a canopy, with suitcase, umbrella, clock and key icons orbiting his head on a dashed line.

    The doorman fallacy in AI strategy

    Rory Sutherland's doorman fallacy explains why AI rollouts that only automate the measurable part of a job keep backfiring, and what CBA's reversed layoffs show about it.

  10. A line-art test bench showing eval cases fed through an agent run into pass and fail gates, with a regression marker on one lane.

    Why I run evals before every agent deploy

    A small, representative eval baseline in CI catches the regressions that manual spot-checking misses. Here is how I size the set and what I actually measure.

  11. Abdul Samad seated in graduation robes with his cap covering his face, set against a muted paper collage of code marks and node diagrams.

    Four years of showing up

    I started university without a laptop and without knowing what a folder was. This is what the four years to a software engineering degree actually felt like.

  12. A balance scale weighing a valuation weight against a stack of compute cost blocks, beside two meters reading run-rate and recognized revenue at different levels.

    A valuation is not a profit statement

    Anthropic's Series H numbers got read as proof of profitability. Private valuation, run-rate revenue, recognized revenue, margins and compute subsidy are five different things.

  13. Three labelled cache drawers for application data, prompt prefixes, and final responses, connected to a simple language model pipeline.

    The three caches in a production LLM system

    Application data, repeated prompt prefixes, and final answers behave differently. Treating them as one cache creates stale replies and hides the real cost of an AI product.