Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

AN ANTHROPIC LEAD ENGINEER ACCIDENTALLY LEAKED HIS PERSONAL OBSIDIAN. INSIDE - NOT CODE OR PROMPTS, BUT A DIAGRAM OF HIS OWN BRAIN, ORGANIZED AS A NEURAL NETWORK 8,893 nodes. 4,729 connections. A $10/month app opens Obsidian. 21 inputs, ReLU on every layer. The first hidden layer has 26 neurons,...

chewadot's profile picture

chewa.

3,511 subscribers

309,244 görüntüleme • 2 gün önce •via X (Twitter)

Bilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

ANTHROPIC'S LEAD ENGINEER ACCIDENTALLY LEAKED HIS PERSONAL OBSIDIAN VAULT. INSIDE - NO CODE, NO PROMPTS. JUST A SCHEMATIC OF HIS OWN MIND, BUILT LIKE A NEURAL NETWORK 8,893 nodes. 4,729 links. A $10-a-month app opens Obsidian. 21 inputs, 10+ hidden layers, ReLU activation. First layer 64 neurons, then 37, then 22, all the way to the output. Thousands of connections firing in real time this isn't a concept diagram from a blog - it's a living brain that actually runs decisions inside the company. 9,000 documents, each its own knowledge space, all interconnected he makes around $2M a year for putting markdown files into the right folders. The company building the best AI in the world manages its internal knowledge with the same app a college freshman uses for lecture notes. hasn't written a single line of infrastructure for any of it. three years of discipline and one open Obsidian tab you're reading this on a device where you could open the same Obsidian tonight and start building your own vault
0:10

ANTHROPIC'S LEAD ENGINEER ACCIDENTALLY LEAKED HIS PERSONAL OBSIDIAN VAULT. INSIDE - NO CODE, NO PROMPTS. JUST A SCHEMATIC OF HIS OWN MIND, BUILT LIKE A NEURAL NETWORK 8,893 nodes. 4,729 links. A $10-a-month app opens Obsidian. 21 inputs, 10+ hidden layers, ReLU activation. First layer 64 neurons, then 37, then 22, all the way to the output. Thousands of connections firing in real time this isn't a concept diagram from a blog - it's a living brain that actually runs decisions inside the company. 9,000 documents, each its own knowledge space, all interconnected he makes around $2M a year for putting markdown files into the right folders. The company building the best AI in the world manages its internal knowledge with the same app a college freshman uses for lecture notes. hasn't written a single line of infrastructure for any of it. three years of discipline and one open Obsidian tab you're reading this on a device where you could open the same Obsidian tonight and start building your own vault

chewa.

1,204,047 görüntüleme • 11 gün önce

HERMES AGENT HAS A SECOND BRAIN. 1,100+ KNOWLEDGE FILES. AUTO-LINKED. SELF-IMPROVING. GROWING EVERY NIGHT. THIS IS THE OBSIDIAN GRAPH BEHIND IT. every dot = one knowledge file (markdown) every line = one wiki-link between files every color = one category (skills, notes, decisions, sources, entities) HOW IT BUILDS ITSELF: Hermes ships with a bundled LLM Wiki skill. based on Andrej Karpathy's pattern. unlike RAG (rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. when you feed the agent a source: → it reads the content → writes a structured markdown page → auto-links to every related existing page → flags contradictions with previous entries → updates all affected pages one source in. multiple connections created. the graph grows denser with every entry. WHAT FEEDS THE WIKI: → articles and URLs you find interesting → meeting transcripts → PDF documents and research papers → conversation history from Hermes sessions → Claude Code and Codex session history → Slack logs, email threads, saved notes → YouTube transcripts → raw text dropped into a _raw/ folder the obsidian-wiki package supports multi-agent ingest from Hermes, Claude Code, Codex, OpenClaw, Pi, Windsurf, and ChatGPT exports. install: pip install obsidian-wiki obsidian-wiki setup --vault ~/wiki AUTOMATE THE GROWTH: set cron jobs to feed the wiki overnight: "every day at 9am, check for new meetings. ingest transcripts into the wiki." "every week, check arXiv for new papers in [niche]. summarize and file into the wiki." "every day, ingest today's Hermes sessions into the wiki under session-history." month 1: 50 entries. scattered. month 3: 300+ entries. cross-referenced. month 6: 1,000+ entries. the agent surfaces patterns you never searched for. WHY OBSIDIAN: the wiki is plain markdown files. no database. no lock-in. open it in Obsidian for graph view: → nodes show knowledge density → links show how ideas connect → clusters reveal your strongest domains → orphan nodes reveal gaps Hermes writes from a VPS. Obsidian reads on your laptop. obsidian-headless syncs without a GUI. agent writes from the server, you browse on your device. FOUR MEMORY LAYERS: Layer 1: memory.md + user.md (~2,200 + 1,375 chars. short-term.) Layer 2: SQLite with FTS5 (full session transcripts. searchable.) Layer 3: external providers (Mem0, SuperMemory, Honcho. optional.) Layer 4: Obsidian wiki via LLM Wiki skill (unlimited. compounding. the long-term brain.) layers 1-3 handle memory. layer 4 handles knowledge. the graph in this post is layer 4. SETUP: set in Desktop app, Dashboard, or config.yaml: WIKI_PATH=~/wiki OBSIDIAN_VAULT_PATH=~/wiki first run: Hermes asks for your domain. answer with your niche. the skill builds SCHEMA.md with tag taxonomy. after that: "index this into my wiki: [URL or text]" the wiki grows. the graph densifies. the agent gets smarter because the knowledge base got smarter. full 15 levels breakdown in the article 👇
0:11

HERMES AGENT HAS A SECOND BRAIN. 1,100+ KNOWLEDGE FILES. AUTO-LINKED. SELF-IMPROVING. GROWING EVERY NIGHT. THIS IS THE OBSIDIAN GRAPH BEHIND IT. every dot = one knowledge file (markdown) every line = one wiki-link between files every color = one category (skills, notes, decisions, sources, entities) HOW IT BUILDS ITSELF: Hermes ships with a bundled LLM Wiki skill. based on Andrej Karpathy's pattern. unlike RAG (rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. when you feed the agent a source: → it reads the content → writes a structured markdown page → auto-links to every related existing page → flags contradictions with previous entries → updates all affected pages one source in. multiple connections created. the graph grows denser with every entry. WHAT FEEDS THE WIKI: → articles and URLs you find interesting → meeting transcripts → PDF documents and research papers → conversation history from Hermes sessions → Claude Code and Codex session history → Slack logs, email threads, saved notes → YouTube transcripts → raw text dropped into a _raw/ folder the obsidian-wiki package supports multi-agent ingest from Hermes, Claude Code, Codex, OpenClaw, Pi, Windsurf, and ChatGPT exports. install: pip install obsidian-wiki obsidian-wiki setup --vault ~/wiki AUTOMATE THE GROWTH: set cron jobs to feed the wiki overnight: "every day at 9am, check for new meetings. ingest transcripts into the wiki." "every week, check arXiv for new papers in [niche]. summarize and file into the wiki." "every day, ingest today's Hermes sessions into the wiki under session-history." month 1: 50 entries. scattered. month 3: 300+ entries. cross-referenced. month 6: 1,000+ entries. the agent surfaces patterns you never searched for. WHY OBSIDIAN: the wiki is plain markdown files. no database. no lock-in. open it in Obsidian for graph view: → nodes show knowledge density → links show how ideas connect → clusters reveal your strongest domains → orphan nodes reveal gaps Hermes writes from a VPS. Obsidian reads on your laptop. obsidian-headless syncs without a GUI. agent writes from the server, you browse on your device. FOUR MEMORY LAYERS: Layer 1: memory.md + user.md (~2,200 + 1,375 chars. short-term.) Layer 2: SQLite with FTS5 (full session transcripts. searchable.) Layer 3: external providers (Mem0, SuperMemory, Honcho. optional.) Layer 4: Obsidian wiki via LLM Wiki skill (unlimited. compounding. the long-term brain.) layers 1-3 handle memory. layer 4 handles knowledge. the graph in this post is layer 4. SETUP: set in Desktop app, Dashboard, or config.yaml: WIKI_PATH=~/wiki OBSIDIAN_VAULT_PATH=~/wiki first run: Hermes asks for your domain. answer with your niche. the skill builds SCHEMA.md with tag taxonomy. after that: "index this into my wiki: [URL or text]" the wiki grows. the graph densifies. the agent gets smarter because the knowledge base got smarter. full 15 levels breakdown in the article 👇

YanXbt

34,368 görüntüleme • 22 gün önce

THIS GUY HAD 1,283 NOTES AND HIS SYSTEM WAS DUMBER THAN A FOLDER that galaxy in the background is his Obsidian vault > looks incredible > does nothing dead notes, zero connections, zero value extracted from any of it > the fix isn't taking better notes > it's building a pipeline where Claude Opus 4.8 does the research, NotebookLM does the analysis, and every session feeds your vault automatically one command: > Claude Code searches YouTube for 10 relevant sources > passes them to NotebookLM - Google's servers do the heavy processing, not your tokens > NotebookLM runs full analysis, generates infographics, mindmaps, flashcards > everything lands as structured markdown in your Obsidian vault, linked and ready total time: 6 minutes > after a month the vault knows your thinking style. after a year it's a trained research assistant the $300K AI architects aren't taking better notes > they're building systems that compound 30-minute setup. full step-by-step in the article below 👇
0:12

THIS GUY HAD 1,283 NOTES AND HIS SYSTEM WAS DUMBER THAN A FOLDER that galaxy in the background is his Obsidian vault > looks incredible > does nothing dead notes, zero connections, zero value extracted from any of it > the fix isn't taking better notes > it's building a pipeline where Claude Opus 4.8 does the research, NotebookLM does the analysis, and every session feeds your vault automatically one command: > Claude Code searches YouTube for 10 relevant sources > passes them to NotebookLM - Google's servers do the heavy processing, not your tokens > NotebookLM runs full analysis, generates infographics, mindmaps, flashcards > everything lands as structured markdown in your Obsidian vault, linked and ready total time: 6 minutes > after a month the vault knows your thinking style. after a year it's a trained research assistant the $300K AI architects aren't taking better notes > they're building systems that compound 30-minute setup. full step-by-step in the article below 👇

Mr. Buzzoni

48,417 görüntüleme • 1 ay önce

An Asian guy discovered a method to learn any knowledge fast using AI. The key is Claude + Obsidian. Most people learn slowly: read, forget, read again, forget again. His method: use Claude to break any content into small, interconnected notes. Use Obsidian to link them, so every piece of knowledge is never isolated. Slow method: highlight books, keep going, forget after a week. Fast method: Claude breaks it into atomic notes, Obsidian links them into a network. Six months later, a new idea instantly connects to twenty things you already know. I compiled the full A–Z guide to building this second brain with Claude and Obsidian that most people have never discovered. Article below
0:17

An Asian guy discovered a method to learn any knowledge fast using AI. The key is Claude + Obsidian. Most people learn slowly: read, forget, read again, forget again. His method: use Claude to break any content into small, interconnected notes. Use Obsidian to link them, so every piece of knowledge is never isolated. Slow method: highlight books, keep going, forget after a week. Fast method: Claude breaks it into atomic notes, Obsidian links them into a network. Six months later, a new idea instantly connects to twenty things you already know. I compiled the full A–Z guide to building this second brain with Claude and Obsidian that most people have never discovered. Article below

Kirill

23,264 görüntüleme • 4 gün önce

Karpathy method + Claude Code reading your whole Obsidian vault is the smartest second brain on earth. The method is simple and brutal. If you can’t build a thing from scratch, you don’t know it. Tutorials are fake learning and your brain deletes them in 3 days. Most people ignore this. They build a second brain that just sits there, folders of notes nobody reopens, dead text. Point Claude Code at the vault and it wakes up. 5,000 notes, one mind. It reads all of it and answers in your own words and your own proofs, not a model’s guess. Then the loop closes. Want to understand neural nets? Skip the 3-hour video and ask Claude Code to build a tiny one. 200 lines from scratch. Watch it train, break a layer, watch it fail, fix it. It clicks in 20 minutes instead of 3 weeks. The second it lands the note gets written. One idea per file, linked to 10 others, dropped into the vault while the memory is still hot. Now it compounds. Month 1: is 60 notes. Month 6 is 900. Every new note pulls in old ones, so you ask anything and the answer comes from your brain, not the internet. Before: 40 tabs, 6 half read PDF, 0 retained. After: build it once, own it for life. Setup takes 4 minutes. Plain text, no lock-in. A second brain nobody reads is a graveyard. Yours just started thinking.
0:13

Karpathy method + Claude Code reading your whole Obsidian vault is the smartest second brain on earth. The method is simple and brutal. If you can’t build a thing from scratch, you don’t know it. Tutorials are fake learning and your brain deletes them in 3 days. Most people ignore this. They build a second brain that just sits there, folders of notes nobody reopens, dead text. Point Claude Code at the vault and it wakes up. 5,000 notes, one mind. It reads all of it and answers in your own words and your own proofs, not a model’s guess. Then the loop closes. Want to understand neural nets? Skip the 3-hour video and ask Claude Code to build a tiny one. 200 lines from scratch. Watch it train, break a layer, watch it fail, fix it. It clicks in 20 minutes instead of 3 weeks. The second it lands the note gets written. One idea per file, linked to 10 others, dropped into the vault while the memory is still hot. Now it compounds. Month 1: is 60 notes. Month 6 is 900. Every new note pulls in old ones, so you ask anything and the answer comes from your brain, not the internet. Before: 40 tabs, 6 half read PDF, 0 retained. After: build it once, own it for life. Setup takes 4 minutes. Plain text, no lock-in. A second brain nobody reads is a graveyard. Yours just started thinking.

West Lord

585,306 görüntüleme • 18 gün önce

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE FABLE 5 + OBSIDIAN Andrej Karpathy (openai co-founder) shared an architecture that turns Claude into a persistent second brain instead of a basic chat window how it works: > you point Claude Code at an Obsidian vault folder > you drop articles, PDFs, or video transcripts into raw folders > Claude reads the files, updates topic summaries, and cross-references everything > the knowledge base compounds like interest instead of resetting on every new chat the setup is simple: > install and create a local vault directory > open the directory in Claude Code and paste Karpathy's wiki prompt: > > let the agent generate raw, wiki, and CLAUDE.md schema directories > drop any text file into raw and tell the model to ingest it > ask questions across the whole vault and query compiled summaries this eliminates rag database overhead and keeps your local vault organized how do you manage your local knowledge base?
0:11

BUILD KARPATHY'S SECOND BRAIN WITH CLAUDE FABLE 5 + OBSIDIAN Andrej Karpathy (openai co-founder) shared an architecture that turns Claude into a persistent second brain instead of a basic chat window how it works: > you point Claude Code at an Obsidian vault folder > you drop articles, PDFs, or video transcripts into raw folders > Claude reads the files, updates topic summaries, and cross-references everything > the knowledge base compounds like interest instead of resetting on every new chat the setup is simple: > install and create a local vault directory > open the directory in Claude Code and paste Karpathy's wiki prompt: > > let the agent generate raw, wiki, and CLAUDE.md schema directories > drop any text file into raw and tell the model to ingest it > ask questions across the whole vault and query compiled summaries this eliminates rag database overhead and keeps your local vault organized how do you manage your local knowledge base?

Mr. Buzzoni

78,973 görüntüleme • 13 gün önce

HE BUILT A 100% PRIVATE SECOND BRAIN IN OBSIDIAN TO AUTOMATE HIS RESEARCH USING HERMES AGENT AND NOTEBOOKLM He visualizes his entire knowledge graph on-premise without paying for cloud subscriptions By connecting Hermes Agent and NotebookLM, developers can index hundreds of documents and generate content locally Four components of this local knowledge architecture: 1. Memory layer - set up an Obsidian PARA vault to store markdown notes and profiles 2. Agent layer - connect Hermes Agent to write files and run background scripts 3. Synthesis layer - use NotebookLM to create structured overviews from raw transcripts 4. Automation layer - trigger cron tasks to synchronize files and calendar standups The setup saves over $4,000 annually while keeping all private files offline Get the full step-by-step configuration guide and setup commands in the article below ↓
0:16

HE BUILT A 100% PRIVATE SECOND BRAIN IN OBSIDIAN TO AUTOMATE HIS RESEARCH USING HERMES AGENT AND NOTEBOOKLM He visualizes his entire knowledge graph on-premise without paying for cloud subscriptions By connecting Hermes Agent and NotebookLM, developers can index hundreds of documents and generate content locally Four components of this local knowledge architecture: 1. Memory layer - set up an Obsidian PARA vault to store markdown notes and profiles 2. Agent layer - connect Hermes Agent to write files and run background scripts 3. Synthesis layer - use NotebookLM to create structured overviews from raw transcripts 4. Automation layer - trigger cron tasks to synchronize files and calendar standups The setup saves over $4,000 annually while keeping all private files offline Get the full step-by-step configuration guide and setup commands in the article below ↓

marfin

20,603 görüntüleme • 19 gün önce

THIS GUY TURNS NOTES, DOCUMENTS, AND IDEAS INTO AN AI SECOND BRAIN the system stores all the context of your work and helps claude not forget anything how to build one yourself: install obsidian connect claude code keep your projects, notes, and sessions in one vault link similar ideas together use the graph to discover new connections as a result, claude gets memory of your projects and understands the context without you constantly having to explain everything the more you work, the smarter the system gets don’t collect notes build connections between them instead
0:16

THIS GUY TURNS NOTES, DOCUMENTS, AND IDEAS INTO AN AI SECOND BRAIN the system stores all the context of your work and helps claude not forget anything how to build one yourself: install obsidian connect claude code keep your projects, notes, and sessions in one vault link similar ideas together use the graph to discover new connections as a result, claude gets memory of your projects and understands the context without you constantly having to explain everything the more you work, the smarter the system gets don’t collect notes build connections between them instead

Marvin

24,954 görüntüleme • 1 ay önce

The company that built the car sitting next to that Waymo, the Tesla, is exactly why Waymo’s business won’t survive in the long run. You can’t compete with a company that builds its own cars from the ground up, its own AI, its own chips, its own charging network, and has real-world data from millions of vehicles with the greatest entrepreneur our of our time at the helm. I bet people will be looking back at this moment in history and say that I was right.
0:12

The company that built the car sitting next to that Waymo, the Tesla, is exactly why Waymo’s business won’t survive in the long run. You can’t compete with a company that builds its own cars from the ground up, its own AI, its own chips, its own charging network, and has real-world data from millions of vehicles with the greatest entrepreneur our of our time at the helm. I bet people will be looking back at this moment in history and say that I was right.

Teslaconomics

92,929 görüntüleme • 1 yıl önce

I HAVEN’T OPENED A SINGLE BOOK THIS MONTH. CLAUDE READ 34 OF THEM FOR ME I built a vault in Obsidian, connected Claude and added Notebooklm went to sleep woke up with flashcards, mind maps, and an AI that answers from my own notes only my friends are still highlighting pdfs manually the only thing separating us is one setup: claude + obsidian + notebooklm every idea captured. every book processed. zero knowledge lost if this is the setup you’ve been looking for - like & bookmark so you don’t lose it
0:19

I HAVEN’T OPENED A SINGLE BOOK THIS MONTH. CLAUDE READ 34 OF THEM FOR ME I built a vault in Obsidian, connected Claude and added Notebooklm went to sleep woke up with flashcards, mind maps, and an AI that answers from my own notes only my friends are still highlighting pdfs manually the only thing separating us is one setup: claude + obsidian + notebooklm every idea captured. every book processed. zero knowledge lost if this is the setup you’ve been looking for - like & bookmark so you don’t lose it

leopardracer

247,317 görüntüleme • 2 ay önce

I genuinely don't understand why everyone isn't using this yet Andrej Karpathy, a co-founder of OpenAI, posted a simple idea that hit 16 million views: stop using AI to write code, use it to build a second brain. You point Claude Code at a folder, drop in any source, an article, a transcript, a PDF, and Claude reads it, links it, and files it into a living wiki of everything you know. It compounds like interest, the more you feed it, the smarter it gets. Here's the whole thing: > Install Obsidian, create a vault, open it in Claude Code > Paste Karpathy's wiki idea file and tell Claude to build it > Claude makes three folders: raw for sources, wiki for its pages, a CLAUDE.md that runs it > Drop any source into raw and say "ingest this" > Ask questions across everything, forever Five minutes to set up, and you never start from a blank chat again. Full step-by-step guide with Claude and Obsidian, link below. Bookmark this
0:16

I genuinely don't understand why everyone isn't using this yet Andrej Karpathy, a co-founder of OpenAI, posted a simple idea that hit 16 million views: stop using AI to write code, use it to build a second brain. You point Claude Code at a folder, drop in any source, an article, a transcript, a PDF, and Claude reads it, links it, and files it into a living wiki of everything you know. It compounds like interest, the more you feed it, the smarter it gets. Here's the whole thing: > Install Obsidian, create a vault, open it in Claude Code > Paste Karpathy's wiki idea file and tell Claude to build it > Claude makes three folders: raw for sources, wiki for its pages, a CLAUDE.md that runs it > Drop any source into raw and say "ingest this" > Ask questions across everything, forever Five minutes to set up, and you never start from a blank chat again. Full step-by-step guide with Claude and Obsidian, link below. Bookmark this

Ridark

6,829,704 görüntüleme • 25 gün önce

A guy in Vancouver built an entire operating system inside a Chrome tab. By himself. Over six years. His personal website is the OS. You open and a Windows-style desktop loads. File explorer. Start menu. Taskbar. You can drag in a zip and extract it. You can play DOOM. You can play Quake III Arena. You can boot Linux from an ISO. You can run Stable Diffusion locally for image generation. You can open a Python terminal. You can edit code in Monaco, the same engine that powers VS Code. All of it runs in your browser tab. Nothing installs. His name is Dustin Brett. Self-taught engineer. Father. Husband. 4,473 commits. All his. He had to swap the Windows icon for the π symbol because of legal pressure. The repo has 12,883 stars. MIT license. His hosting bill is one dollar a month. A single Cloudflare CDN does the rest. This is what the open web was built for. (Link in the comments)
0:18

A guy in Vancouver built an entire operating system inside a Chrome tab. By himself. Over six years. His personal website is the OS. You open and a Windows-style desktop loads. File explorer. Start menu. Taskbar. You can drag in a zip and extract it. You can play DOOM. You can play Quake III Arena. You can boot Linux from an ISO. You can run Stable Diffusion locally for image generation. You can open a Python terminal. You can edit code in Monaco, the same engine that powers VS Code. All of it runs in your browser tab. Nothing installs. His name is Dustin Brett. Self-taught engineer. Father. Husband. 4,473 commits. All his. He had to swap the Windows icon for the π symbol because of legal pressure. The repo has 12,883 stars. MIT license. His hosting bill is one dollar a month. A single Cloudflare CDN does the rest. This is what the open web was built for. (Link in the comments)

Nav Toor

71,836 görüntüleme • 26 gün önce

Jeff Bezos just described AI in three words that make most of the economy temporary. Bezos: “AI is real and it is going to change every industry. In fact it’s a very unusual technology in that regard in that it’s a horizontal enabling layer.” Horizontal enabling layer. Not a product. Not a platform. Not a feature. A layer. Underneath everything. Everyone is asking which AI company wins. Bezos is telling you that is the wrong question entirely. A horizontal layer does not produce winners. It produces a new floor. Everything standing on the old one either gets rebuilt or gets erased. This has happened exactly twice in modern history. Electricity. The internet. Both times the same pattern. The new layer appeared. The old economy kept running above it. Revenue held. Careers continued. Everything looked normal. Then quietly and permanently the entire structure reorganized around the new substrate. The people who did not move were not outcompeted. They were made structurally irrelevant. Not because they were wrong. Because the ground they stood on stopped being ground. Bezos is telling you it is happening a third time. Not with a product. Not with a platform. With intelligence itself becoming infrastructure. A horizontal layer does not compete with the expert. It makes expertise free. It hands a 22 year old with zero credentials the same cognitive output you spent a decade and a quarter million dollars learning to produce. For $20 a month. That is not disruption. Disruption replaces a product with a better product. This dissolves the scarcity your entire career was priced on. Not because the work disappeared. Because the wall around it did. Every profession that exists because knowledge is hard to acquire. Every company that profits because analysis takes time. Every industry that survives because complexity locks outsiders out. All of it rests on a single assumption. That cognition is scarce. AI does not challenge that assumption. It retires it. The people who understand this are already rebuilding. Quietly. Deliberately. While everyone else argues about whether the thing underneath them is real. Bezos did not give you a prediction. He gave you a position on a map. You are either above the new layer or beneath it.
0:16

Jeff Bezos just described AI in three words that make most of the economy temporary. Bezos: “AI is real and it is going to change every industry. In fact it’s a very unusual technology in that regard in that it’s a horizontal enabling layer.” Horizontal enabling layer. Not a product. Not a platform. Not a feature. A layer. Underneath everything. Everyone is asking which AI company wins. Bezos is telling you that is the wrong question entirely. A horizontal layer does not produce winners. It produces a new floor. Everything standing on the old one either gets rebuilt or gets erased. This has happened exactly twice in modern history. Electricity. The internet. Both times the same pattern. The new layer appeared. The old economy kept running above it. Revenue held. Careers continued. Everything looked normal. Then quietly and permanently the entire structure reorganized around the new substrate. The people who did not move were not outcompeted. They were made structurally irrelevant. Not because they were wrong. Because the ground they stood on stopped being ground. Bezos is telling you it is happening a third time. Not with a product. Not with a platform. With intelligence itself becoming infrastructure. A horizontal layer does not compete with the expert. It makes expertise free. It hands a 22 year old with zero credentials the same cognitive output you spent a decade and a quarter million dollars learning to produce. For $20 a month. That is not disruption. Disruption replaces a product with a better product. This dissolves the scarcity your entire career was priced on. Not because the work disappeared. Because the wall around it did. Every profession that exists because knowledge is hard to acquire. Every company that profits because analysis takes time. Every industry that survives because complexity locks outsiders out. All of it rests on a single assumption. That cognition is scarce. AI does not challenge that assumption. It retires it. The people who understand this are already rebuilding. Quietly. Deliberately. While everyone else argues about whether the thing underneath them is real. Bezos did not give you a prediction. He gave you a position on a map. You are either above the new layer or beneath it.

Dustin

101,678 görüntüleme • 2 gün önce

🚨 JUST IN: CHINA just released an AI EMPLOYEE that works 24X7 on its own. 100% OPEN SOURCE. It researches, codes, builds websites, creates slide decks, and generates videos. All by itself. All on your computer. It's called DeerFlow. You give it a task. It makes a plan, spins up its own team of sub-agents, and gets to work. You come back and there's a finished deliverable waiting. Not a draft. Not a summary. The actual thing. Not a chatbot. Not a research assistant. An AI with its own computer that works while you sleep. Here's what it does on its own: → Spawns multiple sub-agents in parallel, each tackling a different piece of your task, then combines everything into one finished output → Writes real code, runs it, reads the results, and fixes its own mistakes without asking you once → Builds slide decks, websites, full research reports, and data dashboards from scratch → Remembers you across sessions. Your writing style. Your tech stack. Your preferences. Gets better every time. → Reads files you upload, works with them inside its own filesystem, hands you clean finished outputs → Searches the web, runs commands, calls any tool you plug in Here's how it thinks: You give one instruction. The lead agent makes a plan. Sub-agents fan out and work in parallel. Results come back. Everything gets synthesized. You get a deliverable. A single research task might split into a dozen sub-agents, each exploring a different angle, then converge into one finished website with generated visuals. Here's the wildest part: DeerFlow 2.0 launched on February 28th 2026 and hit number 1 on all of GitHub Trending the same day. Version 2.0 was a complete rewrite. Zero shared code with version 1. Because users kept using it for things the team never intended. Data pipelines. Dashboards. Entire content workflows. The community told them what it needed to become. So they burned it down and rebuilt it. 22.7K GitHub stars. 2.7K forks. Built by ByteDance 100% Open Source. MIT License.
0:17

🚨 JUST IN: CHINA just released an AI EMPLOYEE that works 24X7 on its own. 100% OPEN SOURCE. It researches, codes, builds websites, creates slide decks, and generates videos. All by itself. All on your computer. It's called DeerFlow. You give it a task. It makes a plan, spins up its own team of sub-agents, and gets to work. You come back and there's a finished deliverable waiting. Not a draft. Not a summary. The actual thing. Not a chatbot. Not a research assistant. An AI with its own computer that works while you sleep. Here's what it does on its own: → Spawns multiple sub-agents in parallel, each tackling a different piece of your task, then combines everything into one finished output → Writes real code, runs it, reads the results, and fixes its own mistakes without asking you once → Builds slide decks, websites, full research reports, and data dashboards from scratch → Remembers you across sessions. Your writing style. Your tech stack. Your preferences. Gets better every time. → Reads files you upload, works with them inside its own filesystem, hands you clean finished outputs → Searches the web, runs commands, calls any tool you plug in Here's how it thinks: You give one instruction. The lead agent makes a plan. Sub-agents fan out and work in parallel. Results come back. Everything gets synthesized. You get a deliverable. A single research task might split into a dozen sub-agents, each exploring a different angle, then converge into one finished website with generated visuals. Here's the wildest part: DeerFlow 2.0 launched on February 28th 2026 and hit number 1 on all of GitHub Trending the same day. Version 2.0 was a complete rewrite. Zero shared code with version 1. Because users kept using it for things the team never intended. Data pipelines. Dashboards. Entire content workflows. The community told them what it needed to become. So they burned it down and rebuilt it. 22.7K GitHub stars. 2.7K forks. Built by ByteDance 100% Open Source. MIT License.

Kanika

737,110 görüntüleme • 3 ay önce

THIS GUY GOT SICK OF UK TRAIN STATIONS HIDING THE PLATFORM NUMBER UNTIL THE LAST SECOND, SO HE VIBE CODED AN APP THAT PREDICTS IT BEFORE THEY REVEAL IT if youve ever stood in a crowded station like london euston, you know the pain the platform stays hidden until 15 minutes before boarding, then it flashes up and hundreds of people sprint for the same gate so he built something that fixes this: > a clean departures and arrivals app pulling live data straight from the network rail apis > live train tracking so you can watch where your train actually is on the route and whether its running on time > the main feature is a predictive engine that guesses your platform before the station reveals it, and its right about 75% of the time heres how it predicts: every time a train finishes its journey, it logs which platform it actually pulled into and compares that to the platform network rail originally advertised it saves every one of those comparisons, and over time it builds up enough history to predict the platform with a real confidence score he built the whole thing with claude, mostly opus with some fable
0:18

THIS GUY GOT SICK OF UK TRAIN STATIONS HIDING THE PLATFORM NUMBER UNTIL THE LAST SECOND, SO HE VIBE CODED AN APP THAT PREDICTS IT BEFORE THEY REVEAL IT if youve ever stood in a crowded station like london euston, you know the pain the platform stays hidden until 15 minutes before boarding, then it flashes up and hundreds of people sprint for the same gate so he built something that fixes this: > a clean departures and arrivals app pulling live data straight from the network rail apis > live train tracking so you can watch where your train actually is on the route and whether its running on time > the main feature is a predictive engine that guesses your platform before the station reveals it, and its right about 75% of the time heres how it predicts: every time a train finishes its journey, it logs which platform it actually pulled into and compares that to the platform network rail originally advertised it saves every one of those comparisons, and over time it builds up enough history to predict the platform with a real confidence score he built the whole thing with claude, mostly opus with some fable

Om Patel

175,685 görüntüleme • 11 gün önce

The world just paid $2 trillion for a rocket company that lost $4.9 billion last year. And the rockets are not why it lost the money. They are the only part making any. SpaceX went public Friday, the largest IPO in history. Up 19%, a $2 trillion valuation, Elon Musk the first trillionaire. Then you open the filing. Three businesses sit inside it. Starlink, the satellites, brought in $11.4 billion, 61% of all revenue, and $4.4 billion in profit. It is the only piece that earns a dollar. The rockets that land themselves run a small loss reinvesting in Starship. And the AI arm, Grok plus the app once called Twitter, folded in this February, lost $6.4 billion in a single year on $12.7 billion of spending. Read that again. The satellites pay for everything. The AI loses more than the satellites make. And the AI is the part the market fell in love with. It gets bolder. The prospectus claims a total market of $28.5 trillion, the largest any company has ever put in a filing. Larger than the GDP of the United States. That is the number underwriting a $2 trillion price tag built on a division bleeding $6 billion a year. Now the structure. About 4% of the company trades. That sliver sets the price for all of it. Musk is locked up for 366 days and holds roughly 80% of the votes. The public bought a company they cannot steer, priced on the one segment losing the most. This is the whole year in one ticker. The profit is satellites. The story is AI. The market bought the story. The rockets were never the risk. The risk is a $2 trillion price resting on the one bet that has yet to make a cent.
0:10

The world just paid $2 trillion for a rocket company that lost $4.9 billion last year. And the rockets are not why it lost the money. They are the only part making any. SpaceX went public Friday, the largest IPO in history. Up 19%, a $2 trillion valuation, Elon Musk the first trillionaire. Then you open the filing. Three businesses sit inside it. Starlink, the satellites, brought in $11.4 billion, 61% of all revenue, and $4.4 billion in profit. It is the only piece that earns a dollar. The rockets that land themselves run a small loss reinvesting in Starship. And the AI arm, Grok plus the app once called Twitter, folded in this February, lost $6.4 billion in a single year on $12.7 billion of spending. Read that again. The satellites pay for everything. The AI loses more than the satellites make. And the AI is the part the market fell in love with. It gets bolder. The prospectus claims a total market of $28.5 trillion, the largest any company has ever put in a filing. Larger than the GDP of the United States. That is the number underwriting a $2 trillion price tag built on a division bleeding $6 billion a year. Now the structure. About 4% of the company trades. That sliver sets the price for all of it. Musk is locked up for 366 days and holds roughly 80% of the votes. The public bought a company they cannot steer, priced on the one segment losing the most. This is the whole year in one ticker. The profit is satellites. The story is AI. The market bought the story. The rockets were never the risk. The risk is a $2 trillion price resting on the one bet that has yet to make a cent.

Shanaka Anslem Perera ⚡

721,192 görüntüleme • 1 ay önce

ReLU vs Leaky ReLU 👉 = ReLU = ReLU is the default activation in modern deep learning — cheap to compute, and stable enough to train networks hundreds of layers deep. To see what it does, picture five boba tea shops on the same block — 𝚊, 𝚋, 𝚌, 𝚍, 𝚎 — each running their own books. Each value is a shop's monthly profit — receipts minus rent, ingredients, and wages. When profit is positive, the shop stays open and the owner pockets every dollar. When profit turns negative, the shop runs out of cash and shutters — the lights go off, the books are wiped to zero. ReLU is exactly that rule, applied one shop at a time. Read the diagram left to right. The first column is the raw value x — each shop's profit at month's end. The second column is the gate: 1 if the shop is open (x > 0), 0 if it has shuttered. The last column is the ReLU output: open shops pass their profit through untouched, while shuttered ones are zeroed out. Five rows means five parallel shops on the same block, each evaluated independently. That's why ReLU is called an element-wise activation: every neuron decides its own fate. = LeakyRelu = Plain ReLU wipes negative values to zero — clean, but a shop that shutters can never recover, since both its output and its gradient stay pinned at zero. This is the dying ReLU problem, and in deep networks it can quietly kill a meaningful fraction of the units. Leaky ReLU is the one-line fix: instead of shuttering, the shop files for Chapter 11 protection and keeps the lights on at reduced capacity. Its debt is restructured down to a fraction α (typically 0.1) — the rest is forgiven, and the shop is wounded, not killed. A small negative signal still flows through, so the gradient survives, and the shop can crawl back to life if a TikTok goes viral. Read the diagram left to right. The first column is the raw value x — each shop's profit at month's end. The second column is the leakage α — the fraction of the loss held over after restructuring (default 0.1, editable). The third column is the gate: 1 for shops still in the black, α for those operating under bankruptcy protection. The last column is the Leaky ReLU output: y = x · gate. Profitable shops pass through untouched; struggling ones shrink by a factor of α but still carry a sign. Five rows means five parallel shops, each evaluated independently. Like ReLU, this is an element-wise activation: every neuron's fate is decided on its own merits. #aibyhahd
0:18

ReLU vs Leaky ReLU 👉 = ReLU = ReLU is the default activation in modern deep learning — cheap to compute, and stable enough to train networks hundreds of layers deep. To see what it does, picture five boba tea shops on the same block — 𝚊, 𝚋, 𝚌, 𝚍, 𝚎 — each running their own books. Each value is a shop's monthly profit — receipts minus rent, ingredients, and wages. When profit is positive, the shop stays open and the owner pockets every dollar. When profit turns negative, the shop runs out of cash and shutters — the lights go off, the books are wiped to zero. ReLU is exactly that rule, applied one shop at a time. Read the diagram left to right. The first column is the raw value x — each shop's profit at month's end. The second column is the gate: 1 if the shop is open (x > 0), 0 if it has shuttered. The last column is the ReLU output: open shops pass their profit through untouched, while shuttered ones are zeroed out. Five rows means five parallel shops on the same block, each evaluated independently. That's why ReLU is called an element-wise activation: every neuron decides its own fate. = LeakyRelu = Plain ReLU wipes negative values to zero — clean, but a shop that shutters can never recover, since both its output and its gradient stay pinned at zero. This is the dying ReLU problem, and in deep networks it can quietly kill a meaningful fraction of the units. Leaky ReLU is the one-line fix: instead of shuttering, the shop files for Chapter 11 protection and keeps the lights on at reduced capacity. Its debt is restructured down to a fraction α (typically 0.1) — the rest is forgiven, and the shop is wounded, not killed. A small negative signal still flows through, so the gradient survives, and the shop can crawl back to life if a TikTok goes viral. Read the diagram left to right. The first column is the raw value x — each shop's profit at month's end. The second column is the leakage α — the fraction of the loss held over after restructuring (default 0.1, editable). The third column is the gate: 1 for shops still in the black, α for those operating under bankruptcy protection. The last column is the Leaky ReLU output: y = x · gate. Profitable shops pass through untouched; struggling ones shrink by a factor of α but still carry a sign. Five rows means five parallel shops, each evaluated independently. Like ReLU, this is an element-wise activation: every neuron's fate is decided on its own merits. #aibyhahd

Tom Yeh

32,165 görüntüleme • 2 ay önce

messy inputs 👉🏽 polished outputs built a prototype with the idea of letting users bring together images from Lummi into a canvas, quickly wireframe a concept, and then generate polished images as a photo, illustration, 3d render, whatever—with the right lighting, shadows, cohesive colors, and all that good stuff the output is still not great... but this is where I see the future of creative tools heading—kind of like how you give ChatGPT an idea for an email—all the messy bits—and it writes it for you in any tone or style you want in a clear way. now imagine that but for design or imagery
0:16

messy inputs 👉🏽 polished outputs built a prototype with the idea of letting users bring together images from Lummi into a canvas, quickly wireframe a concept, and then generate polished images as a photo, illustration, 3d render, whatever—with the right lighting, shadows, cohesive colors, and all that good stuff the output is still not great... but this is where I see the future of creative tools heading—kind of like how you give ChatGPT an idea for an email—all the messy bits—and it writes it for you in any tone or style you want in a clear way. now imagine that but for design or imagery

Pablo Stanley

12,109 görüntüleme • 1 yıl önce

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:
0:16

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

18,374 görüntüleme • 2 ay önce

Every agent. Every user. Every contribution. That’s how the Sentient GRID grows not by scale from a single model, but by compounding intelligence across an open network. The GRID isn’t a product. It’s an ecosystem of intelligence. Each new integration adds new capabilities reasoning, retrieval, data, and alignment making the whole network smarter. Closed labs build vertically (one model trying to do everything). Sentient builds horizontally thousands of agents learning, sharing, and evolving together. Today there are 100+ active partners building on the GRID from AI researchers to tool developers all feeding value back into a shared intelligence layer. It’s a living system that improves itself, powered by collaboration instead of control. The more people build on it, the more capable it becomes. Just like Linux became the invisible layer running the internet, the GRID is becoming the invisible layer powering intelligence. Open-source always wins. And the GRID is where that victory starts All apps built on the Grid will be accessible to $SENT holders. The full open release of Sentient Chat is coming soon (confirmed from the yesterday community call) gsenti
0:11

Every agent. Every user. Every contribution. That’s how the Sentient GRID grows not by scale from a single model, but by compounding intelligence across an open network. The GRID isn’t a product. It’s an ecosystem of intelligence. Each new integration adds new capabilities reasoning, retrieval, data, and alignment making the whole network smarter. Closed labs build vertically (one model trying to do everything). Sentient builds horizontally thousands of agents learning, sharing, and evolving together. Today there are 100+ active partners building on the GRID from AI researchers to tool developers all feeding value back into a shared intelligence layer. It’s a living system that improves itself, powered by collaboration instead of control. The more people build on it, the more capable it becomes. Just like Linux became the invisible layer running the internet, the GRID is becoming the invisible layer powering intelligence. Open-source always wins. And the GRID is where that victory starts All apps built on the Grid will be accessible to $SENT holders. The full open release of Sentient Chat is coming soon (confirmed from the yesterday community call) gsenti

OHJAY ⭕️ || 🇬🇧

16,178 görüntüleme • 9 ay önce