Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

A DEVELOPER FOUND SEVEN WAYS TO TAKE DOWN A PRODUCTION DATABASE THAT ALL LOOK EXACTLY LIKE NORMAL, INNOCENT CODE AND ALMOST EVERY TEAM IS SHIPPING AT LEAST ONE OF THEM RIGHT NOW 17 minutes from Josh Berkus, one of the people who actually maintains PostgreSQL, walking through the quiet... mistakes that turn a healthy database into a 3am outage. -> The moment it lands, you realize none of these are exotic attacks. They're ordinary-looking decisions -- a query that locks a table, a connection that never closes, a setting no one ever questioned -- that work perfectly until the day they don't, and then they take everything down with them. The scary part isn't that the database breaks. It's how normal the code looks right up until it does. A query that runs in 5ms on your laptop and 5 minutes on prod. A migration that silently locks the whole table. A connection pool that runs dry the moment real traffic shows up. Every one of them passed review. Writing SQL that runs was never the hard part -> writing SQL that survives production is. And now that an AI agent is generating and firing queries at your real database faster than anyone can read them, every one of those seven landmines is one autocomplete away -- and the only person who can stop it is the one who already knows where they're buried. Your database doesn't go down because someone attacked it. It goes down because something that looked completely normal finally caught up with it. Save and Watch it today. You'll see the next outage coming before it lands ↓show more

slash1s

9,057 subscribers

22,268 görüntüleme • 29 gün önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

A DEVELOPER PROVED THE REGEX YOU'VE WRITTEN A THOUSAND TIMES IS SECRETLY A COMPILER AND THAT ALMOST NO ONE WHO USES THEM HAS ANY IDEA WHAT ACTUALLY RUNS 36 minutes from Paul Wankadia, the engineer behind a regex engine that compiles your pattern straight down to raw machine code -- walking through what really happens between the slashes. -> The moment it clicks, regex stops being magic punctuation you paste from Stack Overflow and becomes what it actually is: a tiny machine. Your pattern gets turned into a state machine, and that machine is what runs against every character of your text. That one idea explains everything you never understood. Why one regex returns instantly and a nearly identical one hangs your whole server. Why some patterns are safe and others are a denial-of-service waiting to happen. It was never random -- it's whether the machine underneath is built well or badly. Writing a regex was never the skill -> reading one is. And now that an AI agent hands you dense, clever patterns you'd never write yourself, the person who can see the machine underneath is the one who catches the one that takes down production at 3am. Everyone copies regex and prays. This is the talk that ends the praying. Save it. The next time a pattern "Just works," you'll actually know why ↓

A DEVELOPER PROVED THE REGEX YOU'VE WRITTEN A THOUSAND TIMES IS SECRETLY A COMPILER AND THAT ALMOST NO ONE WHO USES THEM HAS ANY IDEA WHAT ACTUALLY RUNS 36 minutes from Paul Wankadia, the engineer behind a regex engine that compiles your pattern straight down to raw machine code -- walking through what really happens between the slashes. -> The moment it clicks, regex stops being magic punctuation you paste from Stack Overflow and becomes what it actually is: a tiny machine. Your pattern gets turned into a state machine, and that machine is what runs against every character of your text. That one idea explains everything you never understood. Why one regex returns instantly and a nearly identical one hangs your whole server. Why some patterns are safe and others are a denial-of-service waiting to happen. It was never random -- it's whether the machine underneath is built well or badly. Writing a regex was never the skill -> reading one is. And now that an AI agent hands you dense, clever patterns you'd never write yourself, the person who can see the machine underneath is the one who catches the one that takes down production at 3am. Everyone copies regex and prays. This is the talk that ends the praying. Save it. The next time a pattern "Just works," you'll actually know why ↓

slash1s

191,595 görüntüleme • 1 ay önce

A DEVELOPER MADE A REAL COMMIT WITHOUT EVER TYPING GIT ADD OR GIT COMMIT -- JUST TO PROVE THE COMMANDS YOU LIVE BY ARE A THIN SHELL OVER A DATABASE YOU'VE NEVER ONCE OPENED 55 minutes from Tim Berglund, a longtime Git teacher and GitHub evangelist, taking the tool apart down to the raw objects almost nobody who uses it every day has ever touched. -> The moment it clicks, Git stops being a pile of memorized commands and becomes what it actually is underneath: a tiny content-addressed database of blobs, trees and commits. git add and git commit are just polite wrappers around writing objects into it by hand. Every commit you've ever made was Git hashing a snapshot and filing it by fingerprint. Branches are just labels pointing at one of those objects. The work you thought you destroyed with a bad reset is still sitting in the reflog. Once you can see that graph, the commands that used to terrify you stop being scary at all. Memorizing commands was never the skill -> reading the object graph in your head is. And with an AI agent now committing and rebasing on your machine faster than you can follow, the one person who can untangle the mess it leaves is the one who knows what's really stored down there. There's a person on every team everyone runs to when Git breaks. This is the talk that quietly turns you into them. You'll reach for it the next time a rebase goes sideways. Bookmark & Watch it today ↓

A DEVELOPER MADE A REAL COMMIT WITHOUT EVER TYPING GIT ADD OR GIT COMMIT -- JUST TO PROVE THE COMMANDS YOU LIVE BY ARE A THIN SHELL OVER A DATABASE YOU'VE NEVER ONCE OPENED 55 minutes from Tim Berglund, a longtime Git teacher and GitHub evangelist, taking the tool apart down to the raw objects almost nobody who uses it every day has ever touched. -> The moment it clicks, Git stops being a pile of memorized commands and becomes what it actually is underneath: a tiny content-addressed database of blobs, trees and commits. git add and git commit are just polite wrappers around writing objects into it by hand. Every commit you've ever made was Git hashing a snapshot and filing it by fingerprint. Branches are just labels pointing at one of those objects. The work you thought you destroyed with a bad reset is still sitting in the reflog. Once you can see that graph, the commands that used to terrify you stop being scary at all. Memorizing commands was never the skill -> reading the object graph in your head is. And with an AI agent now committing and rebasing on your machine faster than you can follow, the one person who can untangle the mess it leaves is the one who knows what's really stored down there. There's a person on every team everyone runs to when Git breaks. This is the talk that quietly turns you into them. You'll reach for it the next time a rebase goes sideways. Bookmark & Watch it today ↓

slash1s

236,545 görüntüleme • 1 ay önce

A DEVELOPER PROVED THAT MOST OF THE LANGUAGE RUNNING EVERY WEBSITE YOU USE IS A MINEFIELD AND THAT ALMOST NO ONE WAS EVER TAUGHT WHICH PARTS ARE SAFE An hour from Douglas Crockford, the man who invented JSON, on the good parts of JavaScript buried under a pile of blunders nobody warned you about. -> The moment it lands, every weird bug makes sense. The language never had time to be polished. It went global in months, bad parts and all, and you inherited every one of them. Global variables. Silent semicolon insertion. eval. Coercion that turns a simple comparison into a coin flip. Most people never learned to avoid them -- they just lose hours and blame themselves. Writing JavaScript that runs was never the skill -> knowing which half of it to never touch is. And when an AI agent happily generates the bad parts at scale, the person who knows the safe subset is the one who catches it before it ships. Everyone writes JavaScript. Almost no one was shown the line between the parts that save you and the parts that quietly burn you. Bookmark and Watch it ↓

A DEVELOPER PROVED THAT MOST OF THE LANGUAGE RUNNING EVERY WEBSITE YOU USE IS A MINEFIELD AND THAT ALMOST NO ONE WAS EVER TAUGHT WHICH PARTS ARE SAFE An hour from Douglas Crockford, the man who invented JSON, on the good parts of JavaScript buried under a pile of blunders nobody warned you about. -> The moment it lands, every weird bug makes sense. The language never had time to be polished. It went global in months, bad parts and all, and you inherited every one of them. Global variables. Silent semicolon insertion. eval. Coercion that turns a simple comparison into a coin flip. Most people never learned to avoid them -- they just lose hours and blame themselves. Writing JavaScript that runs was never the skill -> knowing which half of it to never touch is. And when an AI agent happily generates the bad parts at scale, the person who knows the safe subset is the one who catches it before it ships. Everyone writes JavaScript. Almost no one was shown the line between the parts that save you and the parts that quietly burn you. Bookmark and Watch it ↓

slash1s

13,073 görüntüleme • 22 gün önce

ChatGPT can write you a thousand trading strategies from one sentence. 999 will quietly bleed your account dry. Every single one of them looks like a winner. One method pulls the real one out. Quant desks have run it for years. It's called loop engineering. It's not a smarter prompt. It's a loop: generate a strategy, test it, score why it failed, feed that back, and run it again until one survives data it has never seen. Man Group runs $150 billion. They built an AI that writes and tests hundreds of strategies a week. And second agent whose only job is to hunt the ones that secretly overfit and kill them before a cent goes live. > describe an idea -> backtest 5 years in 12 seconds > read why it died -> feed that back in > run it again until one survives data it never saw AI can write a thousand strategies. Loop engineering is the only thing that tells you which one was ever real. 89% of retail lost money in 2025. Almost none of it from bad ideas. All of it from trading the first guess and never running it through backtest loop. Horizon just put the whole thing in a chat box, free while the beta's open: You're not losing to smarter traders. You're losing to the ones who opened the tab. Anyone can generate a strategy now. Almost no one runs the loop that proves it. That gap is the whole edge. You'll mean to check it later. Later is a "waitlist closed" page.

ChatGPT can write you a thousand trading strategies from one sentence. 999 will quietly bleed your account dry. Every single one of them looks like a winner. One method pulls the real one out. Quant desks have run it for years. It's called loop engineering. It's not a smarter prompt. It's a loop: generate a strategy, test it, score why it failed, feed that back, and run it again until one survives data it has never seen. Man Group runs $150 billion. They built an AI that writes and tests hundreds of strategies a week. And second agent whose only job is to hunt the ones that secretly overfit and kill them before a cent goes live. > describe an idea -> backtest 5 years in 12 seconds > read why it died -> feed that back in > run it again until one survives data it never saw AI can write a thousand strategies. Loop engineering is the only thing that tells you which one was ever real. 89% of retail lost money in 2025. Almost none of it from bad ideas. All of it from trading the first guess and never running it through backtest loop. Horizon just put the whole thing in a chat box, free while the beta's open: You're not losing to smarter traders. You're losing to the ones who opened the tab. Anyone can generate a strategy now. Almost no one runs the loop that proves it. That gap is the whole edge. You'll mean to check it later. Later is a "waitlist closed" page.

cvxv666

165,663 görüntüleme • 17 gün önce

A DEVELOPER PROVED THAT MOST OF THE CLASSES YOU WRITE SHOULD NEVER HAVE BEEN CLASSES AT ALL 27 minutes from Jack Diederich, a Python core developer, on how much of your code is just a function wearing a costume. -> The moment it lands, the rule is brutal: if a class has two methods and one is __init__, you meant to write a function. Most people add structure to feel like real engineers. It just adds weight no one ever needed. Writing more code was never the skill -> writing less of it is. And when an AI agent happily generates ten classes for a job that needed three lines, the person who knows what to delete is the one who ships something clean. Anyone can add abstraction. Knowing when not to is the whole job. Bookmark it and Watch ↓

A DEVELOPER PROVED THAT MOST OF THE CLASSES YOU WRITE SHOULD NEVER HAVE BEEN CLASSES AT ALL 27 minutes from Jack Diederich, a Python core developer, on how much of your code is just a function wearing a costume. -> The moment it lands, the rule is brutal: if a class has two methods and one is init, you meant to write a function. Most people add structure to feel like real engineers. It just adds weight no one ever needed. Writing more code was never the skill -> writing less of it is. And when an AI agent happily generates ten classes for a job that needed three lines, the person who knows what to delete is the one who ships something clean. Anyone can add abstraction. Knowing when not to is the whole job. Bookmark it and Watch ↓

slash1s

266,884 görüntüleme • 19 gün önce

A LINUX KERNEL DEVELOPER PROVED THE THING YOU PUSH CODE TO IS SECRETLY A DATABASE THAT CAN VERSION ALMOST ANYTHING AND THAT MOST DEVS HAVE ONLY EVER TOUCHED A TENTH OF IT 42 minutes from Josh Triplett -- a longtime Linux kernel and Debian developer -- showing that Git is a general-purpose, tamper-evident versioning engine that just happens to be famous for code. -> The moment it clicks, Git stops being "Where my code lives" and becomes what it really is underneath: a content-addressable store that can version almost anything -- your configs, your notes, your servers' state, entire datasets. People run whole wikis on it. They version their entire machine's configuration with it. They ship websites by pushing to it. They track data too big to email. None of it is a hack -- it's the same handful of objects you already use for code, pointed somewhere new. Treating Git as a code-only tool was never the ceiling -> it's a versioning engine for anything, and the people who see that automate what the rest of the team still does by hand. And as AI agents start spitting out not just code but configs, docs and data, the one system that can version and audit all of it at once is already sitting on your machine. You learned five commands to survive. This is the talk that shows you were standing on top of a database the whole time. It changes what you think the tool is even for. Bookmark & Watch it today ↓

A LINUX KERNEL DEVELOPER PROVED THE THING YOU PUSH CODE TO IS SECRETLY A DATABASE THAT CAN VERSION ALMOST ANYTHING AND THAT MOST DEVS HAVE ONLY EVER TOUCHED A TENTH OF IT 42 minutes from Josh Triplett -- a longtime Linux kernel and Debian developer -- showing that Git is a general-purpose, tamper-evident versioning engine that just happens to be famous for code. -> The moment it clicks, Git stops being "Where my code lives" and becomes what it really is underneath: a content-addressable store that can version almost anything -- your configs, your notes, your servers' state, entire datasets. People run whole wikis on it. They version their entire machine's configuration with it. They ship websites by pushing to it. They track data too big to email. None of it is a hack -- it's the same handful of objects you already use for code, pointed somewhere new. Treating Git as a code-only tool was never the ceiling -> it's a versioning engine for anything, and the people who see that automate what the rest of the team still does by hand. And as AI agents start spitting out not just code but configs, docs and data, the one system that can version and audit all of it at once is already sitting on your machine. You learned five commands to survive. This is the talk that shows you were standing on top of a database the whole time. It changes what you think the tool is even for. Bookmark & Watch it today ↓

slash1s

382,693 görüntüleme • 1 ay önce

A DEVELOPER WHO HELPS MAINTAIN GIT ITSELF PROVED THAT USING GIT AND CONTRIBUTING WITH GIT ARE TWO DIFFERENT SKILLS AND ALMOST NO ONE LEARNS THE SECOND 55 minutes from Johannes Schindelin, one of git's most prolific contributors, on the workflow that gets your code accepted into a project you don't own. -> The moment it lands, committing to your own repo turns out to be the easy 10%. Landing a change in someone else's codebase is the part nobody taught you. Most people can save their own work. Far fewer can revise a patch five times, keep the history clean, and merge it into a project moving under them. Saving your code was never the skill -> getting it merged into someone else's is. And when an AI agent fires off a pull request nobody asked for, the person who knows how to really contribute is the one who gets it accepted instead of closed. Anyone can commit to their own repo. The person who can land a change in a project they don't own is the one who actually ships. Bookmark & Watch it today ↓

A DEVELOPER WHO HELPS MAINTAIN GIT ITSELF PROVED THAT USING GIT AND CONTRIBUTING WITH GIT ARE TWO DIFFERENT SKILLS AND ALMOST NO ONE LEARNS THE SECOND 55 minutes from Johannes Schindelin, one of git's most prolific contributors, on the workflow that gets your code accepted into a project you don't own. -> The moment it lands, committing to your own repo turns out to be the easy 10%. Landing a change in someone else's codebase is the part nobody taught you. Most people can save their own work. Far fewer can revise a patch five times, keep the history clean, and merge it into a project moving under them. Saving your code was never the skill -> getting it merged into someone else's is. And when an AI agent fires off a pull request nobody asked for, the person who knows how to really contribute is the one who gets it accepted instead of closed. Anyone can commit to their own repo. The person who can land a change in a project they don't own is the one who actually ships. Bookmark & Watch it today ↓

slash1s

12,624 görüntüleme • 23 gün önce

A WRITER WENT ON STAGE AND CALLED IT YEARS EARLY: THE MACHINE ON YOUR DESK WOULD SLOWLY STOP BEING YOURS AND ALMOST NO ONE WOULD NOTICE THE MOMENT IT FLIPPED 54 minutes from Cory Doctorow, arguing the copyright fights were just the warm-up -- that the real battle is whether general-purpose machines, the kind that run whatever you tell them, are even allowed to keep existing. -> The moment it lands, you see the move. Nobody takes your computer away. They sell you one that looks like yours but answers to them -- locked down, logging, checking with a server you'll never see before it obeys you. For years that was DRM and locked phones. Now it's intelligence itself. Rent your AI from the cloud and the most powerful tool on your desk was never yours: it reads your prompts, sets your limits, keeps your data, and can cut you off tomorrow. You don't own the computation. You're licensed to borrow it. Using the smartest model was never the whole game -> owning the machine that runs it is. And the post below is what winning that war looks like now: one box, private AI running on it, every byte of client data kept off the cloud, and the line item that drains everyone else's account quietly turned into income. A rented computer obeys whoever signs the check. The one you own obeys you. In the AI era, that's the entire difference. The full breakdown below. Bookmark & Watch it today ↓

A WRITER WENT ON STAGE AND CALLED IT YEARS EARLY: THE MACHINE ON YOUR DESK WOULD SLOWLY STOP BEING YOURS AND ALMOST NO ONE WOULD NOTICE THE MOMENT IT FLIPPED 54 minutes from Cory Doctorow, arguing the copyright fights were just the warm-up -- that the real battle is whether general-purpose machines, the kind that run whatever you tell them, are even allowed to keep existing. -> The moment it lands, you see the move. Nobody takes your computer away. They sell you one that looks like yours but answers to them -- locked down, logging, checking with a server you'll never see before it obeys you. For years that was DRM and locked phones. Now it's intelligence itself. Rent your AI from the cloud and the most powerful tool on your desk was never yours: it reads your prompts, sets your limits, keeps your data, and can cut you off tomorrow. You don't own the computation. You're licensed to borrow it. Using the smartest model was never the whole game -> owning the machine that runs it is. And the post below is what winning that war looks like now: one box, private AI running on it, every byte of client data kept off the cloud, and the line item that drains everyone else's account quietly turned into income. A rented computer obeys whoever signs the check. The one you own obeys you. In the AI era, that's the entire difference. The full breakdown below. Bookmark & Watch it today ↓

slash1s

239,651 görüntüleme • 29 gün önce

You can now access AI directly from your database! Here is a step-by-step demo that uses GPT-4 to classify customer reviews from a MySQL dataset. And I'm only writing SQL instructions! You have to see it! The model acts as another table in the database. I can query it and join it with other tables. It's awesome! This is all thanks to mindshub. Here is their GitHub repository: They are sponsoring this post. Watch the video.

You can now access AI directly from your database! Here is a step-by-step demo that uses GPT-4 to classify customer reviews from a MySQL dataset. And I'm only writing SQL instructions! You have to see it! The model acts as another table in the database. I can query it and join it with other tables. It's awesome! This is all thanks to mindshub. Here is their GitHub repository: They are sponsoring this post. Watch the video.

Santiago

209,434 görüntüleme • 2 yıl önce

A PHYSICS PROFESSOR GAVE THE SAME LECTURE 1,742 TIMES TO WARN ABOUT ONE IDEA QUIETLY BREAKING THE HUMAN RACE. IT IS THE WORD EVERY AI LAB THROWS AROUND TODAY AND ALMOST NONE OF THEM ACTUALLY UNDERSTAND IT. 72 minutes from Albert Bartlett, a University of Colorado physicist, on the one piece of math he called humanity's greatest blind spot. -> The idea that lands: a small steady percentage is never small. 7% a year sounds calm, but it doubles in a decade, doubles again in the next, and quietly runs away from you. He shows it with bacteria in a bottle, with money, with whole cities -- the same curve that looks flat for ages and then explodes almost overnight. Everyone calls that curve "Exponential". He proves most people hear it as "Fast" when it actually means something far more violent. Right now every lab and every headline calls AI exponential. This is the talk that shows you what the word truly does -- so you see both the hype and the real danger the way the math demands. You thought it was a boring math word. It was the whole story the entire time. Save this one. You'll never hear "Exponential" the same way ↓

A PHYSICS PROFESSOR GAVE THE SAME LECTURE 1,742 TIMES TO WARN ABOUT ONE IDEA QUIETLY BREAKING THE HUMAN RACE. IT IS THE WORD EVERY AI LAB THROWS AROUND TODAY AND ALMOST NONE OF THEM ACTUALLY UNDERSTAND IT. 72 minutes from Albert Bartlett, a University of Colorado physicist, on the one piece of math he called humanity's greatest blind spot. -> The idea that lands: a small steady percentage is never small. 7% a year sounds calm, but it doubles in a decade, doubles again in the next, and quietly runs away from you. He shows it with bacteria in a bottle, with money, with whole cities -- the same curve that looks flat for ages and then explodes almost overnight. Everyone calls that curve "Exponential". He proves most people hear it as "Fast" when it actually means something far more violent. Right now every lab and every headline calls AI exponential. This is the talk that shows you what the word truly does -- so you see both the hype and the real danger the way the math demands. You thought it was a boring math word. It was the whole story the entire time. Save this one. You'll never hear "Exponential" the same way ↓

slash1s

98,484 görüntüleme • 7 gün önce

Your trading strategy didn't break. The market it was built for quietly stopped existing. Read that twice. It's most of why 89% of retail finished 2025 in the red. There's now an app that does the entire job of a $400,000 quant. You type a trading idea in plain English. It writes the code, backtests 5 years in 12 seconds, runs thousands of simulations, and tells you cold whether your edge is dead or the regime just changed. No code. No Python. No $25,000 terminal. 20,000 already inside. Waitlist stops at 25,000: That distinction is the whole game, and you never had a way to see it. Every strategy is a bet that one thing stays true. Momentum bets trends continue. Mean reversion bets ranges hold. When the regime flips, the assumption dies and your strategy bleeds with nothing wrong in the code. You stare at the logic for a month and never find the bug, because there isn't one. So you delete it, or refit it to the last drawdown and build something that would have survived the pain you already felt and nothing coming next. The desks never had that problem. 92% of institutional volume is automated. Only 45% of retail is. They test 100 strategies for every 1 you test by hand, and kill 97 of them on purpose, because they can tell a dead edge from a normal drawdown. Now that exact loop costs $0. One hypothesis used to cost a fund $87,500 to test. With Horizon you get unlimited, in seconds, and a winner deploys live in 90 seconds and runs without your hands on it.

Your trading strategy didn't break. The market it was built for quietly stopped existing. Read that twice. It's most of why 89% of retail finished 2025 in the red. There's now an app that does the entire job of a $400,000 quant. You type a trading idea in plain English. It writes the code, backtests 5 years in 12 seconds, runs thousands of simulations, and tells you cold whether your edge is dead or the regime just changed. No code. No Python. No $25,000 terminal. 20,000 already inside. Waitlist stops at 25,000: That distinction is the whole game, and you never had a way to see it. Every strategy is a bet that one thing stays true. Momentum bets trends continue. Mean reversion bets ranges hold. When the regime flips, the assumption dies and your strategy bleeds with nothing wrong in the code. You stare at the logic for a month and never find the bug, because there isn't one. So you delete it, or refit it to the last drawdown and build something that would have survived the pain you already felt and nothing coming next. The desks never had that problem. 92% of institutional volume is automated. Only 45% of retail is. They test 100 strategies for every 1 you test by hand, and kill 97 of them on purpose, because they can tell a dead edge from a normal drawdown. Now that exact loop costs $0. One hypothesis used to cost a fund $87,500 to test. With Horizon you get unlimited, in seconds, and a winner deploys live in 90 seconds and runs without your hands on it.

cvxv666

39,933 görüntüleme • 22 gün önce

Notion's Head of Product Max Schoening : "I actually don't care at all whether designers write code that lands in production. The reason I like designers thinking in code is that it forces you to consider the medium. I would much rather take a designer or PM who has a deep affinity for understanding how agent loops work than someone who can ship PRs. And the only way that you can actually get to understanding agent loops is by building them in the material that they're made of, which is currently code. That's why I care that designers 'code.' Not because of the utility of shipping to production, but because it forces you to really interrogate the material that you're designing with."

Notion's Head of Product Max Schoening : "I actually don't care at all whether designers write code that lands in production. The reason I like designers thinking in code is that it forces you to consider the medium. I would much rather take a designer or PM who has a deep affinity for understanding how agent loops work than someone who can ship PRs. And the only way that you can actually get to understanding agent loops is by building them in the material that they're made of, which is currently code. That's why I care that designers 'code.' Not because of the utility of shipping to production, but because it forces you to really interrogate the material that you're designing with."

Lenny Rachitsky

76,242 görüntüleme • 2 ay önce

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

118,124 görüntüleme • 1 ay önce

When you pull up the tuition for a D3 school, the number hits you like a wall. You show your parents. They shake their heads. Someone closes the laptop. And just like that, a school that could have been the perfect fit gets crossed off a list it never even made it onto. That happens every single recruiting cycle. What most families never get to is the part where the sticker price is not the real price. Where financial aid, merit scholarships, and one of the highest discount rates in the country bring that number down to something that actually makes sense. There are athletes on D3 rosters right now from public schools, from towns that are not affluent, from families who almost did not apply because of that first number they saw online. They kept digging. And it changed everything. Every school in the country is also required by law to have a net price calculator on their website. Plug in your GPA and your family's information and you will get a real ballpark number, not the scary one on the homepage. Brant McAdams is the head football coach at Pacific Lutheran Football and this week on the podcast he breaks down recruiting from a head coach's perspective and what families get wrong about D3. Want the full episode? Comment PODCAST and I will send it over.

When you pull up the tuition for a D3 school, the number hits you like a wall. You show your parents. They shake their heads. Someone closes the laptop. And just like that, a school that could have been the perfect fit gets crossed off a list it never even made it onto. That happens every single recruiting cycle. What most families never get to is the part where the sticker price is not the real price. Where financial aid, merit scholarships, and one of the highest discount rates in the country bring that number down to something that actually makes sense. There are athletes on D3 rosters right now from public schools, from towns that are not affluent, from families who almost did not apply because of that first number they saw online. They kept digging. And it changed everything. Every school in the country is also required by law to have a net price calculator on their website. Plug in your GPA and your family's information and you will get a real ballpark number, not the scary one on the homepage. Brant McAdams is the head football coach at Pacific Lutheran Football and this week on the podcast he breaks down recruiting from a head coach's perspective and what families get wrong about D3. Want the full episode? Comment PODCAST and I will send it over.

Nick Lemke, RD | Sports Nutrition for Athletes

40,153 görüntüleme • 1 ay önce

How do you explain Crypto simply? Matt Hougan keeps it easy: Think about PayPal. It works instantly because it’s one database PayPal controls. If you send $100, they just update a line in that database. Banks are slower because they have to coordinate multiple databases. The blockchain is the first time in history we’ve had one global database that updates in real time - and no company controls it. That means you can move money worldwide instantly and own digital property without trusting a bank, a tech giant, or a billionaire. Matt calls it one of the most significant financial breakthroughs of the last 200 years. Bitwise

How do you explain Crypto simply? Matt Hougan keeps it easy: Think about PayPal. It works instantly because it’s one database PayPal controls. If you send $100, they just update a line in that database. Banks are slower because they have to coordinate multiple databases. The blockchain is the first time in history we’ve had one global database that updates in real time - and no company controls it. That means you can move money worldwide instantly and own digital property without trusting a bank, a tech giant, or a billionaire. Matt calls it one of the most significant financial breakthroughs of the last 200 years. Bitwise

MR SHIFT 🦁

17,389 görüntüleme • 10 ay önce

Notch Clips. every other ad tool ignores the footage sitting in your dropbox and generates new clips from a prompt. notch opens your library instead. it watches every clip you have ever shot and understands what is inside each one. the mood. who is in frame. what they are doing. the quality. so when you ask it to build an ad, it does not start from scratch. it reaches into your past shoots, finds the clip that fits, and slots it into the exact moment that needs it. here is what that looks like. you had thirteen versions of one reaction shot. notch picked the one that worked and left the other twelve. not by filename. not by guessing from a reference image. it watched all thirteen and could tell the difference. that is the whole idea. the right clip was already in your library. every other tool was about to make a worse one. footage you already shot, turned into every ad you still need. drop your site and a few clips you have. notch builds the first ad from them.

Notch Clips. every other ad tool ignores the footage sitting in your dropbox and generates new clips from a prompt. notch opens your library instead. it watches every clip you have ever shot and understands what is inside each one. the mood. who is in frame. what they are doing. the quality. so when you ask it to build an ad, it does not start from scratch. it reaches into your past shoots, finds the clip that fits, and slots it into the exact moment that needs it. here is what that looks like. you had thirteen versions of one reaction shot. notch picked the one that worked and left the other twelve. not by filename. not by guessing from a reference image. it watched all thirteen and could tell the difference. that is the whole idea. the right clip was already in your library. every other tool was about to make a worse one. footage you already shot, turned into every ad you still need. drop your site and a few clips you have. notch builds the first ad from them.

Vinay Jain

406,286 görüntüleme • 1 ay önce

Your faith was forged in people who would rather be exterminated than assimilated. A soft version of it, eager to be liked and desperate to fit in, is not the thing they died to hand you. So stop striving to be liked. Stop angling to be loved by a world that drove your fathers into the snow. That world would think no better of the gospel today than it did in 1838. Stop trying to file down every peculiar and glorious edge of the Restoration until the world finally finds you acceptable. It never will. And the wanting of its approval is the slow death of everything your people bled to preserve. I am thinking of the proclamation on the family, and of how many have quietly gone looking for a way around it. Some say it aloud now. Some march under the world's Pride banners and tell themselves it is only love. They have done the quiet arithmetic and concluded that if they give the world this one doctrine, the world will finally stop hating them, finally let them belong, finally call them good. It does not work that way. It has never once worked that way. Understand what the world actually hates, because it is not a single teaching about marriage that it cannot abide. It is the claim. It is the unbearable, scandalous claim that the keys of the priesthood were restored to the earth, that there is a prophet who speaks for God, that this and no other is the authorized house of the Lord. That is the offense. That is what it cannot forgive. You could surrender every doctrine the world finds distasteful, one after another, and you would not buy a single hour of peace, because the thing it objects to is not your position on this or that. It is that you claim to hold the authority of heaven, and it intends to see that claim humbled. The doctrine is only the doorway it is pushing on. The house is what it wants. Embrace the truth. Embrace the battle that has always come with it, because there has always been a battle, and there is one now. It is the oldest war there is, good against evil, light against the dark, and you were born onto its field whether you wished to be or not. You did not inherit a museum. You inherited a war, and a banner, and a people who never once surrendered it. You are a Mormon. The blood of the persecuted is in you, and the truth they died for is in your hands. You are not tourists. You are not spectators. You are the heirs of warriors, and the line they held is now yours to hold. So plant your feet on the ground they bled for. Lift the banner they would not drop.

Your faith was forged in people who would rather be exterminated than assimilated. A soft version of it, eager to be liked and desperate to fit in, is not the thing they died to hand you. So stop striving to be liked. Stop angling to be loved by a world that drove your fathers into the snow. That world would think no better of the gospel today than it did in 1838. Stop trying to file down every peculiar and glorious edge of the Restoration until the world finally finds you acceptable. It never will. And the wanting of its approval is the slow death of everything your people bled to preserve. I am thinking of the proclamation on the family, and of how many have quietly gone looking for a way around it. Some say it aloud now. Some march under the world's Pride banners and tell themselves it is only love. They have done the quiet arithmetic and concluded that if they give the world this one doctrine, the world will finally stop hating them, finally let them belong, finally call them good. It does not work that way. It has never once worked that way. Understand what the world actually hates, because it is not a single teaching about marriage that it cannot abide. It is the claim. It is the unbearable, scandalous claim that the keys of the priesthood were restored to the earth, that there is a prophet who speaks for God, that this and no other is the authorized house of the Lord. That is the offense. That is what it cannot forgive. You could surrender every doctrine the world finds distasteful, one after another, and you would not buy a single hour of peace, because the thing it objects to is not your position on this or that. It is that you claim to hold the authority of heaven, and it intends to see that claim humbled. The doctrine is only the doorway it is pushing on. The house is what it wants. Embrace the truth. Embrace the battle that has always come with it, because there has always been a battle, and there is one now. It is the oldest war there is, good against evil, light against the dark, and you were born onto its field whether you wished to be or not. You did not inherit a museum. You inherited a war, and a banner, and a people who never once surrendered it. You are a Mormon. The blood of the persecuted is in you, and the truth they died for is in your hands. You are not tourists. You are not spectators. You are the heirs of warriors, and the line they held is now yours to hold. So plant your feet on the ground they bled for. Lift the banner they would not drop.

Kirk Rollins

30,483 görüntüleme • 18 gün önce

Hermes agent just left the terminal. 𝗛𝗲𝗿𝗺𝗲𝘀 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 dropped yesterday. native app for macOS, Windows, and Linux. for months Hermes was the agent that learned your projects, wrote its own skills, and built a model of who you are. all of it buried in terminal logs. now it has a window. the important part is that it's not a wrapper. it runs the same agent core, the same sessions, memory, and skills as the CLI. you can start a task in the terminal and finish it in the app without anything resetting. the state is shared across every interface, not copied between them. what the GUI actually adds: → streaming chat that shows live tool calls and inline reasoning instead of a spinner → a preview rail that renders pages, code, and images right beside the conversation → an artifacts panel that collects every file the agent has ever produced → remote gateway mode, so you can point the app at a VPS and run the heavy work elsewhere → skills, cron, profiles, and gateways managed point-and-click instead of through YAML → voice mode, drag-drop files, and inline image generation remote gateway mode is the one worth slowing down on. the agent runs 24/7 on a $5 server while you control it from your laptop like a local app. other agent UIs are chatboxes with a logo. this one shows the autonomy instead of hiding it, so you watch the skills load, the tools fire, and the artifacts pile up as it works. it was teased in Jensen's GTC keynote. MIT licensed, local-first, no telemetry. if you already run Hermes, download it and everything is already there. your chats, memory, and skills carry straight over. i wrote a full masterclass on Hermes Agent that walks through the SOUL. md identity layer, the three-tier memory system, the self-evolving skills loop, and how to run three specialized agents 24/7. desktop is the interface that finally does all of it justice. the article is quoted below.

Akshay 🚀

51,091 görüntüleme • 1 ay önce

A DEVELOPER PROVED YOU CAN FIND THE EXACT COMMIT THAT BROKE YOUR CODE IN A HISTORY OF 10,000 -- IN ABOUT 13 STEPS, AUTOMATICALLY.. 33 minutes from a Google engineer on git bisect: the built-in command that binary-searches your entire history to hunt down the one commit that introduced a bug. -> The moment it lands, "When did this break?" stops being an afternoon of guessing. You hand git a good commit, a bad one, and a test and it finds the culprit while you watch. Most people debug a regression by reading diffs by hand, blaming the obvious file, and hoping. Bisect doesn't hope. It cuts the search in half, then in half again, until only the guilty commit is left standing. Reading history by hand was never the skill -> letting git do the binary search for you is. And when an AI agent dumps hundreds of commits into your repo and one quietly breaks production, bisect is what finds the needle without you reading a single line. The bug isn't hiding. It's sitting in one exact commit. Most people just never learned to make git point at it. Bookmark & Watch it today ↓

A DEVELOPER PROVED YOU CAN FIND THE EXACT COMMIT THAT BROKE YOUR CODE IN A HISTORY OF 10,000 -- IN ABOUT 13 STEPS, AUTOMATICALLY.. 33 minutes from a Google engineer on git bisect: the built-in command that binary-searches your entire history to hunt down the one commit that introduced a bug. -> The moment it lands, "When did this break?" stops being an afternoon of guessing. You hand git a good commit, a bad one, and a test and it finds the culprit while you watch. Most people debug a regression by reading diffs by hand, blaming the obvious file, and hoping. Bisect doesn't hope. It cuts the search in half, then in half again, until only the guilty commit is left standing. Reading history by hand was never the skill -> letting git do the binary search for you is. And when an AI agent dumps hundreds of commits into your repo and one quietly breaks production, bisect is what finds the needle without you reading a single line. The bug isn't hiding. It's sitting in one exact commit. Most people just never learned to make git point at it. Bookmark & Watch it today ↓

slash1s

37,628 görüntüleme • 23 gün önce

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

57,975 görüntüleme • 28 gün önce