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

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

На главную

🤖 #AI automated schematic design — what takes a skilled engineer half a day, it finishes in just one hour ⚡. It’s not just software engineers being replaced, #hardware engineers are next 🔧. The AI era is hitting hard, and it’s terrifying. Can we even survive this? 🤔💭

18,439 просмотров • 27 дней назад •via X (Twitter)

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

Фото профиля Adam Taylor
Adam Taylor27 дней назад

Think of the future like engineering in star trek

Фото профиля George Burgyan
George Burgyan27 дней назад

Why even have schematic design? The project I’m working on is using SKiDL as the netlist generator, and I drop into PCB layout skipping the formal schematic step entirely. And since everything is data in the SKiDL layer, the AI can reason about that directly.

Фото профиля Sipeed
Sipeed27 дней назад

AI still has many detail issues when drawing complex schematics. A readable schematic is needed for human review—otherwise, a pure netlist can't be checked. Did you try PCB more than 2000 pins? Is that still work and correct without human review?

Фото профиля George Burgyan
George Burgyan27 дней назад

I'm still doing an absolute ton of reviews personally, so it's not completely AI. And layout (which also catches things) was entirely manual. The biggest win that I found was being able to quickly iterate on questions and design review questions. A typical workflow goes like: "check the connections of the ADC and cross-reference the datasheet to verify that everything in the reference ladder mux is correct." The schematic fundamentally still exists, but it's not in the KiCad (or whatever) format. The SKiDL is 100% isomorphic with with schematic capture, it's just not visual. It's the same as the software side for the same project (which is easier for me since that's my background). Heavy AI use, but I don't let it run wild. AI is great for some things, but I don't think it's a replacement for human judgement.

Фото профиля Luca Barbato
Luca Barbato27 дней назад

Experience and taste cannot be replaced easily. That said vllm.cpp is shaping up, do you want it to support your new Infer Box from day 0? @mudler_it has experience with DGX Spark and contributions are welcome.

Фото профиля Sipeed
Sipeed27 дней назад

@mudler_it Thanks, but it already supported!

Фото профиля Luca Barbato
Luca Barbato27 дней назад

@mudler_it even better!

Фото профиля Michal
Michal27 дней назад

Is this local agent with kicad mcp?

Фото профиля Yasir Prototyper
Yasir Prototyper27 дней назад

Tried AI-assisted schematic capture yet? The tech works seamlessly for traces, but the architecture... let's just say some things are better left un-disrupted. 😅

Фото профиля Sipeed
Sipeed27 дней назад

We have put 1K+ opensource pcb project for AI learning, it is better than me now...

Фото профиля Yasir Prototyper
Yasir Prototyper26 дней назад

@SipeedLab Better at routing, maybe. But when parts hit supply chain dead ends, I'm the one making vendor calls at midnight. Not AI. 😅

Фото профиля philia
philia27 дней назад

Soit tu en dit plus soit tu ne dis rien, là c'est juste une accroche marketing débile !

Фото профиля Joe Desbonnet
Joe Desbonnet27 дней назад

My experiments with Kicad and codex and claude earlier this year were not very successful. It's the one time I was surprised by how poorly it performed. But that was with early 2026 models and very simplistic prompting. Maybe worth another shot.

Фото профиля Vineesh
Vineesh27 дней назад

What did they use

Фото профиля Oliver
Oliver27 дней назад

@grok 用的是哪个画图工具

Фото профиля M. Ceyhan
M. Ceyhan27 дней назад

Which ai please advice wanna to try.

Фото профиля 윤선우
윤선우27 дней назад

와 대단한데요! 당장 사용하고 싶습니다!

Фото профиля Haka Haky
Haka Haky27 дней назад

Is this a skill or a fine-tuned model?

Фото профиля Mikhail Shevtsov
Mikhail Shevtsov27 дней назад

We get more quality products faster due to AI help

Фото профиля Gene Kong
Gene Kong27 дней назад

敢直接用不,感觉当前硬件设计95%都是参考设计缝合而成的,应该可以ai化

Фото профиля Sipeed
Sipeed27 дней назад

不是参考设计缝合的

Фото профиля Sheral Tech
Sheral Tech22 дней назад

Amazing progress AI empowers engineers to innovate faster and achieve more.⚡🚀

Фото профиля 🃏
🃏27 дней назад

Replace me babyyyy

Фото профиля cyber
cyber27 дней назад

Schematic design is easy, now do PCB routing...

Фото профиля Nedyalko Balkanov
Nedyalko Balkanov27 дней назад

I can see it - in the future there would be just THE ENGINEER

Фото профиля TheRickestMorty
TheRickestMorty27 дней назад

Can you write your own posts? I guess not.

Фото профиля Mark James Francis
Mark James Francis27 дней назад

The best I've managed with ai so far is using kicad and konnect MCP. Do you know a better way for AI to create and iterate on a design?

Фото профиля bailout00
bailout0010 дней назад

How do you handle sourcing decisions. I’m finding that’s the hardest part right now

Фото профиля shaunlucky
shaunlucky27 дней назад

This was generated by KiCAD and MCP services on my computer. It's a very simple circuit, but the results don't seem to be very good.

Фото профиля Boz NZ
Boz NZ27 дней назад

Software is a little cheaper/faster to iterate mistakes on than hardware (for now) so it would still be worth running your design past an EE until our AI overlords take over fully.

Фото профиля Daniel Saul D.
Daniel Saul D.27 дней назад

Hubo una época en que todos eran DJs y también sobrevivimos. A ver, que mande a imprimir la IA y revise si le quedó bien.

Фото профиля ali
ali27 дней назад

That is great.👍 What AI tool/skills/MCP server are you using?

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

Jensen Huang just explained why every company cutting engineers over AI is asking the entirely wrong question. Huang: “People say, I don’t need software engineers because apparently coding is going to be automated.” That was the narrative. Here is what Huang actually did. Huang: “I’ve given AIs to every one of my software engineers and hardware engineers and engineers period. 100% of NVIDIA has AI assistants, AI coders, and they’re busier than ever.” Not fewer engineers. Not smaller teams. Busier than ever. That is the line most companies are getting completely wrong right now. They hear “AI can write code” and immediately start cutting headcount. Huang did the opposite. He armed everyone. Huang: “And so the question is, what is the task versus what is the job? No different than a financial analyst; the task is mess around with spreadsheets, but the job is to make financial advice. The job is to help a customer.” Writing code was always the task. It was never the job. The job is architecture. Knowing what to build. Why it matters. How it fits into a system that actually creates value. Code is the execution layer between the idea and the outcome. Nothing more. When you automate that layer, you don’t eliminate the engineer. You eliminate the bottleneck between what they can envision and what they can ship. The companies using AI to cut headcount are optimizing for cost. The companies using AI to multiply output are optimizing for territory. Nvidia chose territory. Every engineer at the most valuable semiconductor company on Earth now operates with an AI assistant. Not a pilot program. Not an experiment. Company-wide. Every function. Every team. And the result is not less work. It is more work. Faster. At a scale that was physically impossible twelve months ago. The companies that understand the difference between eliminating engineers and unleashing them will build what comes next. The ones that don’t will watch their best talent walk out the door to the ones that did.

Dustin

82,841 просмотров • 6 месяцев назад

Some personal hot takes from AI: engineer Miami follows... 1. Software development is a dead-end profession because anyone can be a software developer now. 2. Anyone can use Cursor or any other tool and generate code. Being a coder and being a software engineer are different. 3. Computers used to be gated; now everyone has the power to make computers malleable. Everyone is a software developer now, but that does not mean they are software engineers 4. If you cannot demonstrate how a coding agent works, you are just a consumer and have imposed an artificial glass ceiling on your career as a software engineer. 5. If you are curious, you will have a job. If you have not been curious in the last two years, you are replaceable. 6. SaaS per-seat economics may become unstable as customers need fewer people to achieve results, prompting founders to think about new unit economics 7. Most companies will take two or three years (or more!) to figure out AI transformation. 8. Some companies are already building AI native teams of five to ten people who can build with the grain of AI 9. There will be an explosion in the number of software developers. Software development is now essentially free, and tokens are cheaper than humans 10. Not enough engineers know what it means to be a product engineer 11. JIRA ticket monkeys are cooked 12. If your company has banned AI, you should quit that company 13. AI is more like a musical instrument than just a tool play with it, make discoveries, build intuition learn where AI is good and where it fails

geoff

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

Broadcom's CEO just told investors that one senior engineer with Claude Opus can do in one week what ten engineers earning $300,000 a year take three months to produce. Every engineering org in the world is running the wrong headcount math. This was not a prediction. It was a report from inside Broadcom. Hock Tan said his engineers are already using Claude Opus for engineering design and code assistance. Not experimenting with it. Using it. And the output they are getting from a single senior engineer in one week is equivalent to what a team of ten would produce over three months. Do that math slowly. Ten engineers at $300,000 a year is $3 million in annual salary. Three months of their time is $750,000 of labor. One engineer with Claude Opus produces the same result in one week. He also said something that most people in the room let slide past them. The engineers who get good at these tools do not just get faster. They get better. The designs they produce with AI assistance are probably better than what they would produce without it. That is the part nobody wants to say out loud. It was never just about speed. The ceiling on what a single engineer can produce just moved. And the teams that have not figured that out yet are spending $750,000 to do what one person with the right tools can do for a fraction of that. What do you guys think about this? (Watch the full interview at Bloomberg Live on YouTube)

Ihtesham Ali

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