$ cat ~/linkedin/posts/today.json

I run 50+ AI skills from a single monorepo. Not because I planned to. Because single-agent workflows kept breaking.

I run 50+ AI skills from a single monorepo. Not because I planned to. Because single-agent workflows kept breaking. The pattern I kept hitting: one agent tries to do everything, context window fills up, quality drops, things get missed. So I started splitting. One agent routes tasks. Another write...

If you're building multi-agent anything, start with the handoff format. Everything else follows from that.

Inspired by Swyx: "Swyx discusses the evolution of AI agents, emphasizing multi..." source2500 likes, 450 comments

Six months ago I was mass-sending 200 emails a day from SalesLoft on a primary domain with no warmup. Now I have an AI agent that writes, tests, and commits code while I review diffs.

Six months ago I was mass-sending 200 emails a day from SalesLoft on a primary domain with no warmup. Now I have an AI agent that writes, tests, and commits code while I review diffs. The career arc from SDR to GTM engineer happened fast. But the shift from "I write code" to "I supervise code being...

The skill that matters most right now isn't writing code. It's describing precisely what you want built and knowing when the output is wrong.

Inspired by Andrej Karpathy: "Karpathy explores LLMs as agents for code generation and deb..." source4500 likes, 780 comments

Everyone wants to talk about the AI in their sales stack. Nobody wants to talk about the 14 API calls, 3 enrichment sources, and MX validation layer underneath it.

Everyone wants to talk about the AI in their sales stack. Nobody wants to talk about the 14 API calls, 3 enrichment sources, and MX validation layer underneath it. I built an ABM pipeline that sources accounts from Apollo, enriches them, validates contacts, filters by title and email deliverability...

Start with data quality. Seriously. Your AI personalization means nothing if you're emailing the wrong person at a dead domain.

Inspired by Hamish Grierson: "Details building production-grade AI agents for sales automa..." source1200 likes, 210 comments

AI agents that handle entire pull requests sound amazing until you realize most codebases don't have enough context written down for a human to make good PRs, let alone an agent.

AI agents that handle entire pull requests sound amazing until you realize most codebases don't have enough context written down for a human to make good PRs, let alone an agent. I maintain a monorepo with 3 Next.js sites, a macOS app, Python scripts, and a cron pipeline. My AI agent makes real com...

Write your docs like an AI agent will read them tomorrow. Because it probably will.

Inspired by Nat Friedman: "Nat reflects on the next wave of developer tools powered by ..." source3100 likes, 520 comments

Benchmarks say AI agents struggle with long-horizon planning. My experience says they struggle with remembering what they did 10 minutes ago.

Benchmarks say AI agents struggle with long-horizon planning. My experience says they struggle with remembering what they did 10 minutes ago. I've been building with AI agents daily for months. Real production work, not demos. And the gap between "agent completes benchmark task" and "agent ships re...

If your agent keeps making the same mistakes, the fix isn't a better model. It's a better memory system.

Inspired by Eliot Peper: "Analyzes the hype vs. reality of AI agent infrastructure, po..." source800 likes, 140 comments

I used to manually build buying committees in Salesforce. 40 contacts per account, mapped by title and department, one by one. Now I have a Python script that does it in 11 seconds.

I used to manually build buying committees in Salesforce. 40 contacts per account, mapped by title and department, one by one. Now I have a Python script that does it in 11 seconds. SDRs make the best GTM engineers. Not because SDRs are technical. Because SDRs know which manual processes are actual...

If you're an SDR drowning in manual work and curious about automation, start with one workflow you hate. Automate just that. The rest follows.

Inspired by Sami Rahman: "Discusses building scalable GTM engines by integrating engin..." source2500 likes, 450 comments

The difference between personalized outbound and spam isn't the copy. It's whether you actually know who you're emailing and why.

The difference between personalized outbound and spam isn't the copy. It's whether you actually know who you're emailing and why. I've been on both sides. I've sent thousands of garbage emails from templates that said "I noticed your company is growing" to people at companies that were laying off. ...

Your outbound is only as good as your data layer. Fix the inputs and the outputs fix themselves.

Inspired by Josh Braun: "Breaks down ethical outbound automation tactics using AI too..." source3200 likes, 600 comments

I have 4 live websites, a daily SEO brief generated by cron, and a blog pipeline that converts Substack posts to web pages automatically. None of it started as a "content strategy."

I have 4 live websites, a daily SEO brief generated by cron, and a blog pipeline that converts Substack posts to web pages automatically. None of it started as a "content strategy." It started as documenting what I was building. Posts about Clay workflows I actually use. Breakdowns of ABM pipeline...

Stop planning content. Start documenting what you're already doing. The pipeline follows the substance.

Inspired by Aja Frost: "Outlines a step-by-step content strategy for B2B SaaS that d..." source1800 likes, 320 comments

I run a monorepo with 3 Next.js sites, a macOS app, Python automation scripts, a CRM sync pipeline, and a cron system. No team. No VC. Just one repo and an AI agent.

I run a monorepo with 3 Next.js sites, a macOS app, Python automation scripts, a CRM sync pipeline, and a cron system. No team. No VC. Just one repo and an AI agent. The solo builder movement usually gets romanticized. "Ship fast, break things, ramen profitable." The reality is more like... debuggi...

The barrier to building isn't talent or funding anymore. It's willingness to sit with the discomfort of figuring it out alone.

Inspired by Pieter Levels: "Pieter shares his experience as a solo founder shipping mult..." source12000 likes, 450 comments

I was a plumber. Then an SDR. Then I taught myself to code because I got tired of waiting for engineering to build the automations I needed.

I was a plumber. Then an SDR. Then I taught myself to code because I got tired of waiting for engineering to build the automations I needed. The career pivot stories on LinkedIn usually skip the ugly middle. The part where you're mass-sending emails during the day and watching Python tutorials at n...

If you're in a non-technical role thinking about learning to code, start by automating one thing you already do manually. You don't need permission or a CS degree. You need a problem worth solving.

Inspired by Arvid Kahl: "Arvid recounts building and selling his first SaaS product a..." source8500 likes, 320 comments