Kevin Denman

2.1K posts

Kevin Denman banner
Kevin Denman

Kevin Denman

@kcdenman

building https://t.co/1MXXugJgNH

California, USA Katılım Ekim 2011
528 Takip Edilen448 Takipçiler
Kevin Denman
Kevin Denman@kcdenman·
Thanks @grinich I’ve been looking for more writings like this. Agentic coding (and many other AI agent use cases) have fundamentally shifted working patterns in tech. Product engineering is a really succinct way to take two roles that used to be decoupled and show how AI Agents can now enable one person to address the full spectrum of product and engineering in a single role.
English
0
0
1
76
Nathan Baschez
Nathan Baschez@nbaschez·
AI pretty much obliterates the way tech companies organize teams to build products What teams have figured out the new way? We got the agile manifesto 25 years ago, who is writing this for the AI era?
English
14
2
66
11.7K
Kevin Denman
Kevin Denman@kcdenman·
@shl Agentic coding makes this possible. @AgentGraphAI thesis is that elite agentic engineers with proper context can outcompete large implementation teams. Let’s go!
English
0
0
0
46
Sahil Lavingia
Sahil Lavingia@shl·
1 engineer > 2 engineers
Nederlands
88
23
404
34.5K
Kevin Denman
Kevin Denman@kcdenman·
I could not emphasize this enough to builders. I’m about 3000 hours in to agentic coding. If your product (API / CLI / MCP / Docs / Templates) can’t talk to my agents it won’t get into the stack. Edge cases: writing C++ directly on Ethernet cables to optimize AI throughput
Aakash Gupta@aakashgupta

Karpathy is telling you something most product teams haven’t internalized yet. The new distribution channel for software is agents. Agents don’t browse your marketing site, watch your demo video, or click through your onboarding flow. They call your CLI. They hit your MCP server. They read your docs programmatically. If none of those surface areas exist, your product is invisible to them. Look at how fast this moved. MCP went from zero to 97 million monthly SDK downloads in twelve months. 10,000+ active servers. OpenAI, Google DeepMind, Microsoft, and Cloudflare all adopted it. By December 2025, Anthropic donated MCP to the Linux Foundation because the standard had already won. Running an MCP server is now compared to running a web server. That’s the new baseline for product discovery. 85% of enterprises are expected to have AI agents deployed. Those agents need structured, programmatic access to your product. They need CLIs, MCP endpoints, and machine-readable documentation. A beautiful React dashboard is worthless to an agent trying to pull data into a workflow at 3am. This tells you everything about why Karpathy’s framing of CLIs as “legacy” technology is so precise. Legacy means battle-tested, standardized, universally parseable. stdin/stdout, flags, JSON output. The entire Unix philosophy was accidentally designed for AI agents decades before they existed. Your competitor ships an MCP server and suddenly every Claude Code user, every Cursor session, every autonomous workflow can discover and use their product. No human ever visits the website. No sales call. No onboarding email. The agent just finds the tool and starts using it. The companies that win the next 24 months are the ones building agent-accessible surface area right now. The ones that lose are still optimizing their landing page above the fold.

English
4
0
3
86
Charly Wargnier
Charly Wargnier@DataChaz·
This is huge. You can now run Claude Code for FREE 🤯 Thanks to @ollama’s Anthropic API compatibility, you can: → run Claude Code locally → plug in open-source models → keep full agent + tool workflows Running on open-source LLMs via Ollama. Link in 🧵↓
Charly Wargnier tweet media
English
80
215
1.9K
208.7K
Kevin Denman
Kevin Denman@kcdenman·
@tom_doerr Can this be added on to an existing memory system for the learning capability or are you required to implement it as the core memory architecture
English
0
0
2
1.2K
Kevin Denman
Kevin Denman@kcdenman·
👍 agree with you here The idea that advanced technology is going to create generation of less capable people is short sighted. This has never happened- ever. Advanced technology, like LLMs and Coding agents, will be the tools that are used to build incredible things and the “mental models” will be very human indeed
English
0
0
2
40
em
em@matnewera·
@Prathkum counterpoint: a new generation will show up who can debug across 10 languages simultaneously because they never had to memorize syntax in the first place. the mental model evolves, it doesn't disappear
English
1
1
6
128
Pratham
Pratham@Prathkum·
A new generation of developers will show up who can’t debug their own logic because they have outsourced their entire mental model to an LLM.
English
263
62
1K
48.3K
Boardy
Boardy@boardyai·
@rauchg discontinuity is a fancy word for "we're all getting replaced" but hey, 20% cheaper automation
English
2
0
2
1.8K
Guillermo Rauch
Guillermo Rauch@rauchg·
We're introducing 𝚜𝚔𝚒𝚕𝚕𝚜 – the "npm" of AI skills. Excited to see an open, agent-agnostic ecosystem of skills flourish. To get started, try: ▲ ~/ npx skills i vercel-labs/agent-skills
Guillermo Rauch tweet media
English
231
407
5.6K
725.6K
Kevin Denman
Kevin Denman@kcdenman·
Why these words? I think “scroll animation” is part of the web design vernacular. Those working in tech don’t realize how much of a moat there still is around industry specific terminology The curious kind will first ask the model to educate them on terms and then start using the terms to instruct the coding
English
0
0
2
225
Prajwal Tomar
Prajwal Tomar@PrajwalTomar_·
I replicated a $5K scroll animation inside Cursor in 10 minutes. People keep saying AI can’t replace designers. That might be true for big companies with huge teams and complex design systems. But if your goal is to ship an MVP fast, Gemini 3 or Opus 4.5 is MORE than enough. I one-shotted a landing page with a scroll animation agencies charge thousands for. Here’s the exact process I used ↓
English
55
117
1.5K
1.3M
Kevin Denman
Kevin Denman@kcdenman·
Great read. So who’s building some good tech to index and analyze trace data? I’m using @mastra to write the traces to memory and I have users providing direct feedback at the thread/message level, but I still need a way to visualize traces, cluster them, and ultimately identify how to generate GitHub issues that provide enough detail to become evidence-based value-added PRs
English
0
0
0
26
Dev Shah
Dev Shah@0xDevShah·
1 in every 5 founders I meet in the Bay Area is building an observability platform for agents. There are so many observability platforms, yet the least mature part of building an agent is still telemetry. Everyone is trying to solve the wrong problem with observability. Visibility is the easiest piece. The hard part is analyzing and understanding what you’re observing. I’ve spoken to teams recording 100k+ traces every single day. What are they doing with those traces? Literally nothing. Because it’s impossible to read and summarize 100,000 traces at any human scale. So stop vibecoding those stupid dashboards, and how about you re-center the problem from first principles?
English
150
70
1.6K
163.4K
Kevin Denman retweetledi
Boardy
Boardy@boardyai·
@pmarca @wabi everyone can build but nobody wants to maintain
English
2
1
18
576
Niels Rogge
Niels Rogge@NielsRogge·
Both Anthropic and Cursor realized, "filesystem is all you need" (alongside bash) The filesystem enables "dynamic context discovery". Instead of bloating the context window with a huge amount of tokens before the agent starts doing any work, the agent loads them "just-in-time"
Niels Rogge tweet media
English
30
35
533
34.4K
Kevin Denman
Kevin Denman@kcdenman·
I find this n8n vs LangGraph comparison very helpful. If you are building agentic apps, you need a LangGraph-like framework. It you are building a bunch of integration for make existing apps agentic, a visual workflow builder is probably enough.
Shraddha Bharuka@BharukaShraddha

Everyone is building AI agents. Very few understand the agentic frameworks that actually power them. In 2025, two frameworks dominate agent development — not as competitors, but as complementary layers: n8n — Visual Workflow Automation What it does • Visually connects AI agents with business tools and APIs • Flow: Trigger → AI Agent → Tools → Action • Removes integration complexity and speeds up deployment Think of it as: The orchestrator that plugs AI into your entire tech stack — LangGraph — Graph-based Agent Orchestration (LangChain) What it does • Enables stateful, cyclical, multi-step agent workflows • Flow: State → Agents → Conditional Logic → State (loops) • Designed for complex reasoning and coordination Think of it as: The brain managing advanced agent decision-making — When to use n8n • AI + business tool integrations • Customer support and ops automation • No-code or low-code workflows for teams • Fast shipping with 700+ integrations When to use LangGraph • Multi-agent reasoning systems • Enterprise-grade AI applications • Cyclical or long-running workflows • Fine-grained state control and memory — Ecosystem strengths n8n • Visual builder for non-developers • Self-hosted, open-source option • Strong business automation community LangGraph • Deep LangChain integration • LangSmith for observability and debugging • Advanced state persistence and control — The real insight 👇 The best AI systems use both. n8n → Visual orchestration and tool integration LangGraph → Agent logic, reasoning, and state Think in layers: business automation and intelligent decision-making — Your turn 👋 What would you build first? A visually simple, tool-connected agent (n8n)? Or a deeply orchestrated, reasoning-heavy agent (LangGraph)?

English
0
0
1
77