Comment by idank
6 hours ago
The success of AI doesn't hinge on whether you can vibecode it all or even one particular sector really well. For example, despite several attempts to make vibecoding PCBs, it's still pretty crap. But it's really useful as a copilot, human in the loop for targeted tasks in electronics. Same for CAD work, not so good at drawing but still useful at looking at an image, understanding it, and answering specific questions.
Whether the value attached to these companies is grounded in reality is a different question.
The reality is experience isn't codified in text.
It's passed person to person over long periods of time.
And you can't train an LLM on that.
Yes. For every line of code or documentation I write there is a lengthy internal dialog that can never be scraped & used by an LLM.
It can barely read a datasheet correctly, in my experience, getting confused between different registers.
I'll be more forgiving: I found it gets confused easily when it extracts text from a PDF because datasheets tend to be written in a not so parseable way for a machine. But 1) if you tell it to take screenshots of said datasheet, it'll have greater success. 2) We're in year n<5 (depends how you count) of the age of LLMs, this will get better over time. Either on the LLM side or the thing you feed to it.
Yeah throw it at a moderately complex STM32 clock arrangement and see what comes out.