Recommendation · MoneyYou need a syncing layer on top of MCP live lookups for anything you want to semantically question or go deeper into — sync a copy of the data locally into a vector database, which AI can build relatively easily. If you need any form of semantic lookup or analysis beyond a simple lookup — anything requiring looking across a vast data set — you have to sync a copy. Static, single-entity lookups (e.g., asking Stripe a question about a specific customer or taking a single action) can remain live MCP calls.
AI Engineer · Why Your Company Needs a Context Graph (and How to Build It) — Gil Feig, Merge
Recommendation · MoneyPedro Lopez recommends OAuth for authenticating the MCP server itself: a connect button spins up the OAuth flow where the user signs in and accepts privileges.
AI Engineer · Designing CLIs for Agents, Not Humans — Pedro Lopez, Airbyte
Recommendation · MoneyAfter trial and error, Pedro Lopez's team keeps tool counts small, exposing only describe (schema for querying) and execute (read/write/delete) for connector execution.
AI Engineer · Designing CLIs for Agents, Not Humans — Pedro Lopez, Airbyte
Recommendation · MoneyPedro Lopez recommends exposing CLI inputs through flags, environment variables, and config files instead of interactive prompts, so setup can happen out of band.
AI Engineer · Designing CLIs for Agents, Not Humans — Pedro Lopez, Airbyte
Recommendation · MoneyAnders Swanson recommends using a database for the memory layer rather than building your own database on top of files: building a memory layer on files leads to building your own database, so you could just use a database instead. With one database query connection in a multi-model database, you can do hybrid search and return the data back.
endorsed
AI Engineer · From Context to Memory: Your Agents Need a Real Memory Layer — Anders Swanson, Oracle
Recommendation · MoneyAnders Swanson recommends choosing a multi-model database for the memory layer so rows, columns, vector embeddings, full text search, relational entities, graphs, episodes, and facts live in one consolidated place.
endorsed
AI Engineer · From Context to Memory: Your Agents Need a Real Memory Layer — Anders Swanson, Oracle
Recommendation · MoneyViren Baraiya recommends that for payments you use a very well-defined deterministic workflow rather than non-deterministic agent behavior. Similarly, for an agent harness responsible for monitoring production deployment and managing Kubernetes clusters, define a very well-defined workflow for the sequence of steps to execute when restarting a cluster, so that every cluster restart is exactly the same. The harness should deliver determinism when it matters.
AI Engineer · Brains vs Hands: How to Run AI Agents Safely in Production — Viren Baraiya
Recommendation · MoneyViren Baraiya recommends that restarting a production cluster should require a human gate: send a Slack message to somebody saying 'I'm going to restart this cluster, do you think it's okay to do that or not?' He does not want this to be left to a hallucination by an LLM — execution guarantees must be deterministic, not left to an LLM deciding it doesn't need to do it.
AI Engineer · Brains vs Hands: How to Run AI Agents Safely in Production — Viren Baraiya
Recommendation · MoneyGabriel Martinez recommends that engineers read the code and test the behavior themselves rather than accepting output, own the trade-offs of the code they merge, and notice the missing requirements and decide whether a thing deserves to be part of the system. He also recommends not merging code you don't fully understand or haven't tested yourself.
Creator advice attributed to Gabriel Martinez.
AI Engineer · Generation Is Cheap, Review Is Expensive: How to Stop Shipping AI Slop — Gabriel Martinez, G2i
Recommendation · MoneyGabriel Martinez recommends spending time thinking about guardrails for agents, coding conventions, architectural styles, and constraints around how the system should be shaped. He frames this as fighting slop with conventions, standards, documented flows, small reviewable surfaces, and clear ownership boundaries and definitions of done.
Creator advice attributed to Gabriel Martinez.
AI Engineer · Generation Is Cheap, Review Is Expensive: How to Stop Shipping AI Slop — Gabriel Martinez, G2i
Method · MoneyPostman built an API context graph by: (1) identifying and cataloging every single microservice on production, (2) identifying every endpoint exposed by each REST API service, (3) capturing how each endpoint is implemented right down to the exact line of code, (4) mapping how each service talks to each other and how each endpoint connects to every other endpoint, (5) tracking how data flows all the way down across the stack including databases and caches, (6) identifying how applications like front-ends, CLIs, and APIs interact with the back-end architecture, and (7) indexing all of this data using an LLM to produce a centralized and effective context graph layer.
endorsed
Method, not a verified protocol.
AI Engineer · We Mapped 115 Microservices for Our Coding Agents — Kamalakannan Nandagopal, Postman
Method · MoneyWhen a PR is created, the agent reviews it and posts issues and inline comments; it also analyzes CI failures and posts a summary of root causes, being particularly good at catching flaky tests; the agent can automatically fix code review issues and CI failures, and can be set up to automatically loop until all issues in a PR are fixed, producing a green PR ready to merge.
Method, not a verified protocol.
AI Engineer · AI Writes More PRs. Who Validates Them? — Ali-Reza Adl-Tabatabai, Sonar
Recommendation · MoneyWill Lyon recommends running agent messages (user and assistant) through an entity extraction process that identifies entities and how they are connected, converting unstructured data into a knowledge graph.
AI Engineer · Turning Agent Memory Into Skills That Work — Will Lyon, Neo4j
Recommendation · MoneyWill Lyon recommends distilling a workspace- or project-scoped context graph into a skill grounded in actual observed data rather than just a markdown file, with deterministic, well-understood procedural steps in the graph.
AI Engineer · Turning Agent Memory Into Skills That Work — Will Lyon, Neo4j
Recommendation · MoneyWill Lyon recommends a knowledge graph with strong types and relationships describing how entities are related, and stresses that the entity resolution phase — ensuring a canonical representation of a thing, like knowing Dr. Nguyen is a provider with a name and role — is one of the most important parts of building the graph.
AI Engineer · Turning Agent Memory Into Skills That Work — Will Lyon, Neo4j
Method · MoneyMatt Gibiec describes a workflow: start by observing your environment to build context and dependency mapping; provide production data and details locally to developers as they test; when a service deviates from normal (slower or throwing new errors), inform the developers' agents in the IDE; integrate the tooling in the code repository so it has context of what changed, and overlay change data with issue data to attribute issues to pushed changes or unsuccessful merges; when issues are detected, suggest a fix that uses the context of your environment, application, and monitored agents — not just a fix for the particular breaking issue; and drive the entire SDLC by providing the fix while giving you control at the end to decide whether to push the feature or fix out.
Method, not a verified protocol.
AI Engineer · Your AI Agent Has No Nervous System — Matt Gibiec, Dynatrace
Recommendation · MoneyMatt Owens recommends putting yourself in a fast-growing environment shortly after school — a small startup where you can hire, collaborate, and learn from designers, developers, and business people all figuring it out together. He describes working 14 hours a day at Method 5, a startup that grew from 7 to 45 people in about a year and a half, calling it a 'pressure cooker' that was a blessing after grad school.
Design Better · Matt Owens: Athletics co-founder on keeping your creative fire lit
Method · MoneyThe described memory-learning system works as a loop: when an agent runs, its context is loaded from a context hub (instructions, skills, markdown files, policies, rules). When the agent is invoked, a trace is produced showing failed tool calls, user corrections, and deviations such as tone straying from the desired tone. An engine then looks for patterns in those traces and identifies where static skill markdown files in the context hub need to be changed or promoted, and makes that change. After the memory update process runs, the next time the agent runs its tone visibly changes in interactions with users.
described as the speaker's system; behavior change observed by the speaker, not benchmarked
Method, not a verified protocol.
AI Engineer · Giving AI Agents Memory That Learns — Jake Broekhuizen, LangChain
Recommendation · MoneyAn important consideration in self-updating agents (like OpenClaw and Hermes) is deciding what to make self-updateable versus what needs human review. Procedural memory — instructions, policies, and tone guidelines — probably drives about 75% of an agent's behavior, so changes to it should be surfaced to a human before being committed to the agent's hot reload path.
the 75% figure is the speaker's own estimate for his agent, not a measured benchmark
AI Engineer · Giving AI Agents Memory That Learns — Jake Broekhuizen, LangChain
Recommendation · MoneyWhen tools return large data (logs, database results): externalize by moving big data to persistent storage with a memory pointer, select by retrieving only what is relevant, and compress by summarizing/compacting information.
AI Engineer · Why Bigger Context Windows Won't Save Your Agent — Elizabeth Fuentes Leone, AWS