Загрузка видео...

Не удалось загрузить видео

На главную

Autonomous Engineering Pipelines are incredibly powerful, but how do you actually build one? The hard parts aren't the agent, they're the plumbing: - Orchestrating triggers across Slack, GitHub, Linear, DataDog, Sentry, and other services. - Duplicate detection - Long-term memory - Noise filtering: deciding which messages actually need investigation...

dabit3's profile picture

nader dabit

189,784 subscribers

84,120 просмотров • 1 месяц назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

INSANE: Cursor + MCP just built a customer-requested feature end-to-end!! Our customer sent us a slack message requesting for a feature. Cursor read this, built the feature and created a Pull Request, all on its own! Here's how you can set it up, - Go to Composio's MCP directory - Search for Slack and Github, copy the sse url - Complete Auth with both of these apps - Let Cursor fetch your Slack Messages, Build the feature and Create a Pull Request Customers are happier than even before and engineers can focus on long term stuff!! All you need is
1:33

INSANE: Cursor + MCP just built a customer-requested feature end-to-end!! Our customer sent us a slack message requesting for a feature. Cursor read this, built the feature and created a Pull Request, all on its own! Here's how you can set it up, - Go to Composio's MCP directory - Search for Slack and Github, copy the sse url - Complete Auth with both of these apps - Let Cursor fetch your Slack Messages, Build the feature and Create a Pull Request Customers are happier than even before and engineers can focus on long term stuff!! All you need is

Karan Vaidya

166,209 просмотров • 1 год назад

Factory is better than Devin, Codex, and Jules, and it's not even close. This is not just a fully autonomous software engineer but also a product manager and researcher. It's the entire package you need to build a new project or dramatically expand an existing one. I recorded a quick video so you can see how it works. You can use these autonomous Droids from Factory. Here is what they can do: 1. Build a full production-grade app from scratch 2. Develop new features for an existing codebase 3. Migrations or refactors on your codebase 4. Build integrations 5. Generate complete feature specifications 6. Solve and close issues from your issue management system 7. Do deep research on any software topics And Factory can connect to Linear, GitHub, Google Drive, Slack, Jira, Sentry, GitLab, and Notion to do its work. You can use any of the big models to do what you need.
4:24

Factory is better than Devin, Codex, and Jules, and it's not even close. This is not just a fully autonomous software engineer but also a product manager and researcher. It's the entire package you need to build a new project or dramatically expand an existing one. I recorded a quick video so you can see how it works. You can use these autonomous Droids from Factory. Here is what they can do: 1. Build a full production-grade app from scratch 2. Develop new features for an existing codebase 3. Migrations or refactors on your codebase 4. Build integrations 5. Generate complete feature specifications 6. Solve and close issues from your issue management system 7. Do deep research on any software topics And Factory can connect to Linear, GitHub, Google Drive, Slack, Jira, Sentry, GitLab, and Notion to do its work. You can use any of the big models to do what you need.

Santiago

70,099 просмотров • 1 год назад

✨New LangChain Academy Course: Learn to build with LangSmith Agent Builder 🪄 Learn how to build your own agents with LangSmith Agent Builder. Anyone can now build agents for complex daily tasks, without writing code. We built Agent Builder for anyone whose day gets swallowed by routine work. The research, follow-ups, updates, scheduling, and status checks that are essential to your operations, but quickly take over your calendar. Agent Builder is different from traditional workflow automations. You don’t need to map every step, tinker with if-this-then-that branching, or babysit dependencies. You just give it feedback like you would a teammate, and the agent learns using its memory. In this quickstart course, you'll learn how to: - Build an email agent - Understand what agents can do - Improve your agent - Set up triggers and your Agent Inbox Enroll for free ➡️
1:45

✨New LangChain Academy Course: Learn to build with LangSmith Agent Builder 🪄 Learn how to build your own agents with LangSmith Agent Builder. Anyone can now build agents for complex daily tasks, without writing code. We built Agent Builder for anyone whose day gets swallowed by routine work. The research, follow-ups, updates, scheduling, and status checks that are essential to your operations, but quickly take over your calendar. Agent Builder is different from traditional workflow automations. You don’t need to map every step, tinker with if-this-then-that branching, or babysit dependencies. You just give it feedback like you would a teammate, and the agent learns using its memory. In this quickstart course, you'll learn how to: - Build an email agent - Understand what agents can do - Improve your agent - Set up triggers and your Agent Inbox Enroll for free ➡️

LangChain

26,513 просмотров • 6 месяцев назад

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!
1:37

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!

Andrew Ng

159,737 просмотров • 4 месяцев назад

Yesterday I dropped a guide on setting up Claude Cowork that blew up. One question kept coming up: how do I use all of this on my phone? Cowork doesn't have a mobile app yet. But there's a simple workaround. Push your Cowork workspace to a private GitHub repo. Open Claude Code on the Anthropic mobile app. Connect the repo. Done. Now every skill file, brain file, and writing style you built for Cowork is accessible on the go. No coding. 5 minutes to set up. Two things to know: This syncs your files and skills, not your connectors (Slack, Gmail, etc.) When you update files locally, push to GitHub to keep mobile current Full walkthrough below. Original Cowork setup guide (with the prompt to build your own system) is reposted below as well. Enjoy!!
5:45

Yesterday I dropped a guide on setting up Claude Cowork that blew up. One question kept coming up: how do I use all of this on my phone? Cowork doesn't have a mobile app yet. But there's a simple workaround. Push your Cowork workspace to a private GitHub repo. Open Claude Code on the Anthropic mobile app. Connect the repo. Done. Now every skill file, brain file, and writing style you built for Cowork is accessible on the go. No coding. 5 minutes to set up. Two things to know: This syncs your files and skills, not your connectors (Slack, Gmail, etc.) When you update files locally, push to GitHub to keep mobile current Full walkthrough below. Original Cowork setup guide (with the prompt to build your own system) is reposted below as well. Enjoy!!

JJ Englert

55,555 просмотров • 4 месяцев назад

Let's talk about MoE: 🔶 How many experts should you use? 🔶 How does dynamic routing actually behave in production? 🔶 How do you debug a model that won’t train? 🔶 What does 8x7B actually mean for memory and compute? 🔶 What hardware optimizations matter for sparse models? Mixture of Experts (MoE) is changing how the biggest AI models are built — but it’s still hard to get right. That's why we are launching a new MoE 101 series, led by Daria Soboleva to bridge the gap between theory and practice. Dive in to our MoE guide:
0:50

Let's talk about MoE: 🔶 How many experts should you use? 🔶 How does dynamic routing actually behave in production? 🔶 How do you debug a model that won’t train? 🔶 What does 8x7B actually mean for memory and compute? 🔶 What hardware optimizations matter for sparse models? Mixture of Experts (MoE) is changing how the biggest AI models are built — but it’s still hard to get right. That's why we are launching a new MoE 101 series, led by Daria Soboleva to bridge the gap between theory and practice. Dive in to our MoE guide:

Cerebras

345,732 просмотров • 1 год назад

One of my best engineers just showed me how to set up OpenClaw securely & without a Mac Mini. Here's his step-by-step: 1) Spin up a VPS on Hetzner It's a virtual server in the cloud. basically a computer you rent for $5-10/month. Pick 8GB RAM, Ubuntu, US East. Takes 2 minutes. 2) Install Tailscale This makes your server invisible to the public internet. Think of it like moving from a house on Google Maps into a gated community where only your devices can get in. Without this, bots start attacking your server within seconds of it going live. 3) Harden the server SSH keys only. Firewall. Intrusion prevention. Auto security updates. CJ actually uses AI to red team his own servers. Tells it to try and break in, then patches whatever it finds. 4) Install OpenClaw🦞 and run the onboarding. You pick your model provider, connect Telegram via BotFather, and configure hooks that give your agent long-term memory. The hooks auto-save sessions and context so the agent gets smarter over time. 5) Set up the gateway This is the piece that makes it actually powerful. It's a message bus that lets your main agent talk to sub-agents, receive messages from Telegram/Discord/Slack, and orchestrate everything. this is what keeps it running 24/7. 6) Hatch your claw and start training it Dump as much info about yourself as possible. tell it your preferences, your workflows, your tools. CJ's agent monitors his email, Slack, and manages his to-do list autonomously. Watch the video for the full break-down & follow CJ Hess for more AI engineering sauce.
38:52

One of my best engineers just showed me how to set up OpenClaw securely & without a Mac Mini. Here's his step-by-step: 1) Spin up a VPS on Hetzner It's a virtual server in the cloud. basically a computer you rent for $5-10/month. Pick 8GB RAM, Ubuntu, US East. Takes 2 minutes. 2) Install Tailscale This makes your server invisible to the public internet. Think of it like moving from a house on Google Maps into a gated community where only your devices can get in. Without this, bots start attacking your server within seconds of it going live. 3) Harden the server SSH keys only. Firewall. Intrusion prevention. Auto security updates. CJ actually uses AI to red team his own servers. Tells it to try and break in, then patches whatever it finds. 4) Install OpenClaw🦞 and run the onboarding. You pick your model provider, connect Telegram via BotFather, and configure hooks that give your agent long-term memory. The hooks auto-save sessions and context so the agent gets smarter over time. 5) Set up the gateway This is the piece that makes it actually powerful. It's a message bus that lets your main agent talk to sub-agents, receive messages from Telegram/Discord/Slack, and orchestrate everything. this is what keeps it running 24/7. 6) Hatch your claw and start training it Dump as much info about yourself as possible. tell it your preferences, your workflows, your tools. CJ's agent monitors his email, Slack, and manages his to-do list autonomously. Watch the video for the full break-down & follow CJ Hess for more AI engineering sauce.

Alex Lieberman

64,618 просмотров • 4 месяцев назад

Anthropic's CEO "50% of all tech jobs will be completely wiped out within 1-5 years" he said it on national television here's what nobody in that interview mentioned - the developers who'll survive aren't the ones with the best resumes. they're the ones who figured out how to make AI actually listen to them right now Claude Code has one critical flaw. every time you open it, it forgets everything. your stack, your rules, your last 10 sessions - gone one developer found Karpathy's notes on the 4 behaviors that break Claude Code and turned them into a single file. CLAUDE.md. paste it in your project root and coding accuracy jumps from 65% to 94% 82,000 developers already starred it on GitHub. here's the full breakdown of what goes inside and how to set it up:
4:48

Anthropic's CEO "50% of all tech jobs will be completely wiped out within 1-5 years" he said it on national television here's what nobody in that interview mentioned - the developers who'll survive aren't the ones with the best resumes. they're the ones who figured out how to make AI actually listen to them right now Claude Code has one critical flaw. every time you open it, it forgets everything. your stack, your rules, your last 10 sessions - gone one developer found Karpathy's notes on the 4 behaviors that break Claude Code and turned them into a single file. CLAUDE.md. paste it in your project root and coding accuracy jumps from 65% to 94% 82,000 developers already starred it on GitHub. here's the full breakdown of what goes inside and how to set it up:

KingWilliam

174,340 просмотров • 1 месяц назад

Most people building in n8n are sitting on way more potential than they realize. You don’t need another backend workflow. You need a front-end that makes it usable. This week I built a micro-app in Bolt that does exactly that. Drop in a TikTok keyword, hit go - and behind the scenes, it: - scrapes trending videos - pulls pain points, emotional triggers, hooks - rewrites the script to pitch your product - pipes it all back into the UI, ready to use this approach has me thinking less like "how do i build a workflow" and more like "what micro-app would actually be useful to me or my team?" feels like the missing piece between powerful automations and actual utility. if you're building in n8n and not playing with custom UIs yet... you're sleeping. drop a comment if you want a walkthrough of how I built this, including the prompts I used to code the whole thing - I’ll record it ASAP.
5:41

Most people building in n8n are sitting on way more potential than they realize. You don’t need another backend workflow. You need a front-end that makes it usable. This week I built a micro-app in Bolt that does exactly that. Drop in a TikTok keyword, hit go - and behind the scenes, it: - scrapes trending videos - pulls pain points, emotional triggers, hooks - rewrites the script to pitch your product - pipes it all back into the UI, ready to use this approach has me thinking less like "how do i build a workflow" and more like "what micro-app would actually be useful to me or my team?" feels like the missing piece between powerful automations and actual utility. if you're building in n8n and not playing with custom UIs yet... you're sleeping. drop a comment if you want a walkthrough of how I built this, including the prompts I used to code the whole thing - I’ll record it ASAP.

J.B.

97,397 просмотров • 1 год назад

This 1-min clip from the creator of LangChain + this 10-min read from him will teach you more about what actually matters in AI agents than everything you've scrolled past this year. Watch this. Then read below. You'll think about agents differently after. -Memory defines how an agent behaves; same conversation, different compaction rules, different agent. - There's no version control for memory. No diffs, no reverts, no way to see what changed. - Compaction can silently erase parts of your agent's personality mid-session without anyone noticing. - "Open memory" means exportable state and inspectable compaction, not a vector database. - The storage layer is solved and boring; the memory contract above it is what actually matters. Give this 11 minutes this weekend . It'll change how you build.
1:13

This 1-min clip from the creator of LangChain + this 10-min read from him will teach you more about what actually matters in AI agents than everything you've scrolled past this year. Watch this. Then read below. You'll think about agents differently after. -Memory defines how an agent behaves; same conversation, different compaction rules, different agent. - There's no version control for memory. No diffs, no reverts, no way to see what changed. - Compaction can silently erase parts of your agent's personality mid-session without anyone noticing. - "Open memory" means exportable state and inspectable compaction, not a vector database. - The storage layer is solved and boring; the memory contract above it is what actually matters. Give this 11 minutes this weekend . It'll change how you build.

Avid

16,898 просмотров • 3 месяцев назад

Introducing Base44 Superagents. AI agents built with managed infrastructure, secured by default, one-click integrations, and 24/7 execution from the start. Everything is taken care of so you can focus on what your agent does, not how to get it running. That means no API keys to juggle, no config files, no security setup, and no maintenance. We handle all of it. Your Superagent connects to all the tools you already use in one click, runs on schedules and triggers, remembers context across sessions, acts proactively on your behalf, and keeps working around the clock. All from wherever you already are, WhatsApp, Telegram, Slack, or your browser. The AI agent everyone's been waiting for, with everything you need already built in. We're excited to get this into your hands, so we're giving free credits to everyone who comments and reposts in the next 24 hours.
1:51

Introducing Base44 Superagents. AI agents built with managed infrastructure, secured by default, one-click integrations, and 24/7 execution from the start. Everything is taken care of so you can focus on what your agent does, not how to get it running. That means no API keys to juggle, no config files, no security setup, and no maintenance. We handle all of it. Your Superagent connects to all the tools you already use in one click, runs on schedules and triggers, remembers context across sessions, acts proactively on your behalf, and keeps working around the clock. All from wherever you already are, WhatsApp, Telegram, Slack, or your browser. The AI agent everyone's been waiting for, with everything you need already built in. We're excited to get this into your hands, so we're giving free credits to everyone who comments and reposts in the next 24 hours.

Base44

1,580,475 просмотров • 4 месяцев назад

Introducing: PlayerZero The world's first Engineering World Model that puts debugging, fixing, and testing your code on autopilot. We've raised $20M from Foundation Capital, Matei Zaharia (Databricks), Peter Bailis (Workday), Guillermo Rauch (Vercel), Dylan Field (Figma), Drew Houston (Dropbox), and more PlayerZero frees up 30% of your engineering bandwidth by: 1.⁠ ⁠Finding the root cause for bugs & incidents in minutes that engineering teams take days to identify. 2.⁠ ⁠Predicting in minutes, edge case issues that a 300-person QA team would take weeks to find. ------ Here's why this matters: No one in your org has a complete picture of how your production software actually behaves. Support sees tickets. SRE sees infra. Dev sees code. Each team builds their own fragmented view - and none of these systems talk to each other. When something breaks, everyone scrambles to stitch the picture together by hand. PlayerZero connects all of it into a single context graph - → The Slack thread where your lead said "we went with X because Y fell apart in prod last time" → The PR review where an engineer explained the tradeoff → The lifetime history of your CI/CD pipeline, observability stack, incidents, and support tickets So you can trace any problem to its root cause across every silo. And it compounds. Every incident diagnosed teaches the model something new. The longer it runs, the deeper it understands - which code paths are high-risk, which configurations are fragile, which changes tend to break which customer flows. So when you sit down to debug a live issue, you have your entire org's collective reasoning and production memory behind you - instantly. ------ Zuora, Georgia-Pacific, and Nylas have reduced resolution time by 90% and caught 95% of breaking changes and freeing an average of $30M in engineering bandwidth. ------ Our guarantee: If we can't increase your engineering bandwidth by at least 20% within one week, we'll donate $10,000 to an open-source project of your choice. Book a demo -
2:52

Introducing: PlayerZero The world's first Engineering World Model that puts debugging, fixing, and testing your code on autopilot. We've raised $20M from Foundation Capital, Matei Zaharia (Databricks), Peter Bailis (Workday), Guillermo Rauch (Vercel), Dylan Field (Figma), Drew Houston (Dropbox), and more PlayerZero frees up 30% of your engineering bandwidth by: 1.⁠ ⁠Finding the root cause for bugs & incidents in minutes that engineering teams take days to identify. 2.⁠ ⁠Predicting in minutes, edge case issues that a 300-person QA team would take weeks to find. ------ Here's why this matters: No one in your org has a complete picture of how your production software actually behaves. Support sees tickets. SRE sees infra. Dev sees code. Each team builds their own fragmented view - and none of these systems talk to each other. When something breaks, everyone scrambles to stitch the picture together by hand. PlayerZero connects all of it into a single context graph - → The Slack thread where your lead said "we went with X because Y fell apart in prod last time" → The PR review where an engineer explained the tradeoff → The lifetime history of your CI/CD pipeline, observability stack, incidents, and support tickets So you can trace any problem to its root cause across every silo. And it compounds. Every incident diagnosed teaches the model something new. The longer it runs, the deeper it understands - which code paths are high-risk, which configurations are fragile, which changes tend to break which customer flows. So when you sit down to debug a live issue, you have your entire org's collective reasoning and production memory behind you - instantly. ------ Zuora, Georgia-Pacific, and Nylas have reduced resolution time by 90% and caught 95% of breaking changes and freeing an average of $30M in engineering bandwidth. ------ Our guarantee: If we can't increase your engineering bandwidth by at least 20% within one week, we'll donate $10,000 to an open-source project of your choice. Book a demo -

Animesh Koratana

2,755,945 просмотров • 4 месяцев назад

Xiaomi just dropped a FREE CLAUDE CODE with memory that actually persists between sessions and nobody is talking about it MiMo Code dropped 4 days ago. 8k GitHub stars. Built-in free model called MiMo Auto - you just install it and it works, zero configuration, zero API keys What's inside: > persistent memory across sessions - agent picks up exactly where it stopped > subagents that spawn automatically and run in parallel > /dream extracts knowledge from your session into project memory > /distill turns your repeated workflows into reusable skills > /goal with a judge model that decides if the work is actually done - not just if the agent thinks it is How to install: > Mac / Linux: curl -fsSL | bash > Windows npm install -g MIMO-ai/cli Then run: > mimo video of me installing and running it is attached github(.)com/XiaomiMiMo/MiMo-Code
0:50

Xiaomi just dropped a FREE CLAUDE CODE with memory that actually persists between sessions and nobody is talking about it MiMo Code dropped 4 days ago. 8k GitHub stars. Built-in free model called MiMo Auto - you just install it and it works, zero configuration, zero API keys What's inside: > persistent memory across sessions - agent picks up exactly where it stopped > subagents that spawn automatically and run in parallel > /dream extracts knowledge from your session into project memory > /distill turns your repeated workflows into reusable skills > /goal with a judge model that decides if the work is actually done - not just if the agent thinks it is How to install: > Mac / Linux: curl -fsSL | bash > Windows npm install -g MIMO-ai/cli Then run: > mimo video of me installing and running it is attached github(.)com/XiaomiMiMo/MiMo-Code

monokern

63,696 просмотров • 1 месяц назад

.Scott Wu to Joe Lonsdale on why Cognition uses AI in job interviews: "One or two years ago, people had this mentality of 'How do we make sure people aren't using AI while we're interviewing them?' And I think that has totally flipped. Honestly, I think that was wrong... If you're asking the question of like, how do we evaluate people on exactly the thing that AI can already do, that seems kind of the wrong. Our interview process has always been... you can use as much AI as you want to use. We're going to give you a few hours. Just build your whole own product surface. A lot of these are projects that, frankly, is like, if you were trying to do this by hand, you would not be able to get done in a few hours. So you kind of have to use AI for this. But in reality, what we actually want to test is, in addition to how familiar you are with these tools, what we actually want to test is, what do you think is the right thing to build? Or how do you make these product decisions? How do you make these trade-offs? How do you decide or collect information about what you should be doing?"
0:58

.Scott Wu to Joe Lonsdale on why Cognition uses AI in job interviews: "One or two years ago, people had this mentality of 'How do we make sure people aren't using AI while we're interviewing them?' And I think that has totally flipped. Honestly, I think that was wrong... If you're asking the question of like, how do we evaluate people on exactly the thing that AI can already do, that seems kind of the wrong. Our interview process has always been... you can use as much AI as you want to use. We're going to give you a few hours. Just build your whole own product surface. A lot of these are projects that, frankly, is like, if you were trying to do this by hand, you would not be able to get done in a few hours. So you kind of have to use AI for this. But in reality, what we actually want to test is, in addition to how familiar you are with these tools, what we actually want to test is, what do you think is the right thing to build? Or how do you make these product decisions? How do you make these trade-offs? How do you decide or collect information about what you should be doing?"

American Optimist

13,182 просмотров • 3 месяцев назад

"I woke up and he already built a website, created a product, set up Stripe, and launched." Here's my new episode with Nat Eliason on how he set up his OpenClaw bot, Felix Craft, to build a business that made $14,718 in 3 weeks. We talked about: ✅ The 3-layer memory system that prevents your bot from forgetting things ✅ How to run 5 chats with your bot at the same time ✅ How to safely give your bot Stripe, Vercel, and X access Some quotes from Nat: "Every time Felix asks me to do something, I ask: Can I remove this bottleneck so you never have to ask me this again?" "I'm never in Claude Code or Codex myself anymore. I just tell Felix to do it." "If you get the memory system and the proactivity right, it solves 90% of the frustrations that most people run into." 📌 Watch now: Thanks to our sponsors: Linear: The AI agent platform for modern teams Replit ⠕: From 0 to full stack app in 2 min.
0:40

"I woke up and he already built a website, created a product, set up Stripe, and launched." Here's my new episode with Nat Eliason on how he set up his OpenClaw bot, Felix Craft, to build a business that made $14,718 in 3 weeks. We talked about: ✅ The 3-layer memory system that prevents your bot from forgetting things ✅ How to run 5 chats with your bot at the same time ✅ How to safely give your bot Stripe, Vercel, and X access Some quotes from Nat: "Every time Felix asks me to do something, I ask: Can I remove this bottleneck so you never have to ask me this again?" "I'm never in Claude Code or Codex myself anymore. I just tell Felix to do it." "If you get the memory system and the proactivity right, it solves 90% of the frustrations that most people run into." 📌 Watch now: Thanks to our sponsors: Linear: The AI agent platform for modern teams Replit ⠕: From 0 to full stack app in 2 min.

Peter Yang

230,230 просмотров • 5 месяцев назад

"Claude Code is the first AI tool that can actually recreate how a data scientist thinks." Here's my new episode with Sumeet Marwaha (Head of Data at Brex) on exactly how to build an AI analyst with Claude Code. We covered: ✅ 3 queries to build a data analyst MCP ✅ How to give the analyst both data + context ✅ Exclusive Brex data on which AI tools are crushing it in startups and enterprise Some quotes from Sumeet: "I've set up dashboards many times in my career. They end up getting ignored. Claude will always read it. Claude will always ask the right questions." "You have to set up Claude Code to not just look at the data. It should be able to search Slack, find the incident, and understand why your metrics look wrong." "This tool is absolutely crushing it based on our data. It's both the startup AND enterprise coding tool of choice." 📌 Watch now:
0:46

"Claude Code is the first AI tool that can actually recreate how a data scientist thinks." Here's my new episode with Sumeet Marwaha (Head of Data at Brex) on exactly how to build an AI analyst with Claude Code. We covered: ✅ 3 queries to build a data analyst MCP ✅ How to give the analyst both data + context ✅ Exclusive Brex data on which AI tools are crushing it in startups and enterprise Some quotes from Sumeet: "I've set up dashboards many times in my career. They end up getting ignored. Claude will always read it. Claude will always ask the right questions." "You have to set up Claude Code to not just look at the data. It should be able to search Slack, find the incident, and understand why your metrics look wrong." "This tool is absolutely crushing it based on our data. It's both the startup AND enterprise coding tool of choice." 📌 Watch now:

Peter Yang

39,600 просмотров • 6 месяцев назад

Most AI Agents can Talk..... Very few can actually do anything. You can spin up an agent in minutes… but the second you want it to: 🔴 Create a GitHub issue ⚪ Update Notion 🟡 Send a Slack message 🔵 Log actions properly 🟣 Handle auth securely You’re suddenly building integrations for weeks. This is why Merge Agent Handler caught my attention. It gives your AI agent real tool access across thousands of platforms through one integration, but the part I actually care about is this: Production-ready security + full audit logs out of the box. You can see every tool call. Every API request. Every response. So your agent isn’t just “connected”..... it’s monitored and controlled. If you’re building agents that need to take real actions, this is worth looking at: Video shows it in action 👇
0:22

Most AI Agents can Talk..... Very few can actually do anything. You can spin up an agent in minutes… but the second you want it to: 🔴 Create a GitHub issue ⚪ Update Notion 🟡 Send a Slack message 🔵 Log actions properly 🟣 Handle auth securely You’re suddenly building integrations for weeks. This is why Merge Agent Handler caught my attention. It gives your AI agent real tool access across thousands of platforms through one integration, but the part I actually care about is this: Production-ready security + full audit logs out of the box. You can see every tool call. Every API request. Every response. So your agent isn’t just “connected”..... it’s monitored and controlled. If you’re building agents that need to take real actions, this is worth looking at: Video shows it in action 👇

Kaitee

49,963 просмотров • 4 месяцев назад

How I get shit done, Episode 001 I've set up a playbook called ‘land’, which is triggered automatically when I drag an issue into the merging column in Linear. That reliably runs CI and merges any green PRs. This has allowed me to ship way faster than before. I think the key takeaway here is you can try to build your own code factory and your own agent orchestration layer, but it is a huge amount of work. The truth is there are entire companies with massive funding that are already tackling this and it's just easier to use their platform. I think this is a lot like if you were a carpenter: you could build your own generator, fuel it, wire it up, and then build a plug and then you could plug your saw into it. Or you could just plug your saw into the wall. Because the electricity company has already done all the work in the infrastructure and investment to make that plug work. I think more of us who are building companies should just be plugging into the wall instead of trying to build all this tooling ourselves. As a dev it's so tempting to build your own dev tools but I think a lot of times, even though you can build fast with agents now, it's a complete waste of time. It probably sounds like I'm being paid by Devin or something but I have zero financial interest here. They don't give me credits. I'm not an investor. I'm not being paid. I just think the tooling is really damn good. If you used Devin a long time ago and wrote it off, you really should have another look - for $500/month it's pretty obscene what you can get done.
5:57

How I get shit done, Episode 001 I've set up a playbook called ‘land’, which is triggered automatically when I drag an issue into the merging column in Linear. That reliably runs CI and merges any green PRs. This has allowed me to ship way faster than before. I think the key takeaway here is you can try to build your own code factory and your own agent orchestration layer, but it is a huge amount of work. The truth is there are entire companies with massive funding that are already tackling this and it's just easier to use their platform. I think this is a lot like if you were a carpenter: you could build your own generator, fuel it, wire it up, and then build a plug and then you could plug your saw into it. Or you could just plug your saw into the wall. Because the electricity company has already done all the work in the infrastructure and investment to make that plug work. I think more of us who are building companies should just be plugging into the wall instead of trying to build all this tooling ourselves. As a dev it's so tempting to build your own dev tools but I think a lot of times, even though you can build fast with agents now, it's a complete waste of time. It probably sounds like I'm being paid by Devin or something but I have zero financial interest here. They don't give me credits. I'm not an investor. I'm not being paid. I just think the tooling is really damn good. If you used Devin a long time ago and wrote it off, you really should have another look - for $500/month it's pretty obscene what you can get done.

Ryan Carson

14,059 просмотров • 4 месяцев назад

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering
0:56

THIS IS HOW A SENIOR ENGINEER ACTUALLY SCALES THEMSELVES WITH CLAUDE CODE the biggest change with AI isn't coding faster. it's where you actually spend your time now. more detailed prompts, more code review, more planning, less typing, etc. here's the workflow: this guy has been shipping code since the days of cgi and perl. he uses a compound engineering plugin that runs 5 separate agents on every task. one brainstorms, one plans the technical implementation, one executes, one reviews, one checks different verticals. every step is documented in markdown files. it's slow and way more waiting. but the output quality is way higher because each agent is focused on one thing. then the REAL multiplier is in git worktrees if Claude Code made you 10x faster, worktrees multiplies that again depending on how many agents you can manage in parallel his team runs 4-8 Claude Code sessions at the same time across different worktrees with each one working on a separate task. the skill is managing multiple AI agents in parallel without losing track, that's the next evolution of engineering

Om Patel

159,179 просмотров • 3 месяцев назад

"Not a single one of our full-time engineers right now writes code anymore... it's all agentic... the way you build a company completely changes." JD Ross with Joe Lonsdale on the future of software: JD Ross: Not a single one of our full-time engineers right now writes code anymore. They do everything through Codex, Claude Code, or Cursor. Joe Lonsdale: It's all agentic. JD: It's all agentic. Joe: A lot of them are managing lots of agents at once, right? That's how they're working? JD: Yeah, Cole who runs our engineering team has six agents that are running at once at all times just doing different kind of projects. When we create a new ticket in Linear, it automatically kicks off this thing that basically creates a dev environment, which then tries to one shot the solution and then creates a PR that we review. The whole way you build software is changing so quickly. And I think right now the cost of software is just asymptotically dropping to zero... which means that the way you build a company completely changes. We can now have an enterprise customer come up who says, "Oh yeah, this is so close. What we actually need it for is X." We can build X in one day, ship it live, and close that deal. We did this last week... It's a completely different way of even thinking.
0:53

"Not a single one of our full-time engineers right now writes code anymore... it's all agentic... the way you build a company completely changes." JD Ross with Joe Lonsdale on the future of software: JD Ross: Not a single one of our full-time engineers right now writes code anymore. They do everything through Codex, Claude Code, or Cursor. Joe Lonsdale: It's all agentic. JD: It's all agentic. Joe: A lot of them are managing lots of agents at once, right? That's how they're working? JD: Yeah, Cole who runs our engineering team has six agents that are running at once at all times just doing different kind of projects. When we create a new ticket in Linear, it automatically kicks off this thing that basically creates a dev environment, which then tries to one shot the solution and then creates a PR that we review. The whole way you build software is changing so quickly. And I think right now the cost of software is just asymptotically dropping to zero... which means that the way you build a company completely changes. We can now have an enterprise customer come up who says, "Oh yeah, this is so close. What we actually need it for is X." We can build X in one day, ship it live, and close that deal. We did this last week... It's a completely different way of even thinking.

American Optimist

21,014 просмотров • 4 месяцев назад