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

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

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

One of the most productive engineers I know cannot read code. Matt Van Horn is not an engineer by training. He co-founded June, has 44,000 GitHub stars, and got contributions merged into Go & Python. I had him build live for an hour & walk me through his process.... My fav lessons & quotes from the convo: 1) He never reads code. He does not have an IDE installed. In his words, "I fundamentally believe that very soon no humans should ever write any code and that no humans should ever read any code." 2) Every project starts with the agent writing itself a plan.md file using Compound Engineering. Agents are lazy, he says, and the plan keeps them honest. He never reads the plan either. "Plans are for agents, you silly human." 3) His CLIs leave notes for themselves. Each run records what it learned in a markdown file, so the next run starts where the last one ended. He calls them self-healing. 4) His agent has an email address. From Telegram on his phone, he sends a task. It emails his Mac, authenticated, and the work starts while he is at his kids' soccer practice. 5) He feeds whole transcripts, not summaries. After a two-hour meeting with a Google Ventures researcher, his agent read the researcher's entire book, wrote itself a report on every chapter, and turned it all into a plan for his business. 6) Him yapping to his agents is like nerd ASMR. "Go agent go" is how he likes to finish telling the agent what to do. 7) How he thinks about this next chapter of building: "Every generation of tools moves the engineer's job up a level. The code was never the point. The problem was."show more

Alex Lieberman

311,198 subscribers

52,464 просмотров • 2 дней назад •via X (Twitter)

Наука и технологии Образование Здоровье и велнес

Anya Rossi• Live Now

Private livecam show

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

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

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

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

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

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

Andrew Wilkinson owns 40+ businesses. He just showed me how he's using OpenClaw, Claude Code and AI agents to run latest business, start new ones, and automate everything. Here's what I learned: 1. In December 2025, something clicked. He started waking up at 3AM with a smile, sitting in terminal with 10 Claude Code tabs open. He hasn't stopped since. He calls it chasing the dragon. 2.He built a full SaaS product called Deep Personality. A 40-minute personality test that generates a 100-page report written like Robert Greene. $20 000 in revenue. Zero employees. The entire business runs on AI agents. 3. He has agents for support, marketing, and dev. When a support ticket comes in, the agent either handles it or sends it to the dev agent. If it's critical, the agent fixes the bug and merges the PR before he wakes up. Then it emails the customer back. 4. His marketing agent is connected to PostHog, manages Meta and Reddit ads, creates ad creative, runs multivariate tests, and sets budgets. He's about to give it a $100 k/month ad budget and see what happens. 5. He forgot his laptop on a trip to Arizona. He ran his entire business from the back of Ubers using OpenClaw. Nobody picked up that every single email was written by AI. 6. His take on vibe coding: the worst part about business is people. Between your vision and execution are 100 people you have to convince. Vibe coding removes all of them. For the first time he can do every part of building a product himself. 7. He was trying to build OpenClaw before OpenClaw existed. Now he uses a tool called Harbor, which is basically a GUI for managing multiple agents. You can see all your agents, their status, knowledge bases, and databases in one place. 8. He built a custom AI for his relationship. He and his girlfriend took 15 psychological tests, put the results into ChatGPT, and asked it to analyze their relationship. It nailed every fight they've ever had. That became the product idea for Deep Personality. 9. His honest take: he spends 50% of his time debugging, 30% improving the setup, and 20% being productive. It's a treadmill. But the 20% that works is so powerful he can't stop. 10. His prediction: we're 3-6 months from being able to hand basic businesses off to AI to run entirely. And pretty soon Anthropic and OpenAI are going to launch AI CEOs. This is an inside look at how a serious operator Andrew Wilkinson is using AI agents in the real world. The good, the bad, the debugging, all of it. Most people don't show you this. Episode is live on The Startup Ideas Podcast (SIP) 🧃 watch

Andrew Wilkinson owns 40+ businesses. He just showed me how he's using OpenClaw, Claude Code and AI agents to run latest business, start new ones, and automate everything. Here's what I learned: 1. In December 2025, something clicked. He started waking up at 3AM with a smile, sitting in terminal with 10 Claude Code tabs open. He hasn't stopped since. He calls it chasing the dragon. 2.He built a full SaaS product called Deep Personality. A 40-minute personality test that generates a 100-page report written like Robert Greene. $20 000 in revenue. Zero employees. The entire business runs on AI agents. 3. He has agents for support, marketing, and dev. When a support ticket comes in, the agent either handles it or sends it to the dev agent. If it's critical, the agent fixes the bug and merges the PR before he wakes up. Then it emails the customer back. 4. His marketing agent is connected to PostHog, manages Meta and Reddit ads, creates ad creative, runs multivariate tests, and sets budgets. He's about to give it a $100 k/month ad budget and see what happens. 5. He forgot his laptop on a trip to Arizona. He ran his entire business from the back of Ubers using OpenClaw. Nobody picked up that every single email was written by AI. 6. His take on vibe coding: the worst part about business is people. Between your vision and execution are 100 people you have to convince. Vibe coding removes all of them. For the first time he can do every part of building a product himself. 7. He was trying to build OpenClaw before OpenClaw existed. Now he uses a tool called Harbor, which is basically a GUI for managing multiple agents. You can see all your agents, their status, knowledge bases, and databases in one place. 8. He built a custom AI for his relationship. He and his girlfriend took 15 psychological tests, put the results into ChatGPT, and asked it to analyze their relationship. It nailed every fight they've ever had. That became the product idea for Deep Personality. 9. His honest take: he spends 50% of his time debugging, 30% improving the setup, and 20% being productive. It's a treadmill. But the 20% that works is so powerful he can't stop. 10. His prediction: we're 3-6 months from being able to hand basic businesses off to AI to run entirely. And pretty soon Anthropic and OpenAI are going to launch AI CEOs. This is an inside look at how a serious operator Andrew Wilkinson is using AI agents in the real world. The good, the bad, the debugging, all of it. Most people don't show you this. Episode is live on The Startup Ideas Podcast (SIP) 🧃 watch

GREG ISENBERG

144,005 просмотров • 2 месяцев назад

an OpenAI engineer just showed how he gets agents to do his whole job: code, debug and more, using loops 29 minutes from the engineer who coined "harness engineering" he writes the rules, agents write the code, a reviewer agent loops until it's right the winners won't have the smartest model, they'll have the best loop around it watch it, then read the full guide on loops below

an OpenAI engineer just showed how he gets agents to do his whole job: code, debug and more, using loops 29 minutes from the engineer who coined "harness engineering" he writes the rules, agents write the code, a reviewer agent loops until it's right the winners won't have the smartest model, they'll have the best loop around it watch it, then read the full guide on loops below

Anatoli Kopadze

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

Boris Cherny (Claude Code creator): "I don't prompt Claude anymore... my job is to write loops." In his latest interview, he breaks down the setup step by step. He runs /loops + a dynamic workflow + a couple hundred agents that read his GitHub, Slack, and Twitter and decide what to build next. His only job now is writing the loops that orchestrate them. That's a multi-agent workflow. I broke down how to build your own below ↓

Boris Cherny (Claude Code creator): "I don't prompt Claude anymore... my job is to write loops." In his latest interview, he breaks down the setup step by step. He runs /loops + a dynamic workflow + a couple hundred agents that read his GitHub, Slack, and Twitter and decide what to build next. His only job now is writing the loops that orchestrate them. That's a multi-agent workflow. I broke down how to build your own below ↓

Avid

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

Noah Brier (Noah Brier) uses Claude Code as his second brain—it’s the coolest notetaking setup I’ve ever seen. He has Claude running on a server in his basement hooked up to a VPN. It stores, reads, and writes to thousands of notes in his Obsidian (Obsidian) vault. He does it all from his phone. I had him on the show to tell us exactly how he’s pulling this off. We get into: - The nuts and bolts of the Claude Code-Obsidian setup: Noah set up Claude Code on top of his Obsidian root directory, and he walked me through how he uses it to prep for an upcoming speech—creating a project folder, pulling in relevant research from his notes, saving transcripts from chats with other LLMs, and generating daily progress updates. - The “thinking partner” that lives inside Noah’s second brain: Noah points out that in the hype around AI’s ability to write, the fact that it can read is overlooked. That’s why he has an agent inside Claude Code with strict guardrails to stay in “thinking mode.” It logs his questions, tracks insights, and catches him up on research if he returns to a project after a few days away. - How Noah does deep work on his phone: Noah rigged a home server in his basement, put his Obsidian vault in it—and then runs Claude Code on top. Noah says that being able to think, write, research, and ship code from his phone has fundamentally changed the way he works. This episode of Every 📧’s AI & I is a must-watch for anyone curious about who wants to learn how to use Claude Code to build a true second brain. Watch below! Timestamps: Introduction: 00:01:19 How you can do deep work on your phone: 00:04:28 Why Noah thinks Grok has the best voice AI: 00:06:14 The nuts and bolts of Noah’s Claude Code-Obsidian setup: 00:11:39 Using an agent in Claude Code as a “thinking partner”: 00:23:59 Noah’s Thomas’ English Muffin theory of AI: 00:35:07 The white space still left to explore in AI: 00:44:04 How Noah is preparing his kids for AI: 00:50:41 How he brought his Claude Code setup to mobile: 01:01:54

Noah Brier (Noah Brier) uses Claude Code as his second brain—it’s the coolest notetaking setup I’ve ever seen. He has Claude running on a server in his basement hooked up to a VPN. It stores, reads, and writes to thousands of notes in his Obsidian (Obsidian) vault. He does it all from his phone. I had him on the show to tell us exactly how he’s pulling this off. We get into: - The nuts and bolts of the Claude Code-Obsidian setup: Noah set up Claude Code on top of his Obsidian root directory, and he walked me through how he uses it to prep for an upcoming speech—creating a project folder, pulling in relevant research from his notes, saving transcripts from chats with other LLMs, and generating daily progress updates. - The “thinking partner” that lives inside Noah’s second brain: Noah points out that in the hype around AI’s ability to write, the fact that it can read is overlooked. That’s why he has an agent inside Claude Code with strict guardrails to stay in “thinking mode.” It logs his questions, tracks insights, and catches him up on research if he returns to a project after a few days away. - How Noah does deep work on his phone: Noah rigged a home server in his basement, put his Obsidian vault in it—and then runs Claude Code on top. Noah says that being able to think, write, research, and ship code from his phone has fundamentally changed the way he works. This episode of Every 📧’s AI & I is a must-watch for anyone curious about who wants to learn how to use Claude Code to build a true second brain. Watch below! Timestamps: Introduction: 00:01:19 How you can do deep work on your phone: 00:04:28 Why Noah thinks Grok has the best voice AI: 00:06:14 The nuts and bolts of Noah’s Claude Code-Obsidian setup: 00:11:39 Using an agent in Claude Code as a “thinking partner”: 00:23:59 Noah’s Thomas’ English Muffin theory of AI: 00:35:07 The white space still left to explore in AI: 00:44:04 How Noah is preparing his kids for AI: 00:50:41 How he brought his Claude Code setup to mobile: 01:01:54

Dan Shipper 📧

30,792 просмотров • 10 месяцев назад

Andrej Karpathy hasn't typed a line of code since December. Not because he retired. Not because he switched careers. Because his AI agents do it all now. The former head of Tesla Autopilot, the person who literally wrote the textbook on deep learning, says his workflow flipped from 80% writing code himself to 80% delegating to agents. And he says the ratio has gotten worse since then, not better. He described it as being in "perpetual AI psychosis," spending 16 hours a day not coding, but expressing his will to agents. Manifesting, as he put it. The most unsettling part isn't that he stopped coding. It's that he didn't notice the exact moment it happened. There was no dramatic transition. No announcement. One day he was writing functions, the next he was managing a fleet of autonomous systems that wrote functions for him. This is the person who built Tesla's self-driving AI. Who taught a generation of engineers neural networks through his Stanford lectures. And he's telling you the game changed six months ago. The question isn't whether AI will write most of our code. The question is what happens to the millions of developers whose entire identity was built around being the person who writes it.

Andrej Karpathy hasn't typed a line of code since December. Not because he retired. Not because he switched careers. Because his AI agents do it all now. The former head of Tesla Autopilot, the person who literally wrote the textbook on deep learning, says his workflow flipped from 80% writing code himself to 80% delegating to agents. And he says the ratio has gotten worse since then, not better. He described it as being in "perpetual AI psychosis," spending 16 hours a day not coding, but expressing his will to agents. Manifesting, as he put it. The most unsettling part isn't that he stopped coding. It's that he didn't notice the exact moment it happened. There was no dramatic transition. No announcement. One day he was writing functions, the next he was managing a fleet of autonomous systems that wrote functions for him. This is the person who built Tesla's self-driving AI. Who taught a generation of engineers neural networks through his Stanford lectures. And he's telling you the game changed six months ago. The question isn't whether AI will write most of our code. The question is what happens to the millions of developers whose entire identity was built around being the person who writes it.

Shruti

10,913 просмотров • 29 дней назад

A dude who fixes phones for a living built himself an actual Jarvis. I'm not saying "like Jarvis." I'm saying his room wakes up at 5:40 AM and starts doing things by itself. Screens turn on. Invoices go out. Calendar sorts itself. Clients get reminders he never wrote. He's not even in the room yet. He can't code. At all. He talked to AI for one weekend and told it what he wants. That's it. The AI built everything. Now he has an app making $30,000 a month and a system that runs his entire life while he sits there deciding what to do with his day. He quit fixing phones two months ago. Every single person who's seen his setup says the same thing. "I want one." Yeah. Me too. It's free. One evening to set up.

A dude who fixes phones for a living built himself an actual Jarvis. I'm not saying "like Jarvis." I'm saying his room wakes up at 5:40 AM and starts doing things by itself. Screens turn on. Invoices go out. Calendar sorts itself. Clients get reminders he never wrote. He's not even in the room yet. He can't code. At all. He talked to AI for one weekend and told it what he wants. That's it. The AI built everything. Now he has an app making $30,000 a month and a system that runs his entire life while he sits there deciding what to do with his day. He quit fixing phones two months ago. Every single person who's seen his setup says the same thing. "I want one." Yeah. Me too. It's free. One evening to set up.

Raytar

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

Beethoven could not hear the music he wrote. At the age of 28, he realized he was no longer able to listen to a flute being played in the distance, and he spent the rest of his life composing the most enduring music in Western history in almost complete silence... He had been a working musician since childhood. His ears were everything. In 1798, in the middle of a heated argument with a singer, he noticed for the first time that something was wrong. The sound was thinning at the edges. He could hear voices, but high frequencies were beginning to disappear. He told no one for years. By 1802, the truth was no longer deniable. On his doctor's advice he moved to Heiligenstadt, a quiet village outside Vienna, hoping the country air would help. It did not. There, alone and surrounded by farmland, he wrote a letter to his two brothers that he never sent. It was found among his papers after his death. We now call it the Heiligenstadt Testament, and it is one of the most devastating documents ever written by an artist about himself: "You men who think or say that I am malevolent, stubborn or misanthropic, how greatly do you wrong me. You do not know the cause of my seeming so... what a humiliation, when one stood beside me and heard a flute in the distance and I heard nothing, or someone heard the shepherd singing, and again I heard nothing." He wrote, in the same letter, that he had thought of ending his life. And then he wrote the line that explains everything that followed: "Only my art held me back. It seemed impossible to me to leave the world before I had produced everything I felt called upon to produce." He went back to Vienna. He went on composing. Over the next two decades his hearing continued to fade. Friends began writing their words down in small notebooks instead of speaking them aloud, and waiting while he read. Modern scholars call these the conversation books. Around four hundred of them survive. To compose, he developed his own methods. He bit one end of a wooden rod and pressed the other against the soundboard of his piano, letting the vibrations travel through his jaw to his inner ear. He had stumbled, through trial and error, onto the principle that modern science calls bone conduction. The cause of his deafness has never been settled. What we do know is this: he realized he was losing his hearing at twenty-eight, and he could have stopped. He wrote the letter, he held the thought of dying in his hand, and then he put down the pen and went back to work. Most of what he is remembered for was composed after that moment: The Fifth Symphony. The Seventh. The Ninth. The Missa Solemnis. The late quartets. All of it was made by a man who could no longer hear most of what he was writing. There are people who give the world what they receive, and there are people who give the world what they were never able to receive. The most enduring beauty in human history has almost always come from the second kind... -- -- -- If you enjoyed this, I write a weekly newsletter read by over 50,000 people who love rediscovering the beauty of the past. You can join us here: I write about beauty in all its forms. If you'd like to support my work, a paid subscription is what makes it possible.

Beethoven could not hear the music he wrote. At the age of 28, he realized he was no longer able to listen to a flute being played in the distance, and he spent the rest of his life composing the most enduring music in Western history in almost complete silence... He had been a working musician since childhood. His ears were everything. In 1798, in the middle of a heated argument with a singer, he noticed for the first time that something was wrong. The sound was thinning at the edges. He could hear voices, but high frequencies were beginning to disappear. He told no one for years. By 1802, the truth was no longer deniable. On his doctor's advice he moved to Heiligenstadt, a quiet village outside Vienna, hoping the country air would help. It did not. There, alone and surrounded by farmland, he wrote a letter to his two brothers that he never sent. It was found among his papers after his death. We now call it the Heiligenstadt Testament, and it is one of the most devastating documents ever written by an artist about himself: "You men who think or say that I am malevolent, stubborn or misanthropic, how greatly do you wrong me. You do not know the cause of my seeming so... what a humiliation, when one stood beside me and heard a flute in the distance and I heard nothing, or someone heard the shepherd singing, and again I heard nothing." He wrote, in the same letter, that he had thought of ending his life. And then he wrote the line that explains everything that followed: "Only my art held me back. It seemed impossible to me to leave the world before I had produced everything I felt called upon to produce." He went back to Vienna. He went on composing. Over the next two decades his hearing continued to fade. Friends began writing their words down in small notebooks instead of speaking them aloud, and waiting while he read. Modern scholars call these the conversation books. Around four hundred of them survive. To compose, he developed his own methods. He bit one end of a wooden rod and pressed the other against the soundboard of his piano, letting the vibrations travel through his jaw to his inner ear. He had stumbled, through trial and error, onto the principle that modern science calls bone conduction. The cause of his deafness has never been settled. What we do know is this: he realized he was losing his hearing at twenty-eight, and he could have stopped. He wrote the letter, he held the thought of dying in his hand, and then he put down the pen and went back to work. Most of what he is remembered for was composed after that moment: The Fifth Symphony. The Seventh. The Ninth. The Missa Solemnis. The late quartets. All of it was made by a man who could no longer hear most of what he was writing. There are people who give the world what they receive, and there are people who give the world what they were never able to receive. The most enduring beauty in human history has almost always come from the second kind... -- -- -- If you enjoyed this, I write a weekly newsletter read by over 50,000 people who love rediscovering the beauty of the past. You can join us here: I write about beauty in all its forms. If you'd like to support my work, a paid subscription is what makes it possible.

James Lucas

153,966 просмотров • 2 месяцев назад

A Chinese mathematician posted a 3 minute video on Bilibili explaining how he lost his $10,000 a month gig to AI. The model he had been training started writing harder math problems than he could invent. He admitted his own mistake in business positioning. He had spent four years hand writing PhD level math problems for Scale AI's reinforcement learning pipeline. $50 to $100 per problem. 200 problems a month. Then synthetic data killed his entire contract category. He was no longer able to invent a problem the machine could not solve. At 2:13 he says the word agent. He says it once. He never says it again in the video. The way he says it is the only thing on screen that did not come off the teleprompter. He has been recording videos off a teleprompter for three months. The teleprompter runs on the same agent that killed his Scale AI work. Every script is generated by Claude. Every word he reads to camera is the agent's. The new job is reading. Someone pulled the script repository from a Cursor instance the dev had left public. The folder was labeled bilibili-laments. Inside were 47 video scripts. All in his voice. All written by Claude. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The mathematician had been one of them. He had wired the agent into his content pipeline the week Scale AI cut him off. He had been a PhD candidate at one of the top five Chinese math schools. He taught there for two years before going full time on Scale AI contracts. He still has the credentials. He still has the office. He just no longer writes anything. He wanted to show people how AI took his career. He accidentally showed them how AI also took his post mortem.

A Chinese mathematician posted a 3 minute video on Bilibili explaining how he lost his $10,000 a month gig to AI. The model he had been training started writing harder math problems than he could invent. He admitted his own mistake in business positioning. He had spent four years hand writing PhD level math problems for Scale AI's reinforcement learning pipeline. $50 to $100 per problem. 200 problems a month. Then synthetic data killed his entire contract category. He was no longer able to invent a problem the machine could not solve. At 2:13 he says the word agent. He says it once. He never says it again in the video. The way he says it is the only thing on screen that did not come off the teleprompter. He has been recording videos off a teleprompter for three months. The teleprompter runs on the same agent that killed his Scale AI work. Every script is generated by Claude. Every word he reads to camera is the agent's. The new job is reading. Someone pulled the script repository from a Cursor instance the dev had left public. The folder was labeled bilibili-laments. Inside were 47 video scripts. All in his voice. All written by Claude. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The mathematician had been one of them. He had wired the agent into his content pipeline the week Scale AI cut him off. He had been a PhD candidate at one of the top five Chinese math schools. He taught there for two years before going full time on Scale AI contracts. He still has the credentials. He still has the office. He just no longer writes anything. He wanted to show people how AI took his career. He accidentally showed them how AI also took his post mortem.

Carver

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

A developer pointed Claude Code at a 6,200-note Obsidian vault and let it run overnight. The vault was 4 years of markdown. Meeting notes, half-ideas, book highlights. Dead weight. He hadn't opened 90% of it since 2022. He typed one line into the terminal. "Read everything. Find what I forgot." Then he went to bed. By 7 AM, Claude Code had touched all 6,200 files. It wrote 3 new notes. The first mapped 14 ideas scattered across 3 years into one product. He'd never seen they connected. The second listed 22 promises he'd made in old meeting notes and never kept. The third was a full essay. Stitched from 40 fragments. In his own phrasing. He hadn't written a note in 8 months. The vault had been writing itself the whole time. He just couldn't read his own handwriting at scale. Now Claude Code opens the vault every morning at 6:00. It links new notes to old ones. It flags contradictions. It drafts. 2 tools. 1 folder of plain text. No app, no cloud, no subscription. He stopped taking notes to remember them. He takes them now to be read back.

A developer pointed Claude Code at a 6,200-note Obsidian vault and let it run overnight. The vault was 4 years of markdown. Meeting notes, half-ideas, book highlights. Dead weight. He hadn't opened 90% of it since 2022. He typed one line into the terminal. "Read everything. Find what I forgot." Then he went to bed. By 7 AM, Claude Code had touched all 6,200 files. It wrote 3 new notes. The first mapped 14 ideas scattered across 3 years into one product. He'd never seen they connected. The second listed 22 promises he'd made in old meeting notes and never kept. The third was a full essay. Stitched from 40 fragments. In his own phrasing. He hadn't written a note in 8 months. The vault had been writing itself the whole time. He just couldn't read his own handwriting at scale. Now Claude Code opens the vault every morning at 6:00. It links new notes to old ones. It flags contradictions. It drafts. 2 tools. 1 folder of plain text. No app, no cloud, no subscription. He stopped taking notes to remember them. He takes them now to be read back.

Spike 1%

18,613 просмотров • 5 дней назад

Marc Andreessen says if he were 18 right now, AI is "100% what I would be spending all of my time on." When the co-founder of a16z shares his opinion on what to do in tech, you listen. When he looks at AI today, he sees something that has never existed before in the history of software. AI agents can operate with very little human involvement. The reason is they can run on a Unix shell, the same command line system that has powered computers for decades. With a single instruction from you, it can access your files, your network, and your devices. Or you can instruct it to rewrite its own code. And even if it needs a new capability, you can allow it to write the code itself and install it. Here's a real example of this happening: One of his friends had his agent rewrite the firmware on a robot dog that could barely climb stairs. The agent rebuilt the entire control system. The dog is now a functional pet for his kids, and whenever something breaks, the agent just fixes the code again. Andreessen says no widely deployed software system in history has ever been able to understand and modify itself like this. He calls it "an incredible conceptual breakthrough." — Marc Andreessen (Marc Andreessen 🇺🇸), co-founder at a16z (a16z) on the Latent Space podcast (Latent.Space)

Marc Andreessen says if he were 18 right now, AI is "100% what I would be spending all of my time on." When the co-founder of a16z shares his opinion on what to do in tech, you listen. When he looks at AI today, he sees something that has never existed before in the history of software. AI agents can operate with very little human involvement. The reason is they can run on a Unix shell, the same command line system that has powered computers for decades. With a single instruction from you, it can access your files, your network, and your devices. Or you can instruct it to rewrite its own code. And even if it needs a new capability, you can allow it to write the code itself and install it. Here's a real example of this happening: One of his friends had his agent rewrite the firmware on a robot dog that could barely climb stairs. The agent rebuilt the entire control system. The dog is now a functional pet for his kids, and whenever something breaks, the agent just fixes the code again. Andreessen says no widely deployed software system in history has ever been able to understand and modify itself like this. He calls it "an incredible conceptual breakthrough." — Marc Andreessen (Marc Andreessen 🇺🇸), co-founder at a16z (a16z) on the Latent Space podcast (Latent.Space)

GeniusThinking

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

THIS GUY CONNECTED CLAUDE VOICE MODE TO CLAUDE CODE AND NOW HE CODES BY TALKING INTO HIS AIRPODS while doing whatever he wants he uses Apple Reminders as a bridge between the two he talks into his AirPods, voice mode puts the prompt into a reminders list, Claude Code checks every 60 seconds and picks up the task AND it starts working on it back at his desk. walk outside. brainstorm with voice. code writes itself on your computer at home. he said he does his best thinking while walking and this lets him act on it instantly without pulling out his phone or sitting down. not a developer btw and he vibe coded the whole bridge system too. this is what hands-free vibe coding actually looks like

THIS GUY CONNECTED CLAUDE VOICE MODE TO CLAUDE CODE AND NOW HE CODES BY TALKING INTO HIS AIRPODS while doing whatever he wants he uses Apple Reminders as a bridge between the two he talks into his AirPods, voice mode puts the prompt into a reminders list, Claude Code checks every 60 seconds and picks up the task AND it starts working on it back at his desk. walk outside. brainstorm with voice. code writes itself on your computer at home. he said he does his best thinking while walking and this lets him act on it instantly without pulling out his phone or sitting down. not a developer btw and he vibe coded the whole bridge system too. this is what hands-free vibe coding actually looks like

Om Patel

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

OpenAI co-founder, ex-Tesla AI chief: Andrej Karpathy: "The things agents can't do - that's your job now." Three things he said in an hour. The third splits the room. One: no hand-written code since December. Sixteen hours a day he just directs agents. He calls it AI psychosis. Two: apps are dead. His agent reverse-engineered his house and replaced six of them. Three is your job. Save it. Then bet: do your skills outlive his agents?

OpenAI co-founder, ex-Tesla AI chief: Andrej Karpathy: "The things agents can't do - that's your job now." Three things he said in an hour. The third splits the room. One: no hand-written code since December. Sixteen hours a day he just directs agents. He calls it AI psychosis. Two: apps are dead. His agent reverse-engineered his house and replaced six of them. Three is your job. Save it. Then bet: do your skills outlive his agents?

shmidt

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

Hitler speech 1922: “…he knows well enough his economics brings no blessing: his is no chosen people: he is an exploiter: the jews are a people of robbers. He has never founded any civilization, though he has destroyed civilizations by the hundred. He possesses nothing of his own creation to which he can point. Everything that he has is stolen. Foreign peoples, foreign workmen build him his temples, it is foreigners who create and work for him: it is foreigners who shed their blood for him. He knows no ‘people’s army’: he has only hired mercenaries who are ready to go to death on his behalf. He has no art of his own: bit by bit he has stolen it all from the other peoples or has watched them at work and then made his copy. He does not even know how merely to preserve the precious things which others have created: as he turns the treasures over in his hand they are transformed into dirt and dung.” Educational/historical purposes only

Hitler speech 1922: “…he knows well enough his economics brings no blessing: his is no chosen people: he is an exploiter: the jews are a people of robbers. He has never founded any civilization, though he has destroyed civilizations by the hundred. He possesses nothing of his own creation to which he can point. Everything that he has is stolen. Foreign peoples, foreign workmen build him his temples, it is foreigners who create and work for him: it is foreigners who shed their blood for him. He knows no ‘people’s army’: he has only hired mercenaries who are ready to go to death on his behalf. He has no art of his own: bit by bit he has stolen it all from the other peoples or has watched them at work and then made his copy. He does not even know how merely to preserve the precious things which others have created: as he turns the treasures over in his hand they are transformed into dirt and dung.” Educational/historical purposes only

Truth Troll Official™️

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

$Tom Crawshaw has been building automations for 9 years with $25 million in client revenue to his name. He just walked me through his Claude Code content system that's generating millions of views and tens of thousands of followers. Here's what I learned: 1. Skills beat Projects in Claude. Projects load every context file on every message and burn your token window. Skills work like a book where the LLM reads the table of contents and pulls only the chapter it needs for the job. Same context, fraction of the tokens. 2. He has a /content-create slash command that runs the entire pipeline. Voice profile, copywriting principles, hook generation, image direction. One command. He doesn't write anything from scratch anymore. 3. His voice profile auto-updates weekly. He wrote a script that hits the X API every 7 days, pulls his top-performing posts by engagement, and rewrites his voice profile based on what's actually working. The profile evolves on its own. 4. He distilled a master copywriter's entire body of work into a single markdown file. Grabbed every Alen Sultanic post he could find, dropped it into Claude, asked for the core principles, fed it into the skill. Now every post he writes runs through those principles automatically. 5. The hook generator scores 16 hooks per post against 7 criteria. Curiosity loops, specificity, sensory, credibility, voice match, and a couple of others. He never picks the #1 by default. Sometimes he splices the first line of one hook with the body of another. The taste is still his. 6. /insights is a native Claude Code command nobody talks about. It analyzes every session you've ever run and produces a full report on your usage patterns, where things break down, and prompts you can paste back into Claude to fix them. I had never heard of it. I'm running it tonight. 7. He spends most of his time on hooks and images. If those two suck, the body copy doesn't matter. Nobody reads it. 8. Image generation is never one-shot. He keeps a folder of reference images that have worked before and feeds them into Nano Banana/GPT Image 2 every time. Then he takes the 80-90% output and finishes it in Canva using "magic grab" to move logos and clean up text. Last mile is human every time. 9. The humanizer step is non-negotiable. Strip em dashes. Kill the "it's not X, it's Y" pattern. Cut the triple negatives. Cut "no fluff." He still has to remind Claude mid-session because it drifts. If you're not auditing for AI tells, you're shipping slop. 10. Wisprflow is the most important tool in his stack. Not a content tool. An everything tool. His test for whether you should be using it: do you talk faster than you type? You do. Everyone does. Bonus fact he dropped: QWERTY was designed 200 years ago to slow typing down so old typewriters wouldn't jam. We've been carrying that forward ever since. Voice is finally undoing it. This was an inside look at how a serious operator Tom is using Claude Code to run a content engine. The good, the bad, the iteration, all of it. I hope you enjoy this one as much as I did. Go watch it.$

Tom Crawshaw has been building automations for 9 years with $25 million in client revenue to his name. He just walked me through his Claude Code content system that's generating millions of views and tens of thousands of followers. Here's what I learned: 1. Skills beat Projects in Claude. Projects load every context file on every message and burn your token window. Skills work like a book where the LLM reads the table of contents and pulls only the chapter it needs for the job. Same context, fraction of the tokens. 2. He has a /content-create slash command that runs the entire pipeline. Voice profile, copywriting principles, hook generation, image direction. One command. He doesn't write anything from scratch anymore. 3. His voice profile auto-updates weekly. He wrote a script that hits the X API every 7 days, pulls his top-performing posts by engagement, and rewrites his voice profile based on what's actually working. The profile evolves on its own. 4. He distilled a master copywriter's entire body of work into a single markdown file. Grabbed every Alen Sultanic post he could find, dropped it into Claude, asked for the core principles, fed it into the skill. Now every post he writes runs through those principles automatically. 5. The hook generator scores 16 hooks per post against 7 criteria. Curiosity loops, specificity, sensory, credibility, voice match, and a couple of others. He never picks the #1 by default. Sometimes he splices the first line of one hook with the body of another. The taste is still his. 6. /insights is a native Claude Code command nobody talks about. It analyzes every session you've ever run and produces a full report on your usage patterns, where things break down, and prompts you can paste back into Claude to fix them. I had never heard of it. I'm running it tonight. 7. He spends most of his time on hooks and images. If those two suck, the body copy doesn't matter. Nobody reads it. 8. Image generation is never one-shot. He keeps a folder of reference images that have worked before and feeds them into Nano Banana/GPT Image 2 every time. Then he takes the 80-90% output and finishes it in Canva using "magic grab" to move logos and clean up text. Last mile is human every time. 9. The humanizer step is non-negotiable. Strip em dashes. Kill the "it's not X, it's Y" pattern. Cut the triple negatives. Cut "no fluff." He still has to remind Claude mid-session because it drifts. If you're not auditing for AI tells, you're shipping slop. 10. Wisprflow is the most important tool in his stack. Not a content tool. An everything tool. His test for whether you should be using it: do you talk faster than you type? You do. Everyone does. Bonus fact he dropped: QWERTY was designed 200 years ago to slow typing down so old typewriters wouldn't jam. We've been carrying that forward ever since. Voice is finally undoing it. This was an inside look at how a serious operator Tom is using Claude Code to run a content engine. The good, the bad, the iteration, all of it. I hope you enjoy this one as much as I did. Go watch it.

Corey Ganim

36,120 просмотров • 2 месяцев назад

An 18 year old told his dad he needed an Apple Vision Pro for university. Dad said that's a $3,500 movie headset, you don't need it for school. He said it runs macOS apps natively. Dad didn't know what that means. Bought it for graduation. $3,500. He never watched a single movie on it. Installed VS Code and Claude Code the same night. Threw six floating screens around his bedroom. Lay down in bed and started coding from under the sheets with his bare hands tapping air. His roommate walked in at 2am and saw him lying in bed wearing a headset waving his hands at nothing. Thought he was losing his mind. He was building a client website. At second 0:11 you can see his hand swipe across a floating file explorer. Behind it five more windows are open. All running Claude Code agents on different projects. One building, one testing, one deploying, one reviewing, one handling client messages. All floating above his bed like a command center in a sci-fi movie. The website color change was the demo he filmed. The five windows behind it were the actual business. Within a month he was running projects for seven clients. A restaurant site, an appointment app for a dentist, a landing page for a real estate agent, a dashboard for a gym owner. All built from bed. All coded by Claude while he gave instructions by tapping floating windows above his pillow. $11,400 in his first month. His dad makes $9,200 at his engineering job. His dad called last weekend and asked if the headset was worth it. He said yeah the movies are great. His dad said good, at least you're relaxing after studying. He wasn't studying. He wasn't watching movies. He was lying in bed while five Claude Code agents built software in floating windows above his face. A developer in New York rents a $2,800 apartment just to have a home office with two monitors. This kid has six floating screens that follow him from bed to couch to kitchen and cost nothing after the headset. His mom asked to try the Vision Pro last Sunday. Put it on and saw six VS Code windows floating in the living room, git commits scrolling, Claude mid-task on three projects. She took it off and said I thought this was for watching movies. He said it is. Just not the kind she was thinking of. Setup time: one evening. Screens: six, floating, invisible to everyone else in the room. Money made in month one: $11,400. Movies watched: zero. His dad is still paying off the $3,500. The headset paid for itself in 9 days. Dad doesn't know that yet. He will when his son offers to pay him back.

An 18 year old told his dad he needed an Apple Vision Pro for university. Dad said that's a $3,500 movie headset, you don't need it for school. He said it runs macOS apps natively. Dad didn't know what that means. Bought it for graduation. $3,500. He never watched a single movie on it. Installed VS Code and Claude Code the same night. Threw six floating screens around his bedroom. Lay down in bed and started coding from under the sheets with his bare hands tapping air. His roommate walked in at 2am and saw him lying in bed wearing a headset waving his hands at nothing. Thought he was losing his mind. He was building a client website. At second 0:11 you can see his hand swipe across a floating file explorer. Behind it five more windows are open. All running Claude Code agents on different projects. One building, one testing, one deploying, one reviewing, one handling client messages. All floating above his bed like a command center in a sci-fi movie. The website color change was the demo he filmed. The five windows behind it were the actual business. Within a month he was running projects for seven clients. A restaurant site, an appointment app for a dentist, a landing page for a real estate agent, a dashboard for a gym owner. All built from bed. All coded by Claude while he gave instructions by tapping floating windows above his pillow. $11,400 in his first month. His dad makes $9,200 at his engineering job. His dad called last weekend and asked if the headset was worth it. He said yeah the movies are great. His dad said good, at least you're relaxing after studying. He wasn't studying. He wasn't watching movies. He was lying in bed while five Claude Code agents built software in floating windows above his face. A developer in New York rents a $2,800 apartment just to have a home office with two monitors. This kid has six floating screens that follow him from bed to couch to kitchen and cost nothing after the headset. His mom asked to try the Vision Pro last Sunday. Put it on and saw six VS Code windows floating in the living room, git commits scrolling, Claude mid-task on three projects. She took it off and said I thought this was for watching movies. He said it is. Just not the kind she was thinking of. Setup time: one evening. Screens: six, floating, invisible to everyone else in the room. Money made in month one: $11,400. Movies watched: zero. His dad is still paying off the $3,500. The headset paid for itself in 9 days. Dad doesn't know that yet. He will when his son offers to pay him back.

Marlow

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

ONE OF CLAUDE'S DEVELOPERS SHOWED HIS SETUP. HE DOESN'T USE CLAUDE THE WAY YOU DO he didn't post this on twitter. didn't make a thread. just showed his setup on a call and someone recorded it and when i saw what was inside, i understood why he never starts a conversation with claude from scratch the first file in his vault is called CLAUDE.md. it's not a note. it's a full profile: who he is, how he thinks, where he gets stuck, what projects he's running, how he wants to be talked to. claude loads this file automatically every session meaning the ai doesn't ask "how can i help?" he opens a conversation and claude is already in context. knows his goals. remembers what he postponed two months ago. sees where he's contradicting himself and that's just the beginning every project is its own folder with a clean structure: inputs, process, outputs, feedback. when he works on something, he opens only that folder. claude sees one project, not the chaos of his entire life anything he does more than once is saved as a skill. email a client, break down a call, prep a document. one line and claude does it his way and at 7am every day claude walks through the entire vault on its own. files new stuff. links it. flags what's gone stale. writes him 3 lines: what changed overnight he wakes up and the brain already worked and here's what got me the most: it's all just text files. no cloud. no lock-in. if a better model drops tomorrow, he points it at the same folder and everything keeps working he basically uploaded himself into a file system. and now ai doesn't guess who he is. ai knows most people use claude like google with manners. this guy built himself an external memory that grows every day i break down finds like this every day - follow so you don't miss the next one

kai

110,412 просмотров • 10 дней назад

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,104 просмотров • 24 дней назад

Marimar Martinez, the Chicago woman whom a Border Patrol agent shot five times last year, says she was only at the hospital for three hours before agents rushed her out. She then was admitted to a second hospital because she was through from her bandages. "As we left the hospital, I was escorted out through the back in a wheelchair. I observed over dozens of border patrol agents waiting outside the hospital. One of them, one of the agents came up to me with his cell phone and took a photograph of me. It was the same agent who had previously kept coming in and out of my room, and I had to repeatedly tell him to leave. I told him I did not consent for him to photograph me, but he did not care. It still haunts me that this agent has my photo on his phone. Was this the agent that shot me? Was this a trophy for him?"

Marimar Martinez, the Chicago woman whom a Border Patrol agent shot five times last year, says she was only at the hospital for three hours before agents rushed her out. She then was admitted to a second hospital because she was through from her bandages. "As we left the hospital, I was escorted out through the back in a wheelchair. I observed over dozens of border patrol agents waiting outside the hospital. One of them, one of the agents came up to me with his cell phone and took a photograph of me. It was the same agent who had previously kept coming in and out of my room, and I had to repeatedly tell him to leave. I told him I did not consent for him to photograph me, but he did not care. It still haunts me that this agent has my photo on his phone. Was this the agent that shot me? Was this a trophy for him?"

Heartland Signal

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

Everyone calls Fredo the weak one. Watch that scene again. His father gets shot in the street and Fredo freezes. He fumbles his gun, drops it, ends up on the curb crying like a kid. For most people that settles it: he's useless, he's not built for this life. But that's the point. Fredo was never meant to be strong, or smart. He wasn't Sonny. He wasn't Michael. He was an ordinary man who happened to have the Godfather for a father. So when the shooting starts, he does what most of us would do. He panics. He breaks. The same softness that made him a bad gangster was the one thing the family had no room for. Michael runs the business better than any of them ever could. But the day he loses Fredo, he loses the last soft thing left in him. A family can't run on business alone. Fredo was the proof. Nobody saw it until he was gone

Everyone calls Fredo the weak one. Watch that scene again. His father gets shot in the street and Fredo freezes. He fumbles his gun, drops it, ends up on the curb crying like a kid. For most people that settles it: he's useless, he's not built for this life. But that's the point. Fredo was never meant to be strong, or smart. He wasn't Sonny. He wasn't Michael. He was an ordinary man who happened to have the Godfather for a father. So when the shooting starts, he does what most of us would do. He panics. He breaks. The same softness that made him a bad gangster was the one thing the family had no room for. Michael runs the business better than any of them ever could. But the day he loses Fredo, he loses the last soft thing left in him. A family can't run on business alone. Fredo was the proof. Nobody saw it until he was gone

best of mafia cinema

96,650 просмотров • 16 дней назад