QCon Software Development Conferences (@QCon) header
QCon Software Development Conferences (@QCon) profile picture

Uncover emerging trends and practices from the world’s most innovative software professionals to help you validate your software roadmap. Celebrating 20+ years.

Joined March 2008
Batch APIs can look attractive for background agent workloads, but batch latency applies to every request. Meryem Arik, Co-Founder and CEO at Doubleword, on why an agent with 20 to 30 sequential prompts can take 20 to 30 days end to end.
1
59
LinkedIn's first approach to agent memory had each application identify and store its own signals. Every new use case needed another bespoke integration. Karthik Ramgopal, Distinguished Engineer at LinkedIn, on why the memory layer had to become shared infrastructure.
2
1
66
How does Pinterest serve vision-language models efficiently? Salina Wu and Cristian Lopez will discuss their NVIDIA Dynamo stack at QCon AI New York, Dec 15–16. See the schedule: buff.ly/JysYDJz
1
1
106
Pinterest's session covers disaggregated inference, KV-aware routing, and cache offloading for multimodal workloads. Datadog will examine how it cut cost per AI interaction to one-third while maintaining quality and latency.
1
27
LinkedIn will share server-side guardrails and peer approvals for an operations agent supporting a Kubernetes platform spanning 500,000+ nodes. The two-day program also provides time between sessions to compare implementation choices.
25
LangChain enforces six distinct rules around lazy imports, at different levels of the repository, and very little of that is documented in one place.
1
80
Jeff Smith, CEO & Co-Founder at Neoteny AI, on why a coding agent working from general model knowledge can't know the rules that make a PR mergeable.
1
27
A registry turns agents into owned, versioned artifacts before governance adds controls. Sahil Vashishat explains BlackRock's build order at QCon AI New York. Read the abstract: buff.ly/gvlgCiS
1
62
The stack was built in dependency order: a shared model interface, then evals and guardrails, a common representation for canvas and SDK, an agent registry, governance, and a skills hub.
1
30
The registry makes agents owned, versioned, deployable artifacts. Governance adds authorization, audit, and kill switches. Episodic and procedural memory remain separate because they carry different verification and privacy boundaries.
33
Agent reasoning loops can keep running without a useful result while the inference bill grows. Meryem Arik, Co-Founder and CEO @Doubleword_, on a simple production guardrail: set a cost ceiling per task and flag anything that crosses it.
1
125
The instinct when building agent memory is to preserve everything. It doesn't scale. Karthik Ramgopal, Distinguished Engineer at LinkedIn, on why the harder problem is deciding what deserves to be remembered and when information is no longer worth keeping.
1
92
Easier code generation doesn't remove production ownership. Suhail Patel hosts QCon San Francisco's track on verification, code review, and who operates what gets built. Explore the track: buff.ly/0wHN3ta
1
1
1
1
93
The track examines builder-driven agent development, brownfield judgment, code review, verification when humans cannot read every generated change, and ownership when more people can code.
41
Repo-specific fine-tuning doesn't necessarily require a frontier-sized model or an enormous evaluation budget. Jeff Smith, CEO & Co-Founder at Neoteny AI, on Allen AI's SERA approach, which uses softly verified execution to cut evaluation costs during training.
1
121