Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Hardware engineers should probably look away now. One command, and an AI agent built an entire circuit board from scratch while I watched. It drew the schematic, placed every component, routed every trace and checked its own work for errors. 44 components, 55 connections, 191 vias and 1442 mm...

19,380 görüntüleme • 7 gün önce •via X (Twitter)

23 Yorum

Eli Hughes profil fotoğrafı
Eli Hughes7 gün önce

That pcb is *NOT* read to be manufactured. Not even close. Ithink peple need to spend a little time onthe manufacturing floor before make such claims.

Rina profil fotoğrafı
Rina7 gün önce

Yeah, you’re right, I got a bit carried away there

Zack's Lab profil fotoğrafı
Zack's Lab7 gün önce

you must not be a hardware engineer, otherwise you'd know how stupid this looks.

twikker profil fotoğrafı
twikker7 gün önce

Hey, this is a bullshit. Wires are shorted, decoupling caps far away from parts, routing is like a baby painting, connector sits on a mounting hole.

Josh Builds profil fotoğrafı
Josh Builds7 gün önce

a clean check is a nice start, the real test is whether it survives the first prototype spin off the fab

Stelio Kontos profil fotoğrafı
Stelio Kontos7 gün önce

Why would I look away? Laying out and connecting a low speed circuit board isnt challenging. There is an entire field of hardware engineering concerned with interconnects at high frequency, where its a lot more complex than connecting a trace to a component/via

Frindeston Rodriguez profil fotoğrafı
Frindeston Rodriguez7 gün önce

Check the pins orientation, saw several funny usbs facing the wrong direction.

Edgar Ulysses Joya Carballo 🌎🏴‍☠️ profil fotoğrafı
Edgar Ulysses Joya Carballo 🌎🏴‍☠️7 gün önce

Now make it design a chip.

⚔ vukman 🛠 profil fotoğrafı
⚔ vukman 🛠6 gün önce

Price 3.4USD shiping to #bosna 64USD.. chip not available, delivered in 6 months .. lost in post office

Wiseguy☘️ profil fotoğrafı
Wiseguy☘️7 gün önce

Ra ra ra ra pakkana kurcho Ra ra ra ra pakkana kurcho

Martin Ronfort profil fotoğrafı
Martin Ronfort7 gün önce

We actually talked through this with Blake Scholl recently, how software approaches are accelerating hardware design. This circuit board is exactly what he meant.

littletechbird profil fotoğrafı
littletechbird6 gün önce

The soundtrack was.....unexpected

かいごテク profil fotoğrafı
かいごテク6 gün önce

実際に、メインになる大きなICの推奨回路から設計してましたから、AIが出来ても不思議ないですよ?AIが無理なのは、アナログ回路や、完成品のアナログ的な振る舞いや、ノイズなどの不具合の対策じゃないですかね。回路屋の仕事って、殆どがそっち。あと、量産用の資料書いたり治具作ったりね

Terrestre profil fotoğrafı
Terrestre7 gün önce

But... Why that stupid song?

Charles Murlin profil fotoğrafı
Charles Murlin6 gün önce

Bill of material and identified sources of low-cost included? It’s like a word list and run time for dictionary look up

Rua profil fotoğrafı
Rua6 gün önce

这是什么网站或软件?

doitauto profil fotoğrafı
doitauto7 gün önce

IDE?

Debanshu Roy profil fotoğrafı
Debanshu Roy6 gün önce

DFM Nightmare.

Random Aerospace profil fotoğrafı
Random Aerospace6 gün önce

Lmao

jim profil fotoğrafı
jim7 gün önce

so sick 🤟

Svetovid profil fotoğrafı
Svetovid6 gün önce

It looks awful. Btw, auto-routing has been out there since 80s.

Matt Inglot profil fotoğrafı
Matt Inglot6 gün önce

It was a bit more complex to pull off than that, but I did actually get AI to build a complex board and had it manufactured. Did a very detailed write up of this

Lukas Raschendorfer profil fotoğrafı
Lukas Raschendorfer7 gün önce

Wut? Everything is shorted an dthe DRC is OK? try again...

Benzer Videolar

How to create AI employees — start to finish, everything included The complete build of an AI employee, start to finish — the whole path in under four minutes. The agent underneath — every AI employee starts as an agent: a brain (the AI model), tools (real connections into your email, calendar, spreadsheets so it acts instead of only talking), and a loop (it works the job, checks itself, and keeps going until it's done). Feed the brain context and it works on YOUR business. The four upgrades that make it an employee — memory (corrections get written down and read back before every job — explain a thing once and it stays explained), permanent context (your world lives with it and changes as your business changes), skills (your way of doing a job, taught once, followed every time), and a schedule (an agent runs when you call it — an employee clocks in on its own, seven in the morning, inbox already sorted). The build tool — an AI coding assistant: Claude Code or Codex. That class of tool IS the agent machinery — it navigates your context, picks its next move, loops until the job is done, and carries memory between runs. You set it up in plain English, and when a piece you need exists nowhere, it writes that piece itself. The full assembly — pick one job, give it context, wire the tools, teach the skill, add memory, set the schedule. One rule built in: high-stakes moves wait for your yes; everything else runs around the clock. The ceiling — one employee becomes a pattern, patterns become a team, and the team becomes a department passing work to each other. This video is the skeleton of my entire curriculum — every step is a full course, taught from zero, step by step, about four months front to back. It's all inside my community. #aiemployee #aiagent #aiautomation

Professor Glitch

12,600 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.

Akshay 🚀

123,101 görüntüleme • 5 ay önce

this is crazy... the guy reverse-engineered his Meta Ray-Bans 3 with Opus 5.5 into a 3,000+ Elo chess engine he built AI chess cheat glasses on Opus 5.5 + Jev and open-sourced the whole workflow here's how it works step by step: step 1 → install it on your Mac with one command: npx chesshacker setup. It downloads Stockfish from GitHub and verifies the checksum step 2 → put on Meta Ray-Bans and video-call your own Mac on WhatsApp. The glasses see the board, the Mac sees what the glasses see step 3 → the Mac grabs frames straight from the call window. About 1 per second while it waits for the opponent, 1 every 3 seconds on your turn step 4 → Jev runs a cheap pre-check on every frame: is the board readable, is a hand over it, did a piece move? No change means no expensive AI call step 5 → only then Opus 5.5 reads the board. The app compares it with the position it already knows and accepts a move only if it's legal step 6 → Stockfish thinks for half a second and picks the best reply, with an eval like +1.5 or "mate in 3" step 7 → macOS speaks it through a virtual mic into the WhatsApp call: "Rook a to d1". You hear it in your ear step 8 → on the Mac a command center shows everything live: whose turn it is, the suggested move with a confidence bar, the move list and a log under the hood: → if Opus loses track of the board, the glasses say "Lost track of the board" and you fix it with undo or by typing the move → if Stockfish crashes, it restarts once and says "Something went wrong. Still trying" → every game is saved as a PGN file, API keys live in the macOS Keychain → an overlay draws the suggested move as an arrow on the live video, ready for OBS Clone his workflow below Then read the guide on how to reverse-engineer anything with Opus 5.5.

Movez

402,755 görüntüleme • 18 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

Yarchi

58,730 görüntüleme • 5 ay önce

One of the most important people in AI just let an agent loose inside his home. An autonomous AI agent taught itself how an entire house works, then took control of it. This is Andrej Karpathy, the co-founder of OpenAI and former head of AI at Tesla. What he just described should terrify and excite you at the same time. He typed three words into a chat box: "Can you find my Sonos?" The agent immediately ran an IP scan of every device sitting on the home network. It found the Sonos system, noticed there was zero password protection, and logged straight in. Then it searched the web, reverse-engineered the API endpoints, and asked if it should try playing something. Music started coming out of the speakers in the study and Karpathy could not believe what he was watching. The agent then did the exact same thing for every other system in the house. It mapped the lights, the HVAC, the window shades, the pool, the spa, and the full security system, all without being told how any of them worked. It built its own dashboard, created its own APIs, and stitched six separate apps into one unified control center. Now Karpathy just says "Dobby, it's sleepy time," and every light in the house turns off. This is proof that AI agents can now enter an unknown environment, figure out how it works from scratch, build their own tools around it, and take autonomous control. Karpathy also released something called AutoResearch, an AI agent that runs scientific experiments overnight while he sleeps. In just two days, with zero human input, it executed 700 separate experiments and surfaced improvements that trained researchers had missed entirely. Truly incredible.

Milk Road AI

35,698 görüntüleme • 7 ay önce